AWS Nitro Sandboxes Give Each EKS Pod Its Own MicroVM
Isolation depends on the mode chosen: isolated mode still trusts the parent instance, while confidential mode needs attestation checks to hold.

AWS has released Nitro Sandboxes, which place an opted-in Kubernetes pod, ECS task or EC2 workload in a dedicated microVM with its own guest kernel, split off from a running EC2 instance by the Nitro hypervisor. On EKS, enabling it requires only one pod setting, choosing either the isolated or the confidential sandbox runtime class. The capability is offered at no extra charge across commercial regions, and AWS points to coding agents as the first use case. Developers should note that isolated mode still trusts the parent instance, so a compromised host can observe unencrypted traffic and DNS and mint Pod Identity credentials for other pods, while confidential mode moves enforcement inside the VM but only holds if attestation measurements are actually verified. Practical limits include no GPU or device passthrough at launch and a density cap of five times the node's vCPU count.
Why it matters
For operators running multi-tenant Kubernetes on AWS, the feature offers stronger workload separation at no extra charge, but the protection is not automatic. Isolated mode leaves a compromised host able to see unencrypted traffic and DNS, and confidential mode only gives its guarantee when attestation measurements are actually checked. Limits at launch, including no GPU or device passthrough and a cap on sandbox vCPUs, mean the feature suits some workloads more than others.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.