AWS eks: Nitro Sandboxes isolation in EKS deployment options
Summary
Adds a deployment-options section describing hardware-enforced pod isolation with Nitro Sandboxes on EKS.
Security assessment
The change documents a security isolation capability for selected pods, reducing exposure from shared node environments.
Evidence
+When you run Amazon EKS in the cloud, you can run selected pods inside hardware-isolated virtual machines with Nitro Sandboxes. Nitro Sandboxes works on top of either EKS Auto Mode or managed and self-managed node groups. EKS Auto Mode includes Nitro Sandbox support with no additional configuration. For managed node groups or self-managed nodes, you build a compatible AMI.
Diff
diff --git a/eks/latest/userguide/eks-deployment-options.md b/eks/latest/userguide/eks-deployment-options.md index 5b97bfd..fb9a943 100644 --- a//eks/latest/userguide/eks-deployment-options.md +++ b//eks/latest/userguide/eks-deployment-options.md @@ -45,0 +46,6 @@ Kubernetes data plane location | AWS Regions | AWS Local or Wavelength Zones +### Hardware-enforced pod isolation with Amazon EKS + +When you run Amazon EKS in the cloud, you can run selected pods inside hardware-isolated virtual machines with Nitro Sandboxes. Nitro Sandboxes works on top of either EKS Auto Mode or managed and self-managed node groups. EKS Auto Mode includes Nitro Sandbox support with no additional configuration. For managed node groups or self-managed nodes, you build a compatible AMI. + +Nitro Sandboxes is available in AWS Regions. It is not available 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). +