Software · November 16, 2026 · Moderate impact
AWS launches Nitro Sandboxes, giving each opted-in EKS pod its own microVM
AWS has launched Nitro Sandboxes, which run each opted-in EKS pod, ECS task or EC2 workload inside its own Firecracker microVM with a separate kernel. It is enabled by a single runtimeClassName field and carries no extra charge. A confidential mode adds attestation-gated key release. The documentation lists trade-offs: no GPU passthrough, at most five sandboxes per vCPU, and half the compute on SMT instances.
It gives Kubernetes and container users a stronger isolation boundary for multi-tenant workloads with minimal configuration change, though the GPU and density limits matter for planning.