Menu

One Line in a Pod Spec, a VM Underneath: A Practical Guide to AWS Nitro Sandboxes on EKS
📰

One Line in a Pod Spec, a VM Underneath: A Practical Guide to AWS Nitro Sandboxes on EKS

DEV Community: kubernetes·Avneet bansal·3 days ago
#uOEWlnvg
#devtokubernetes#devto#dev#sandbox#node
Reading 0:00
15s threshold

AWS launched Nitro Sandboxes on November 9, 2026. The short version: add runtimeClassName: isolated-sandbox to a pod, and that pod runs in its own lightweight virtual machine, isolated by the same Nitro hypervisor that separates EC2 instances from each other.

This post is what I would want to read as a platform engineer deciding whether to adopt it: the problem it addresses, how it works, how to roll it out, what changes for your workloads, and what it does not solve.

Disclosure: I work at AWS. This post is my own and is based on the public launch blog , the Amazon EKS user guide and the public blueprints repository.

TL;DR

Pods on a node normally share one Linux kernel. A container escape or kernel bug in one pod can reach its neighbors. Nitro Sandboxes give each opted-in pod its own kernel, behind a hardware boundary.

Adoption is one field: runtimeClassName: isolated-sandbox (node trusted) or confidential-sandbox (node untrusted, secrets gated by attestation).…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.