Menu

1 / 7

AWS Nitro Sandboxes Put Each EKS Pod Inside Its Own Virtual Machine

DEV Community: kubernetes·Taha Echakiri·39 minutes ago
#2R5XZAIB
#devtokubernetes#devto#dev#nitro#sandbox
Reading 0:00
15s threshold

TL;DR

AWS Nitro Sandboxes is a feature of Amazon EKS, announced on 9 November 2026, that runs each Kubernetes pod inside its own lightweight virtual machine on the Nitro System, the same hardware layer that keeps EC2 instances apart.

On EKS Auto Mode the whole opt-in is one pod field: runtimeClassName: isolated-sandbox . Images, Helm charts and deployment pipelines stay as they are.

A second runtime class, confidential-sandbox , treats the machine operator as untrusted and releases an AWS KMS secret only against an attestation document naming the expected system image and Cedar policy.

The boot sequence inside a Nitro Partition runs through the scheduler, a VM boot, an in-guest policy check and a standard container runtime, while the kubelet still sees an ordinary pod.

Egress is declared per workload: the sample coding agent reaches Amazon Bedrock through Pod Identity and one GitHub repository through a scoped token, and an ApplicationNetworkPolicy allows only CoreDNS and HTTPS to those…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.