Repository navigation
[4.x] Raise the maximum function timeout to 30 minutes - #512
Merged
Merged
Conversation
Contributor
|
Yeahhh Nice |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AWS Lambda now lets functions run for up to 30 minutes, double the previous 15-minute limit, through a higher maximum on the existing
Timeoutproperty. The schema still capstimeoutat 900 seconds, and 4.x validates configuration strictly, so setting a longer timeout fails packaging. This raises the schema maximum forprovider.timeoutandfunctions[].timeoutto 1800 seconds. Lambda also now lets durable executions started by event source mappings run for up to 30 minutes, so the cap ondurableConfig.executionTimeoutfor functions with event source mapping events is raised from 900 to 1800 seconds to match. Thetimeoutof web functions is left alone because Lambda still limits it to 900 seconds. The same schema change for 3.x is in #513.