On September 9, 2026, AWS raised the Lambda function timeout to 90 minutes on Lambda Managed Instances and added Graviton5 instances, up to 25% faster than Graviton4. Teams that were working around the 15-minute cap or torn between serverless and EC2 now have a single bridge.
Lambda engineers detail how they replaced an iptables-based packet counter, unable to scale to IPv6, with an eBPF and Rust pipeline that logs every flow across thousands of Firecracker microVMs per host. The lesson outlives AWS: at multi-tenant density, network bookkeeping must be nearly free and provably correct.
On August 25, 2026, AWS opened full IAM resource-based policies to Lambda functions: a single JSON document, the complete range of condition keys, and explicit Deny statements. Platform teams gain precision, but PutResourcePolicy overwrites the whole policy in one call — adopt it with a read-modify-write and an audit of existing triggers first.
On 25 August 2026 AWS Lambda introduced managed runtimes in public preview, a first for the platform, starting with Node.js 26 and Python 3.15. This no-SLA testing channel exists to validate migration ahead of the end-of-support dates of current runtimes.
