The story’s score and claims

Comments on No. 21 of 95 · docs.aws.amazon.com · edition of Tuesday 10 November 2026

Sandboxing on Amazon EKS with isolated and confidential pods

Summary

AWS has added Nitro Sandboxes for EKS pods, ECS tasks and plain EC2. Each pod opts in through runtimeClassName and runs in its own Firecracker microVM with a Cedar admission policy. Isolated mode protects the node from the workload. Confidential mode treats the parent instance as untrusted and uses KMS-gated attestation. The documentation says vCPUs are time-shared and can be oversubscribed, so this is a security boundary, not a performance reservation. AWS says it costs nothing extra. The attestation and policy claims rest on AWS's own documentation.

Comments

Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules