jbesw / aws-serverless-form-handler Goto Github PK

Hi, thanks for this project!

Trying to deploy it from the Serverless Application Repository seems to fail each time, causing a rollback. When I click to view the stack in CloudFormation, I see the following error:

SubmitFormFunction
CREATE_FAILED
Resource handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs18.x) while creating or updating functions.

I'm not sure how to debug further, as I don't see a way to modify the template before deploying. I'll try creating a new project and see if I can modify that to get it to work.

While submitting my form to my Gmail account from SES I am seeing this error :

Be careful with this message

This may be a spoofed message. The message claims to have been sent from your account, but Gmail couldn't verify the actual source. Avoid clicking links or replying with sensitive information …

Thanks

Great project, but AWS keeps moving forward on supported nodejs versions. 12.x is no longer supported. 18.x is.

Hello,
The application works fine but my submission form has more fields than in the example you shared.

When I hit the Submit Form button I get an email with the following:

Same goes with DynamoDB. Is there a way to send all field submission correctly?

Thanks!

Hi James,

First of all, thanks for building it. I have been using for a month and it works great. I would like to add reCaptcha function and I researched other AWS Serverless Apps Repositories but I don't get hot to do it.

I open the issue as an enhancement for someone with better programing skills than me.

Best regards.

Hi James
I've been having some issue getting this handler working, specifically with the CORS policy. When submitting the form its erroring out. Console reports: Access to XMLHttpRequest at 'https://guqjdlil59.execute-api.eu-west-2.amazonaws.com/Prod' from origin 'http://edgyunderwear.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

When I run Enable CORS on the post method of the API its failing on the last one Add Access-Control-Allow-Origin Integration Response Header Mapping to POST method .

When running a test in the API Console. The request sent to Lambada receives a 200 response but the Endpoint response body before transformations is receiving a 500 response,

For the front end I've used you Gist Serverless Form Example, changing the api end point to my own.

I've spent the entire day try to fix this but I have had to admit defeat in the hope you can help.

Thanks STEVE