Run agentic AI, multi-tenant SaaS, and regulated workloads with the isolation of a dedicated Amazon Elastic Compute Cloud (Amazon EC2) instance and the simplicity of a Kubernetes pod. Nitro Sandboxes give each pod a hardware-enforced security boundary, built on the same Nitro System that isolated EC2 instances from each other. Kubernetes containers share a host operating system. That’s what makes them fast and lightweight, but it also means that a vulnerability in one container can compromise every other container on the same machine.

The typical workaround is to give each sensitive workload its own dedicated machine. It works, but it’s expensive, because most of that machine sits idle, and you’re paying for security with wasted infrastructure. Several trends are making this workaround unsustainable: Each of these workarounds depends on keeping a shared kernel patched and spending more on infrastructure to keep workloads apart. A better approach is an architecture where a kernel issue in one workload cannot reach another in the first place, so you don’t have to trade efficiency for isolation.

Autonomous AI agents now probe, adapt, and chain exploits at machine speed, turning every shared-kernel weakness into an attack surface that no human team can patch fast enough. What if the trade-off between efficiency and safety is no longer required? Today we are launching AWS Nitro Sandboxes for Amazon Elastic Kubernetes Service (Amazon EKS) , and with it, pods get strong security isolation for the first time. Every sandboxed pod runs inside its own lightweight virtual machine, powered by the same AWS Nitro System that keeps every EC2 instance isolated from the others.

Each pod gets its own operating system, completely separate from the host and from every neighbor. If something goes wrong inside the pod, no syscall can reach anything outside the guest kernel. Any workload that needs strong isolation now gets a hardware boundary, without dedicating a machine to each one. On EKS Auto Mode, enabling Nitro Sandboxes is a one-line change to your pod spec. You don’t change your container images, deployment pipelines, or Helm charts.