Skip to content
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

APIGW Integration Timeout Increase #2258

Merged
merged 1 commit into from
Aug 1, 2024
Merged

Conversation

Wilveren
Copy link
Contributor

Setting upper limit of integration timeout to max timeout time for a lambda function. This is per the change AWS has rolled out which allows the integration timeout to be increased beyond 29000: https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-api-gateway-integration-timeout-limit-29-seconds/

@markpeek
Copy link
Member

@Wilveren thank you for the PR. Per my additional email comment to you, can you clarify where you saw the "900,000" max timeout value? Thanks!

@Wilveren
Copy link
Contributor Author

@Wilveren thank you for the PR. Per my additional email comment to you, can you clarify where you saw the "900,000" max timeout value? Thanks!

Sure! There's no documented upper limit for the integration timeout now, so I figured it was logical to set it to the same upper limit as a Lambda function.

@markpeek
Copy link
Member

markpeek commented Jul 31, 2024

Thanks for the updated commit. Can you remove integer_range import (now not used) and squash the commits?

@Wilveren
Copy link
Contributor Author

Thanks for the updated commit. Can you remove integer_range import (now not used) and squash the commits?

Done. = )

@markpeek markpeek merged commit 3a1ff77 into cloudtools:main Aug 1, 2024
3 of 6 checks passed
@markpeek
Copy link
Member

markpeek commented Aug 1, 2024

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants