-
Notifications
You must be signed in to change notification settings - Fork 538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backend Image Handler Lambda Function - Timeout #379
Comments
@fvsnippets thank you for your feedback. We will look into it and add it to our backlog. |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Keeping it open. |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
resolved in v6.2.4 |
Hi @fvsnippets , Thank you, |
Describe the bug
Backend Image Handler Lambda Function construct (CDK) has a timeout of
timeout: Duration.minutes(15)
.It makes no sense to continue executing the lambda after 29 seconds since Api Gateway on front will have replied to CloudFront with a 504 status code (Gateway Timeout).
Notice: read about Api Gateway integrations limits with Lambda.
To Reproduce
Time to time (not frequent... Sometimes it takes days or weeks to see this happens) I experience long delays in receiving the response from S3 (the reason is unknown to me, I didn't investigate, but I guess it's irrelevant to this bug report). This in turn causes Lambda to take more than 29 seconds to respond to the Api Gateway's requet.
Expected behavior
After 29 seconds, Lambda engine timeouts execution.
Backend Image Handler Lambda Function construct (CDK) configured with
timeout: Duration.seconds(29)
.Please complete the following information about the solution:
The text was updated successfully, but these errors were encountered: