International
The Morning Dev

Only the news worth knowing

‹
 

Launch

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

InfoQ · By Steef-Jan Wiggers ·

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

The 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.

Who’s affected

  • EKS teams running multi-tenant or untrusted workloads
  • ECS and EC2 users evaluating workload isolation

What to do

  1. Set runtimeClassName on pods that should run in Nitro Sandboxes

AWS has launched Nitro Sandboxes, running each opted-in EKS pod, ECS task or EC2 workload in its own Firecracker microVM with a separate kernel, enabled by one runtimeClassName field at no extra charge. A confidential mode adds attestation-gated key release. The documentation…

How do you feel about this?

0 Comments