Run isolated sandboxes with full lifecycle control: AWS Lambda introduces MicroVMs
AWS Lambda ยท 2026-06-22
Actions
Technical Details
| Regions | us-east-1, us-east-2, us-west-2, eu-west-1, ap-northeast-1 |
|---|---|
| Cost Impact | Neutral |
| IaC Impact | High |
What This Means
For DevOps Teams
Update your deployment processes to integrate Lambda MicroVMs for running user- or AI-generated code in isolated environments, leveraging Firecracker technology for near-instant launch and resume, and reducing toil associated with managing complex virtualization infrastructure.
For Platform Teams
Adopt Lambda MicroVMs to simplify architecture and reduce operational toil by providing isolated, stateful execution environments with rapid launch and resume capabilities, powered by Firecracker technology.
For Executives
Evaluate deploying Lambda MicroVMs to enhance security and performance for multi-tenant applications, enabling isolated execution environments with rapid launch and resume capabilities, and reducing engineering resources required for custom virtualization infrastructure.
Source
Related AWS Lambda Updates
- AWS introduces Lambda MicroVMs for isolated execution of user and AI-generated code (2026-06-22)
- Upgrading Lambda function runtimes at scale with AWS Transform custom (2026-06-20)
- AWS Lambda Managed Instances now supports Tag Propagation for Managed Resources (2026-06-15)
- AWS Lambda Managed Instances expands to additional AWS Regions (2026-06-08)
- ARC Region switch adds Lambda event source mapping execution block for event handling during failover (2026-05-14)