AWS Lambda now supports 90-minute function timeout on Lambda Managed Instances (aws.amazon.com)

AWS Lambda has announced an extension of its function timeout limit to 90 minutes for asynchronous and event source mapping (ESM) invocations on Lambda Managed Instances, a significant increase from the previous 15-minute cap. This enhancement enables developers to run complex, data-intensive tasks—like media transcoding, financial simulations, and AI inference—reliably within a single execution context. By allowing longer continuous execution, AWS helps users avoid convoluted architectural workarounds that often arise from the former time constraints. The introduction of this extended timeout not only facilitates more efficient processing of large workloads but also enhances cost efficiency through the benefits of EC2 pricing without the need to manage underlying infrastructure directly. Additionally, this update applies to durable functions within Lambda, which can now maintain the state across long-running processes for up to a year, emphasizing its utility in event-driven architectures. Developers can configure these timeouts easily through the AWS Lambda Console and various APIs, solidifying Lambda's position as a flexible choice for serverless applications in the AI/ML sector.