Amazon Web Services announced AWS Nitro Sandboxes on November 9, 2026. The feature gives a single Kubernetes pod on Amazon EKS, a single task on Amazon ECS, or a small virtual machine on Amazon EC2 its own hardware-enforced boundary, run by the same Nitro hypervisor that already separates whole EC2 instances from each other.
This matters because containers on one node normally share the same Linux kernel, so a kernel bug or container escape can let one workload reach another.
AWS now offers a way to pack many untrusted or multi-tenant workloads, including AI agents that run generated code, onto one instance while each keeps a VM-grade wall around it. There is no extra charge, and it works in all commercial regions.
What AWS Announced
A Nitro Sandbox is a lightweight child VM that runs next to your workload inside an EC2 instance you already pay for. The parent instance donates vCPU and memory, while Nitro keeps the guest apart from the parent, from other sandboxes and from AWS operators. The guest operating system is not trusted to hold the line.
AWS ships three ways to use it:
- Amazon EKS: isolated and confidential pods, chosen per pod through a runtime class in the pod spec.
- Amazon ECS: isolated and confidential tasks, offered as a capability of ECS Managed Instances.
- Amazon EC2: a self-managed mode where your own orchestrator and a virtual machine monitor such as Firecracker start the sandboxes directly from your own images.
The service runs on Intel, AMD and AWS Graviton processors. It works on most Nitro-based instance types, specifically those that can already run AWS Nitro Enclaves, though the smallest and bare-metal sizes of many families are excluded.
Confidential Mode Versus Direct Mode
Each sandbox starts in one of two modes, and the choice cannot change while it runs. Confidential mode is the default. Nitro moves the guest memory out of the parent's reach, so even the people who administer the parent instance cannot read it.
Confidential mode also adds a Nitro Security Module that measures what the sandbox is running. A key policy in AWS KMS can then check those measurements and hand over secrets only to a sandbox whose code matches the expected values. In practice, a database password or API key never reaches a tampered workload.
Direct mode drops attestation and lets the parent share the guest memory. It is simpler and gives higher I/O throughput, and AWS describes its trust level as equal to a normal nested VM. It suits cases where the same trusted team runs both the parent and the sandbox.
How It Works on EKS and ECS
On EKS, the opt-in is one field: set the pod's runtimeClassName to isolated-sandbox or confidential-sandbox. Pods without that setting keep the default runtime. A shim on the node starts a Firecracker microVM for the pod, and an agent inside the sandbox runs the containers through its own containerd.
Every sandboxed pod also gets a Cedar policy that decides which images may load, which containers may start, and whether exec, log streaming and certain mounts are allowed. The policy is enforced inside the guest and recorded in the attestation, so a compromised node cannot quietly swap it.
Encrypted OCI image layers are decrypted inside the sandbox with KMS, and images signed with AWS Signer can be verified before they run.
AWS says normal cluster plumbing keeps working, including Pod Identity, the VPC CNI plugin, EBS, EFS and S3 storage, and CloudWatch. On ECS, the result resembles the per-task isolation of AWS Fargate, but you keep your choice of EC2 instance type, bin-packing of several tasks per host, and Capacity Reservations.
What It Means for Developers
The clearest use case is AI agents. If your application lets a model write and then execute code, that code is untrusted by definition. Running each agent session in its own sandbox lets you share one large instance across many sessions without trusting the kernel as the only barrier.
SaaS teams that run customer code or per-tenant plugins on shared Kubernetes clusters get a similar benefit. Until now, the main options were a separate node per tenant, a sandboxed container runtime you ran yourself, or Fargate. Nitro Sandboxes add a managed, hardware-backed choice that stays on your own EC2 capacity.
Keep the sizing notes in mind. The isolation is a security wall, not a reserved slice of hardware: sandbox vCPUs are time-shared and can oversubscribe the node, so test density before moving production work. Block devices attach to only one sandbox at a time, hot-plugged devices cannot be removed while running, and each sandbox has its own network stack.
For data teams, confidential mode is worth a look when a job handles regulated records or credentials. Tying KMS key release to an attested measurement is a stronger control than an IAM role alone, because it also guards against a compromised host or an over-privileged operator.
How to Get Started
EKS users should read the sandboxing chapter of the EKS User Guide, confirm their node instance types are supported, and try one test pod with the isolated-sandbox runtime class. ECS users start from the isolated and confidential tasks page for ECS Managed Instances.
Teams that want full control can launch a supported EC2 instance with the Nitro Enclaves option turned on, build a guest image that declares its devices, and start it with Firecracker. Other VMMs, such as QEMU, need extra compatibility work before they can use confidential mode or attestation.
If you are building AI features into your applications, our artificial intelligence roadmap for developers covers the wider skills around agents and model-driven code.
Conclusion
AWS Nitro Sandboxes bring VM-level separation down to the size of a single pod, task or agent session, without a dedicated instance per workload and at no added cost.
For teams running untrusted, multi-tenant or regulated code on EKS, ECS or EC2, it is a practical new option, and confidential mode with KMS attestation is the part most worth testing first.
Sources
- AWS What's New: Introducing AWS Nitro Sandboxes on Amazon EKS, ECS and EC2
- Amazon EC2 User Guide: Isolate workloads with AWS Nitro Sandboxes
- Amazon EKS User Guide: Sandboxing with isolated and confidential pods
- Amazon ECS Developer Guide: Isolated and confidential tasks
See my articles more often when you search Google.
