Lambda API Triggers shows "Internal Server Error"
I have created an API trigger and a GET route for a lambda function which returns a simple "Hello World" response. However, when I click on the API endpoint URL it takes a long time, approximately 5 minutes until the browser shows {"message":"Internal Server Error"}.
Image 1: Lambda API Trigger
Please advice what configurations am I missing here?
- Newest
- Most votes
- Most comments
Hello.
An error will occur if there is a problem with the Lambda function's resource-based policy or if the Lambda function does not return the specified response format.
I recommend using log variables to see more details.
https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-troubleshooting-lambda.html
Hi,
Please, check your CloudTrail logs to get last API calls (possibly done by Lambda) to see if some of them fails and how they fail. It may be more precise than 500 to understand the root cause of your problem.
Best,
Didier
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 months ago
AWS OFFICIALUpdated 3 months ago- AWS OFFICIALUpdated 7 months ago
Hi Riku, thanks for the recommendations. I have applied the log variables "$context.integrationErrorMessage" to CloudWatch. However, there seems to be no related errors when logging.
If you just want to return "Hello World", I think the example in the following document will be helpful. Please try configuring the settings in this document once and check if there are any configuration differences with the current API Gateway. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-create-api-as-simple-proxy-for-lambda.html
Thanks Riku. I managed to create a workable API using this guide