IT Service Management··1 sources verified
AWS Nitro Sandboxes Give Each EKS Pod Its Own MicroVM via One RuntimeClass Field
Summarised by Relevant News AI · Read time: 3 min
AWS launched Nitro Sandboxes, which run each opted-in EKS pod, ECS task, or EC2 workload in its own Firecracker microVM with a separate kernel. Teams enable it with a single runtimeClassName field at no extra charge, and a confidential mode adds attestation-gated key release. The documentation lists trade-offs, including no GPU passthrough, a limit of five sandboxes per vCPU, and half the compute available on SMT instances.
Why it matters: Platform and operations teams can add kernel-level workload isolation to existing EKS clusters with a configuration change, but they need to plan around the GPU, density, and SMT limits before rolling it out.
All sources