AWS Nitro Sandboxes
An Amazon EC2 feature that runs each EKS pod, ECS task or Firecracker workload in its own lightweight VM beside your instance, with the Nitro hypervisor enforcing the boundary. An Amazon EC2 feature that gives EKS pods, ECS tasks and Firecracker workloads Nitro-enforced VM isolation at no additional charge, for teams that run their own instances on AWS.
Overview
AWS Nitro Sandboxes, announced on 9 November 2026, is an Amazon EC2 feature rather than a sandbox service. A Nitro Sandbox is a lightweight VM that runs beside an EC2 instance (the parent) on vCPUs and memory the parent contributes. It builds on Nitro Enclaves, with changes for general workloads: vCPUs can time-share with the parent, and the parent attaches virtio network and block devices. Because the sandbox runs directly on the Nitro Hypervisor instead of a nested one, AWS says compute runs at EC2 instance-level performance. Firecracker 1.18 or later is currently the only supported virtual machine monitor.
There are three ways to use it. On Amazon EKS (Kubernetes 1.36 or later), setting runtimeClassName to isolated-sandbox or confidential-sandbox runs that pod in its own sandbox; EKS Auto Mode ships the runtime classes, and self-managed nodes need a sandbox-enabled AMI. On Amazon ECS with Managed Instances, a trustedExecutionConfiguration block in the task definition does the same per task. On plain EC2 you launch sandboxes yourself with Firecracker on Amazon Linux 2023, and you own guest images, networking and resource accounting.
Two trust models are offered. In isolated mode (direct mode on EC2) the node is trusted and the goal is to contain the workload. In confidential mode the parent is untrusted: its access to sandbox memory is removed, a Nitro Security Module signs an attestation document, and AWS KMS key policies can release secrets only to a sandbox whose measurements match. AWS names AI agents that run code from their users as a target workload, and points to Lambda MicroVMs for teams that do not want to manage instances. Sandboxes cannot be snapshotted, paused or given GPUs.
Notable
- Up to 5 sandboxes per parent vCPU with CPU overcommit, at most 896 per instance, and at least 256 MiB of memory each
- On EKS a one-line
runtimeClassNamechange sandboxes a pod, and the annotationsandbox.amazonaws.com/network-isolatedboots it with no network device - Confidential mode adds attestation through a Nitro Security Module, with a Cedar policy on EKS controlling images, exec and logs
AWS Nitro Sandboxes specifications
| Attribute | Details |
|---|---|
| Isolation | Each sandbox is a lightweight VM with its own kernel that runs on the Nitro Hypervisor beside the parent EC2 instance and is launched through Firecracker; the Nitro System isolates sandboxes from each other, and in confidential mode it also removes sandbox memory from the parent instance |
| Deployment | Cloud or model provider service |
| Open source | No |
| SDKs and interfaces | Kubernetes RuntimeClass, ECS task definition, Firecracker API, CLI |
| Cold start (vendor claim) | Not documented |
| Max session length | No session limit is documented: a sandbox runs until it powers off, its init process exits or its Firecracker process stops, and every sandbox stops when the parent instance stops, reboots or terminates |
| Persistence | No snapshot and restore, pause and resume or live migration. State lives on block devices backed by instance store or EBS volumes of the parent instance, or on S3 and EFS over the network; on EKS, pods can mount EBS and EFS volumes through the CSI drivers |
| GPU | No — GPU passthrough into a Nitro Sandbox is currently unavailable; on accelerated instances a sandbox runs CPU workloads only |
| Networking | Each sandbox runs its own network stack. On EKS, pods keep a VPC IP through the VPC CNI, and an annotation boots a pod with no network device at all; on ECS each task gets an elastic network interface (awsvpc mode). With Firecracker you wire a TAP device yourself and must block the parent's instance metadata service (169.254.169.254), which a routed sandbox can otherwise reach |
| Pricing | No additional charge: sandboxes run on the vCPUs and memory of the parent EC2 instance, so you pay standard EC2 rates, plus the usual EKS Auto Mode or ECS Managed Instances management fee if you use them |
| Free tier | Not documented |
| Compliance | Not documented |
| Regions | All commercial AWS Regions, on most Nitro-based instance types with Intel, AMD or Graviton processors; flex instances are excluded, as are the smallest and bare-metal sizes of most families |
| Company headquarters | Seattle, Washington, United States · More from the United States |
Facts from AWS Nitro Sandboxes’s public documentation, verified November 14, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You already run agents on EKS, ECS or EC2 and want VM isolation per pod, task or session without a new vendor
- You want a boundary enforced by the Nitro hypervisor rather than a shared kernel or nested virtualisation
- You need to keep workload memory from your own node operators and gate secrets on attestation
- You want no charge beyond the EC2 instances you already pay for
Trade-offs
- An EC2 feature rather than a sandbox API: no SDK for creating sessions, running commands or moving files is documented
- No snapshots, pause and resume, live migration or GPU passthrough
- Sandboxes stop whenever the parent instance stops or reboots, and you size and operate those instances
- On plain EC2 you must block the parent's instance metadata service yourself, or a sandbox can read its IAM role credentials
Good fit for: AWS teams that want a hardware-enforced VM boundary around each agent session on EKS, ECS or their own EC2 fleet, at no charge beyond the instances.
Use cases AWS Nitro Sandboxes fits
- Enterprise & BYOC: A VM boundary around each EKS pod or ECS task inside your own AWS account, with a confidential mode that hides workload memory from node operators and gates KMS keys on attestation.
How AWS Nitro Sandboxes compares
| Sandbox | Company HQ | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|---|
| AWS Nitro Sandboxes | United States | Nitro hypervisor VM | No | No / No | Not documented | No limit; tied to parent instance | No / No | No | Kubernetes RuntimeClass, ECS task definition, Firecracker API, CLI |
| AWS Lambda MicroVMs | United States | Firecracker microVM | No | No / No | sub-second to seconds (claimed) | 8 h | Yes / Yes | Not documented | Python, JavaScript/TypeScript, PHP, CLI, REST API |
| AWS Bedrock AgentCore | United States | MicroVM (Runtime) | No | No / Not documented | Not documented | Up to 8 h | Not documented / Not documented | Not documented | Python (AgentCore SDK), AWS SDKs, AWS CLI |
| Kubernetes Agent Sandbox | Not documented | gVisor or Kata | Yes | Yes / Yes | <1 s (warm pool) | Not documented | Yes / Yes | Yes | Kubernetes CRDs, Python, kubectl |
| Kata Containers | Not documented | VM per pod | Yes | Yes / No | Not documented | Not documented | Not documented / Not documented | Yes | CLI |
| Firecracker | United States | KVM microVM | Yes | Yes / No | <125 ms (spec) | Not documented | Yes / Yes | Not documented | REST API, CLI |
| Edera | United States | Xen-based zone VM | No | Yes / No | Not documented | Not documented | Not documented / Not documented | Yes | CLI |
Head-to-head: AWS Lambda MicroVMs vs AWS Nitro Sandboxes
Frequently asked questions
What is AWS Nitro Sandboxes?
How does AWS Nitro Sandboxes isolate code?
Is AWS Nitro Sandboxes open source?
How much does AWS Nitro Sandboxes cost?
Does AWS Nitro Sandboxes support GPUs?
How long can AWS Nitro Sandboxes sessions run?
Does AWS Nitro Sandboxes support snapshots or pause and resume?
Can you self-host AWS Nitro Sandboxes?
Which regions does AWS Nitro Sandboxes run in?
Where is Amazon Web Services based?
What are the alternatives to AWS Nitro Sandboxes?
Sources
- docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-ec2-nitro-sandboxes.html
- docs.aws.amazon.com/AWSEC2/latest/UserGuide/nitro-sandboxes-run-firecracker.html
- docs.aws.amazon.com/eks/latest/userguide/sandboxing.html
- aws.amazon.com/blogs/compute/nitro-sandboxes-hardware-isolation-for-every-eks-pod-ecs-task-and-ec2-workload/
- aws.amazon.com/blogs/containers/aws-nitro-sandboxes-hardware-enforced-workload-isolation-on-amazon-eks/
- aws.amazon.com/privacy/
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). AWS Nitro Sandboxes. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/sandboxes/aws-nitro-sandboxes/