AWS says Nitro Sandboxes are available on EKS, ECS and EC2

AWS says Nitro Sandboxes are available for an Amazon EKS pod, an Amazon ECS task, or a lightweight EC2 virtual machine. The notice is dated November 9, 2026, and AWS says there is no extra charge.

Each workload gets its own Nitro virtual machine. AWS describes Nitro Sandboxes as lightweight virtual machines that the Nitro Hypervisor manages. A pod, a task, or a small VM, including an AI agent running inside it, sits in a separate hardware-isolated machine on the Nitro System. AWS says that boundary is the same isolation a Nitro virtual machine already provides. The company says customers can run untrusted, multi-tenant, or regulated work on the resources of one instance.

AWS says performance stays close to a normal EC2 instance. The sandboxes run on the customer's EC2 instances and take on the isolation of the Nitro hypervisor. Customers can check a workload with cryptographic attestation. AWS says secrets are handed over only after a sandbox has shown that it is intact.

The notice points to agent code as one use. AWS says customers can run code that a large language model produced inside an isolated environment of its own. It says several agent workloads can share one EC2 instance, which can raise utilization and reduce compute cost. The notice does not give a price beyond the statement that there is no extra charge.

Turning the feature on for EKS or ECS is a one-line change. AWS says each pod or task then gets its own virtual machine. It says existing tools keep working, including Pod Identity, the VPC CNI, EBS, EFS, S3, and CloudWatch. Customers who want full control can run the sandboxes on EC2 with their own machine image, their own orchestration, and their own virtual machine monitors. Amazon Linux and Firecracker are supported without an added layer. AWS says patches for other options are available.

The feature is on most Nitro-based EC2 instances. AWS says that covers all commercial regions worldwide. The notice points readers to the EKS, ECS, and EC2 user guides for setup. It does not list a start date later than the November 9 post.