lambda-api | Lightweight web framework for your serverless applications | REST library

I followed the instructions here for setting up a gateway and a lambda but it does not work. The symptoms appear to be the same as described here but the fixes suggested there did not work.

My infrastructure definition is as follows:

AWS Environment -- Lamdba function pulling from RDS/PostgreSQL instance and pushing through API Gateway.

SecretsManager makes it easy enough to pass static data like usernames and passwords to the Lambda function. Terraform, however, prohibits the use of dynamic variables in its variable resource. As such, Terraform cannot define a host and pass the host to the Lambda function through SecretsManager.

I've considered exporting the variable to the environment at the end of the Terraform script. But this would not export to the same machine that the Lambda is running on, correct? SecretsManager is obviously a hacked-ass way to do it in anyway. And all the resources I'm finding just seem to have some manual in between during the creation of the RDS instance and the Lambda function.

Thank you in advanced.

Terraform :

I have a basic lambda function which accepts a JSON, and transforms to XML and uploads the same to s3 bucket. I am running the test through the lambda console and the xml is getting generated and uploaded to s3 as well. Issue happens when I run the test through API Gateway, and there I get the error:

I'm attempting to send a POST request from a Google Sheet, containing a given row's data, using Google Apps Script. That request is to an AWS API Gateway, which sends it along to a Lambda function which then does some other things.

The AWS side all works when I use curl to send requests manually, but for some reason when I attempt to do it programmatically inside Sheets, the API will only pass null events to my function. The POST requests appear to be well formed when I print them out on the Sheets side, but my API refuses to pass them through. I know this because I have it set to log all events passed to the function in CloudWatch, and the automatic calls all just print {} as the event.

There's no authentication required in the API, so I can't imagine it being an auth issue. I also saw a common solution being to enable Lambda Proxy Integration, but I don't understand why curl would work if that were the issue.

I built my API using this tutorial almost exactly, if that's helpful.

Here's the relevant bit of code from the Apps Script side:

I am experimenting with using AWS. To be specific, I am following the tutorial at this link:

https://aws.amazon.com/getting-started/hands-on/build-web-app-s3-lambda-api-gateway-dynamodb/module-three/?e=gs2020&p=build-a-web-app-two

I have tried to add empty PHP tags to the start of the file and renamed the file to index.php instead of the index.HTML of the tutorial. I did a full sequence of refreshing the web app resources and deploying the app on the Amplify console. It did not work. I tried only using the HTML code on index.php and it still did not work. I put back the PHP code, added an echo statement echo "

Is there any way for me to use a file named index.php as the home page of a web app using AWS amplify?

New to Amplify. Following the tutorial on AWS and everything looks good.

Now I want to add a simple html file, called abc.html, just some basic html code for a test. But when I try to visit the url: https://www.yourdomain.com/abc.html, it redirects the url to https://www.yourdomain.com/abc/. So it basically doesn't recognize there is a file called abc.html. How can I add new files to Amplify?

From Amplify console, everything looks OK. It responded to the git push. Provision, build, deploy, verify are all green. It just can't recognize the new added file. Any suggestions?

I'm using API Gateway and AWS Lambda to exchange with another AWS Lambda function.

I'm supposed to send a response after an initial request to insert data, whether it's a success or a failure. I'm using a specific route with API Gateway.

Here's the structure :

Now I keep getting 502 Malformed Lambda proxy response and this is in my API Test logs :

Similar questions has been made but none of them were able to help me fix the issue that I'm facing. What I'm trying to do is to connect my api-gateway/lamnda function with a custom domain name and for some reason when calling the api/domain is not returning what I expected.

cdk version: 1.53.0

I'm learning terraform, and one of the well written tutorials on hashicorp has given me some problems towards the end.

I have a file defining my lambda, and its relationship to an API Gateway. The connections to the API Gateway haven't been tested, since I can't seem to get the API Gateway to deploy.

lambda.tf