AWS has introduced Nitro Sandboxes, a feature for Amazon EKS that runs each opted-in Kubernetes pod inside its own lightweight virtual machine. By setting a single pod field, workload isolation is achieved on top of the Nitro System, using the same hardware separation layer that underpins EC2 instance isolation.

Sources describe two isolation modes via runtime classes. A standard “isolated” mode places each pod in its own sandbox, while a “confidential” mode treats the machine operator as untrusted and gates access to AWS KMS secrets using attestation that references an expected system image and policy. Outlets also outline operational and resource-related trade-offs, including limits on GPU passthrough, sandbox density, and reduced compute on SMT instances. They note that egress controls are handled per workload through allowlisting hostnames, and that some shared resources at the node level (such as bandwidth and I/O contention) remain subject to default protection with configurable throttles.

While both outlets focus on how the runtimeClassName option works and how confidentiality is achieved, one emphasizes the end-to-end boot and in-guest checks flow and the granularity of networking policies; the other highlights Firecracker microVM underpinnings and documented performance/compatibility constraints.