AWS Security ChangesHomeSearch

AWS eks: Hardware-enforced pod isolation on EKS compute

Service: eks · 2026-11-10 · Security-related medium

File: eks/latest/userguide/eks-compute.md · Type: isolation

Summary

Adds guidance on running selected pods in hardware-isolated VMs with Nitro Sandboxes instead of shared-kernel containers.

Security assessment

The change documents a hardening option that mitigates shared-kernel container isolation risk using hardware-isolated VMs.

Evidence

+On nodes in the AWS Cloud, you can run selected pods inside hardware-isolated virtual machines with Nitro Sandboxes, instead of standard containers that share the node’s kernel. Nitro Sandboxes works with EKS Auto Mode and with managed or self-managed nodes that use a compatible AMI, on instance types that support Nitro Enclaves. It is available in AWS Regions, but not in the AWS GovCloud (US) Regions or the China Regions. For more information, see [Sandboxing on Amazon EKS with isolated and confidential pods](./sandboxing.html).

Diff

diff --git a/eks/latest/userguide/eks-compute.md b/eks/latest/userguide/eks-compute.md
index a02fa12..43f8677 100644
--- a//eks/latest/userguide/eks-compute.md
+++ b//eks/latest/userguide/eks-compute.md
@@ -33,0 +34,4 @@ Excluding hybrid nodes, nodes must be in the same VPC as the subnets you selecte
+###### Hardware-enforced pod isolation
+
+On nodes in the AWS Cloud, you can run selected pods inside hardware-isolated virtual machines with Nitro Sandboxes, instead of standard containers that share the node’s kernel. Nitro Sandboxes works with EKS Auto Mode and with managed or self-managed nodes that use a compatible AMI, on instance types that support Nitro Enclaves. It is available in AWS Regions, but not in the AWS GovCloud (US) Regions or the China Regions. For more information, see [Sandboxing on Amazon EKS with isolated and confidential pods](./sandboxing.html).
+