InfoQ: AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field
AWS launched Nitro Sandboxes, which run an opted-in Kubernetes pod, ECS task, or EC2 workload in its own lightweight microVM with a separate guest kernel, available in all commercial regions at no additional charge. On EKS the feature is enabled by setting runtimeClassName to isolated-sandbox or confidential-sandbox. Confidential mode moves enforcement inside the VM, and the documentation says attestation measurements are not guaranteed to be verified unless a KMS policy or external verifier checks them.
What changes for platform teams
Platform teams on EKS can add a per-pod VM isolation boundary with one field, but standard EKS needs a sandbox-enabled AMI or Karpenter setup, Kubernetes 1.36 or later, and Pod Identity. GPU pods cannot use the sandbox class, and density is capped at five times node vCPUs, with SMT halving usable vCPUs on x86.
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules