Release
I Ran a Lambda Function for 20 Minutes Straight: Inside the 90-Minute Managed Instances Timeout
DEV · By Avneet bansal ·
The Brief
- AWS Lambda's hard limit of 900 seconds per invocation has been extended to 90 minutes for one specific case.
- The extended timeout applies to functions running on Lambda Managed Instances that are invoked asynchronously or in a way the source snippet does not fully specify.
- Before this change, a single continuous computation longer than 900 seconds was outside Lambda's design, according to the source.
Why it matters
Developers with long single-invocation workloads on Lambda Managed Instances may no longer need to split the work or move it to another service, but the change is limited to the specific invocation setup described.
Who’s affected
- Teams running AWS Lambda Managed Instances with long-running functions
For a decade, 900 seconds was the hard wall on a single Lambda invocation. If one continuous computation needed longer, Lambda was the wrong tool and you knew it. That wall just moved for one specific case: functions running on Lambda Managed Instances, invoked asynchronously or…