- Check the invocation type first.
- Longer runtime is not a recovery strategy.
What changed
AWS says asynchronous and event-source-mapping invocations on Lambda Managed Instances can now run for up to 90 minutes, up from 15. Synchronous invocations retain the 15-minute ceiling. Availability follows the regions supporting Lambda Managed Instances.
Why the distinction matters
A headline about a longer timeout is not enough to decide whether an existing workload qualifies. Identify its invocation mode and deployment model before changing configuration. The announcement does not establish that a longer-running job will complete successfully or that its dependencies can tolerate the same duration.
A practical evaluation
Use a representative non-production job. Record completion time, duplicate handling, failure recovery and the cost boundary you actually observe. Longer execution reduces one limit; it does not remove the need for checkpoints, idempotency or operational evidence. This is a reading of the launch announcement, not a TLB benchmark.
Read beyond this page.
Recorded source-check date: 10 Sep 2026. A link is not, by itself, evidence that every claim has been independently verified.
Changes & version history
Version 3 · 10 Sep 2026
Scheduled release of checksum-bound AI-assisted editorial review
Version 2 · 10 Sep 2026
Checksum-bound editorial review scheduled for release
Version 1 · 10 Sep 2026
Source-linked private review edition