AWS Lambda now supports 90-minute function timeout on Lambda Managed Instances
AWS Lambda extends the function timeout for asynchronous and event source mapping invocations on Lambda Managed Instances from 15 minutes to 90 minutes, enabling longer-running workloads like data processing and AI inference without re-architecting applications
AWS Lambda extends function timeouts from 15 to 90 minutes for asynchronous and event source mapping calls on Lambda managed instances (LMI), enabling long-running jobs like data processing, media transcoding, financial calculations, AI inference, and batch processing without application redesign. LMI handles multiple concurrent requests per instance, accesses specialized compute configurations, and improves cost efficiency through EC2 pricing advantages. The extended timeout also applies to calls within Lambda durable functions, supported by checkpoint and replay capabilities, allowing multi-step durable executions to run for up to one year. The 90-minute timeout can be set via the AWS management console, AWS CLI, Lambda API, infrastructure-as-code tools, or AWS agent toolkit, while synchronous calls retain the existing 15-minute maximum. This feature is available in all AWS regions where Lambda managed instances are offered.
Why it matters
This update affects users with long-running workloads such as data processing and AI inference, extending the capabilities of Lambda Managed Instances