Skip to content
Source: InfoQ

🛡️AWS Launches Nitro Sandboxes: Per-Pod VMs at No Extra Charge

Your noisy neighbors just lost their access to your kernel

TL;DR

AWS launched Nitro Sandboxes, which run opted-in Kubernetes pods, ECS tasks, or EC2 workloads in their own Firecracker microVM with a separate guest kernel. It's free in all commercial regions. On EKS, the change is a single pod field, so multi-tenant and regulated workloads get VM-grade isolation without rewriting anything.

AWS just gave every opted-in pod its own operating system. Nitro Sandboxes launch each workload inside a lightweight Firecracker microVM with a separate guest kernel, sharing neither kernel nor memory mappings with the host or any neighbor. The feature is free in all commercial regions. If you run multi-tenant SaaS, regulated workloads, CI builds, or remote IDEs, this is the first time you can get VM-level isolation on EKS without rebuilding your containers. The change on EKS is one pod field, runtimeClassName set to isolated-sandbox or confidential-sandbox. The containers themselves start unchanged, so the cost of trying it is an afternoon, not a migration. The catch is the prerequisites. You need Kubernetes 1.36 or later, a launch template with Nitro Enclaves enabled on managed node groups, and Pod Identity instead of IRSA for credentials. GPU and device passthrough aren't supported at launch. Total sandbox vCPUs are capped at five times the node's vCPU count, and simultaneous multithreading gets expensive because core scheduling keeps sandboxes off sibling threads. Graviton, with one thread per core, avoids that.

AWS Launches Nitro Sandboxes: Per-Pod VMs at No Extra Charge — InfoQ

Key Points

1

Each sandbox runs as a Firecracker microVM with hardware-assisted virtualization, sharing neither kernel nor memory mappings with the parent instance or any other sandbox on the node.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

AWSEKSKubernetesFirecrackerNitro Sandboxes

Comments

Subscribe to join the conversation...

Be the first to comment