The feature is available in all commercial regions at no additional charge, and AWS positions it for workloads where the tenant or the code cannot be trusted, with coding agents named first. In an AWS blog post, Carlos Santana and Trishi Mehta write: Each pod gets its own operating system, completely separate from the host and from every neighbor. According to the EKS documentation, a containerd-shim-nitro-sandbox-v2 process on the parent instance launches a Firecracker microVM as a first-level guest with hardware-assisted virtualization, after which an agent inside the VM runs the pod's containers through its own containerd and the two sides communicate over virtio and vsock. The result is a sandbox that shares neither kernel nor memory mappings with the parent instance or any other sandbox, while the containers themselves start unchanged.
cloud —
AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field
On Amazon EKS, the whole change is one pod field: runtimeClassName: isolated-sandbox or confidential-sandbox.

Reported by infoq.com.




