# AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field

Source: [InfoQ](https://www.infoq.com/news/2026/11/aws-nitro-sandboxes-eks/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global) · 2026-11-16 · Cloud & DevOps
Page: https://themorning.dev/story/aws-nitro-sandboxes-put-each-eks-pod-in-its-own-microvm-with-one-runtimeclass-fi-a3c32abe815a051e
Kind: launch · Impact: medium

## In brief

- AWS has launched Nitro Sandboxes, which run each opted-in EKS pod, ECS task or EC2 workload in its own Firecracker microVM with a separate kernel.
- Opting in requires one runtimeClassName field and carries no extra charge.
- A confidential mode adds attestation-gated key release.

## Why it matters

Developers running multi-tenant or untrusted workloads on EKS can get kernel-level isolation per pod by adding one field to their pod spec.

## What to do

- Set runtimeClassName on pods that should run in Nitro Sandboxes

## Coverage

- [AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field](https://www.infoq.com/news/2026/11/aws-nitro-sandboxes-eks/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global) — InfoQ, 2026-11-16

Tags: aws, kubernetes, eks, containers, isolation, virtualization

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
