InfoQRenato Losio2 min readintermediate
AWS Lambda Pushes Serverless Toward Long-Running Workloads
Summary
AWS Lambda Managed Instances now allow functions to run up to 90 minutes, six times longer than before, and add Graviton5 support. The longer timeout requires careful handling of connections, credentials, and idempotency, and may shift some workloads from ad‑hoc workarounds to Lambda but also invites cost‑aware alternatives.
- Lambda Managed Instances support up to 90‑minute execution, extending the previous 15‑minute cap.
- Longer runtimes demand explicit management of network connections, temporary credentials, and idempotent logic to survive retries.
- Lambda still offers two models: 15‑minute event‑driven functions and MicroVMs up to 8 hours; Managed Instances bridge steady‑state workloads with EC2‑like pricing.
- The change can eliminate many workarounds but may encourage expensive patterns; evaluate ECS Tasks or AWS Batch for truly long or idle‑heavy jobs.
Serverless engineers and architects need to know the new limits and design considerations to decide if Lambda can replace traditional compute for longer jobs.
6/10
