# I Ran a Lambda Function for 20 Minutes Straight: Inside the 90-Minute Managed Instances Timeout

Source: [DEV Community: python](https://dev.to/avneet_bansal_a65b3f31fc4/i-ran-a-lambda-function-for-20-minutes-straight-inside-the-90-minute-managed-instances-timeout-12n5) · 2026-11-17 · Languages
Page: https://themorning.dev/story/i-ran-a-lambda-function-for-20-minutes-straight-inside-the-90-minute-managed-ins-af214cd1dbf76ef4
Kind: release · Impact: medium

## In 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.

## Coverage

- [I Ran a Lambda Function for 20 Minutes Straight: Inside the 90-Minute Managed Instances Timeout](https://dev.to/avneet_bansal_a65b3f31fc4/i-ran-a-lambda-function-for-20-minutes-straight-inside-the-90-minute-managed-instances-timeout-12n5) — DEV Community: python, 2026-11-17

Tags: aws, lambda, serverless, timeouts, cloud

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
