Skip to content

[4.x] Raise the maximum function timeout to 30 minutes - #512

Merged
GrahamCampbell merged 1 commit into
4.xfrom
lambda-timeout-30-minutes
Nov 19, 2026
Merged

GrahamCampbell merged 1 commit into
4.xfrom
lambda-timeout-30-minutes

Conversation

@GrahamCampbell

@GrahamCampbell GrahamCampbell commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

AWS Lambda now lets functions run for up to 30 minutes, double the previous 15-minute limit, through a higher maximum on the existing Timeout property. The schema still caps timeout at 900 seconds, and 4.x validates configuration strictly, so setting a longer timeout fails packaging. This raises the schema maximum for provider.timeout and functions[].timeout to 1800 seconds. Lambda also now lets durable executions started by event source mappings run for up to 30 minutes, so the cap on durableConfig.executionTimeout for functions with event source mapping events is raised from 900 to 1800 seconds to match. The timeout of web functions is left alone because Lambda still limits it to 900 seconds. The same schema change for 3.x is in #513.

@GrahamCampbell
GrahamCampbell merged commit 8820dee into 4.x Nov 19, 2026
8 checks passed
@GrahamCampbell
GrahamCampbell deleted the lambda-timeout-30-minutes branch November 19, 2026 21:16
@mnapoli

mnapoli commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Yeahhh Nice

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