ToolsSeptember 19, 2026via InfoQ AI/ML
AWS Lambda Pushes Serverless Toward Long-Running Workloads
Why it matters
A significant capability expansion in a widely-used platform shifts the cost/complexity tradeoff for long-running workloads. Practitioners building on Lambda need to reassess architecture decisions around function duration and cost.
Key signals
- AWS Lambda Managed Instances now support 90-minute timeout (previously 15 minutes)
- 6x increase in maximum function duration
- Change applies only to Lambda Managed Instances, not traditional synchronous requests
- Blurs boundary between Lambda and traditional servers in workload suitability
- Published September 2026
- Lambda Managed Instances now support up to 90-minute function runtime (6x increase from 15-minute previous limit)
- Limit applies only to asynchronous invocations on Managed Instances; synchronous request timeout unchanged
- Blurs distinction between serverless Lambda and traditional server-based architectures
The hook
AWS Lambda now runs 6x longer—up to 90 minutes. Practitioners rethinking serverless vs. always-on compute.
AWS Lambda now allows functions running on Lambda Managed Instances to run for up to 90 minutes, six times longer than the previous 15-minute limit, further blurring the line between a Lambda invocation and a traditional server. The limit remains unchanged for traditional synchronous requests.
By R…