AWS Nitro Sandboxes: hardware-isolated VMs for AI agents

The launch responds to a specific shift in how code gets written: AI coding agents are increasingly generating code that runs in lightweight virtual environments like containers, but container virtualization often shares a kernel. That shared kernel means a single malicious payload could reach other containers or services on the same machine. AWS positions Nitro Sandboxes as a middle ground—hardware-level isolation from the Nitro System without giving up the near-native EC2 performance that makes containers practical.

The design keeps each sandbox on a fully independent OS, and system calls inside cannot reach the host or other sandboxes and containers. For teams already on Amazon EKS, the integration aims to be low-friction: in auto mode, enabling the feature converts Pods into lightweight VMs while leaving container images, deployment pipelines, and Helm charts unchanged. That suggests AWS is targeting existing container workflows rather than asking customers to rebuild around a new primitive.