aws-lambda-microvms
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes. Triggers on: Lambda MicroVMs, Firecracker isolation, snapshot-resumable compute, suspend/resume, sandboxed or untrusted code execution, AI/agent code-execution sandboxes, interactive code playgrounds and notebooks (Jupyter, REPLs), reinforcement-learning environments, multi-tenant CI executors and build runners, sessionful game or simulation servers, isolated security scanners, long-lived sessions,
npx skills add awslabs/agent-plugins --skill aws-lambda-microvms --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AWS Lambda MicroVMs > The AWS MCP server is recommended for sandboxed execution and audit logging. AWS Lambda MicroVMs are serverless compute environments that combine Firecracker VM isolation with container-like efficiency. Each MicroVM: - Runs your application as a **container inside a Firecracker microVM** — you can reproduce the environment locally. - Runs Amazon Linux 2023 as the base OS inside the MicroVM. - Boots from a **memory + disk snapshot** captured at image build time, so application init is skipped on run. - Has a dedicated, TLS-terminated HTTPS endpoint reachable with an auth token. - Can be **suspended and resumed** with state preserved; lives up to 8 hours. **Two-resource model:** - `MicrovmImage` — a versioned artifact built from `{S3 zip with Dockerfile} + baseImageArn`. Each version has per-architecture/chipset `Build`s. - `Microvm` — a running instance created (`RunMicrovm`) from an image version. **Two roles:** - `buildRoleArn` — used during image build (S3 read, CloudWatch logs, optional ECR). - `executionRoleArn` — assumed at runtime by the running MicroVM. ## When to use ### Choose Lambda MicroVMs when - **Analytics workloads** — isolated compute for dat
- When to use
- Choose Lambda MicroVMs when
- Choose AWS Lambda (functions) when
- Choose something else when
- Typical workflow
- Core CLI commands
- Hook configuration
- microvmImageHooks (build-time)
- microvmHooks (runtime)
- Per-MicroVM size limits
- Additional capabilities
- Shell ingress for agent use cases
- Known constraints
- Reference index
Create an image (zip with Dockerfile at root in S3, plus a managed base image) aws lambda-microvms create-microvm-image \ Run a MicroVM (returns endpoint + microvmId). --image-identifier takes the image ARN (the bare name is rejected); --image-version is the full major.minor string. aws lambda-microvms run-microvm \ Mint an auth token and call the endpoint curl "<endpoint>/" -H "X-aws-proxy-auth: $TOKEN" Lifecycle aws lambda-microvms suspend-microvm --microvm-identifier microvm-... aws lambda-microvms resume-microvm --microvm-identifier microvm-...
What does the aws-lambda-microvms skill do?
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes. Triggers on: Lambda MicroVMs, Firecracker isolation, snapshot-resumable compute, suspend/resume, sandboxed or untrusted code execution, AI/agent code-execution sandboxes, interactive code playgrounds and notebooks (Jupyter, REPLs), reinforcement-learning environments, multi-tenant CI executors and build runners, sessionful game or simulation servers, isolated security scanners, long-lived sessions,
How do I install it?
Run `npx skills add awslabs/agent-plugins --skill aws-lambda-microvms --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From awslabs/agent-plugins, a repository with 850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.