aws-lambda-microvms

1# AWS Lambda MicroVMs
2 
3> The AWS MCP server is recommended for sandboxed execution and audit logging.
4 
5AWS Lambda MicroVMs are serverless compute environments that combine Firecracker VM isolation with container-like efficiency. Each MicroVM:
6 
7- Runs your application as a **container inside a Firecracker microVM** — you can reproduce the environment locally.
8- Runs Amazon Linux 2023 as the base OS inside the MicroVM.
9- Boots from a **memory + disk snapshot** captured at image build time, so application init is skipped on run.
10- Has a dedicated, TLS-terminated HTTPS endpoint reachable with an auth token.
11- Can be **suspended and resumed** with state preserved; lives up to 8 hours.
12 
13**Two-resource model:**
14 
15- `MicrovmImage` — a versioned artifact built from `{S3 zip with Dockerfile} + baseImageArn`. Each version has per-architecture/chipset `Build`s.
16- `Microvm` — a running instance created (`RunMicrovm`) from an image version.
17 
18**Two roles:**
19 
20- `buildRoleArn` — used during image build (S3 read, CloudWatch logs, optional ECR).
21- `executionRoleArn` — assumed at runtime by the running MicroVM.
22 
23## When to use
24 
25### Choose Lambda MicroVMs when
26 
27- **Analytics workloads** — isolated compute for data processing, ETL jobs, or query execution with strong tenant separation.
28- **AI / agent code execution sandboxes** — fresh, isolated environment per session, fast resume between turns.
29- **Interactive code playgrounds & notebooks** — Jupyter, REPLs, dev environments executing user code.
30…