ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial1 min readDisconfirmAI Editorial

AWS Lambda doubles on-demand function timeout to 30 minutes, easing constraints for long-running AI agents

AWS Lambda now supports 30-minute timeouts for on-demand functions, removing the 15-minute barrier for complex AI inference and agentic workflows.

2026-11-20 03:28 GMT+8

Amazon Web Services (AWS) has increased the maximum timeout for AWS Lambda Event Functions running on demand from 15 minutes to 30 minutes. This change also applies to synchronous invocations on Lambda Managed Instances. The update, announced on November 19, 2026, allows developers to run longer continuous processes—such as AI inference, media transcoding, and financial calculations—without needing to re-architect their applications to split tasks across multiple shorter invocations.

The previous 15-minute limit was a significant constraint for emerging AI workloads, particularly agentic systems that chain multiple model calls and tool invocations. These sequences often exceed 15 minutes to return a final result. By doubling the limit, AWS addresses a common pain point where spiky traffic patterns did not justify the steady-state capacity costs of other compute options, yet required more time than the old timeout allowed.

For asynchronous and event source mapping (ESM) invocations on Lambda Managed Instances, the timeout remains at 90 minutes, a limit introduced in September 2026. The new 30-minute standard for on-demand synchronous functions brings parity to these core invocation types. Developers can configure this timeout using the AWS CLI, AWS SAM templates, or the Lambda console. The change is available in all commercial AWS Regions for on-demand Event Functions.

Sources

Sign in / Sign up
ReadingResearchRadarInvestment framework
aws.amazon.com
Amazon Web Services
↗
Continue researching →