New featureMedium

AWS introduces Lambda MicroVMs for isolated execution of user and AI-generated code

AWS Lambda now offers MicroVMs, providing VM-level isolation, near-instant launch and resume speeds, and state preservation for executing user or AI-generated code

AWS has introduced Lambda MicroVMs, a new serverless compute primitive that delivers VM-level isolation, near-instant launch and resume speeds, and state preservation for executing user or AI-generated code. Developers building multi-tenant applications that run end-user or AI-supplied code now have a way to allocate a separate, isolated execution environment per user or session without trade-offs between isolation, speed, and state retention. Lambda MicroVMs, built on Firecracker virtualization technology, allows developers to create a MicroVM image from a Dockerfile and launch MicroVMs with dedicated HTTPS URLs supporting protocols like HTTP/2, gRPC, and WebSockets. Currently available in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland). Pricing is based on baseline compute resources while the MicroVM runs, with additional charges only for active duration beyond the baseline

Read the original AWS announcement

Related articles and terms

The Birth of Firecracker - Why the MicroVM Behind Lambda and Fargate Was CreatedExplore the design philosophy behind Firecracker, the microVM monitor AWS built for Lambda and Fargate. Learn how it differs from traditional virtualization, the secret behind its 125ms boot time, and the strategic intent behind open-sourcing it.Why Lambda's Limit Is 15 Minutes - The Rationale Behind Serverless Design ConstraintsThis article explains why Lambda's various limits - 15-minute maximum execution time, 10GB memory cap, 6MB payload - are set at those specific values, from the perspective of Firecracker's design philosophy and multi-tenant operations.Behind Lambda's 1,000 Concurrent Executions - How Firecracker Warm Pools and Worker Managers WorkThis article explains how Lambda manages MicroVMs within the default concurrency limit of 1,000, the warm pool reuse strategy, worker manager placement decisions, and internal optimizations that reduce cold start rates.How AI-DLC Transforms Software Development - A Practical Guide to the Inception, Construction, and Operation PhasesAn overview of the AI-DLC methodology that places AI at the center of the development process. Learn about the three phases of Inception, Construction, and Operation, and how to put them into practice with Kiro and Amazon Q Developer.The Layered Architecture of AWS AI/ML Services - Flexibility Through the Three Tiers of SageMaker, Bedrock, and API ServicesThis article organizes AWS AI/ML services into three layers - SageMaker (full control), Bedrock (managed generative AI), and Rekognition/Comprehend/etc. (API-based) - and explains AWS's flexibility through comparisons with GCP Vertex AI and Azure OpenAI Service, including custom silicon integration.