A Guth Labs publication ↗
Back to News

AWS doubles on-demand Lambda Event Function timeout to 30 minutes

Cream hourglass filled with gold grains beside stacked green glass servers.
AI-generated editorial illustration

AWS increased the maximum timeout for on-demand Lambda Event Functions from 15 to 30 minutes on November 19, giving longer AI inference and agent workflows more execution time.

The change covers synchronous, asynchronous and event-source-mapping invocations, according to the AWS announcement. Synchronous functions on Lambda Managed Instances also gain the 30-minute limit. Asynchronous and event-source-mapping invocations on Managed Instances retain their existing 90-minute maximum, introduced in September.

AWS says the longer timeout is available across all commercial regions for on-demand Event Functions, with standard Lambda pricing. The Managed Instances change applies wherever that service is available. Developers must update their function configuration to use the increased limit.

The extension does not apply to every Lambda format: Web Functions retain a 15-minute duration limit. AWS also warns that Lambda does not guarantee exactly-once processing, so longer jobs still need safeguards against duplicate effects during retries.

For agents chaining model requests and tool calls, the update reduces the need to split work solely to fit the previous execution window.

Sources and citations

Revision history

Published .