• Sources: primary, discussion
  • Summary: AWS Nitro Sandboxes are lightweight VMs managed by the Nitro Hypervisor that run on customers' own EC2 instances. Enabling them in EKS or ECS gives each pod or task its own VM while Pod Identity, VPC CNI, EBS, EFS, S3 and CloudWatch keep working. On EC2 they support Amazon Linux and Firecracker directly, and they are available in all commercial regions on most Nitro instances.
  • Why it matters: Teams running LLM-generated code or multi-tenant workloads on Kubernetes can get VM isolation per pod without a separate sandbox provider or dedicated hosts.
  • Background: Containers share the host kernel, so a kernel bug can let one workload reach another. Projects such as Kata Containers and Firecracker put each workload in a microVM to add a hardware boundary. AWS now offers that model natively inside EKS and ECS, with attestation so secrets go only to verified sandboxes.