AWS eks: Nitro Sandboxes hardware isolation in EKS architecture
Summary
Explains that standard pods share the node kernel, while Nitro Sandboxes provide a hardware trust boundary via isolated VMs.
Security assessment
The change explicitly addresses the shared-kernel isolation weakness by documenting hardware-isolated VMs and a trust boundary between pods.
Evidence
+Regardless of the node type, pods on a node run in standard containers that share the node’s Linux kernel by default. With Nitro Sandboxes, you can instead run selected pods inside their own hardware-isolated virtual machine on the AWS Nitro System. This provides a hardware trust boundary between pods on the same node. You opt in per pod by setting a runtime class. For more information, see [Sandboxing on Amazon EKS with isolated and confidential pods](./sandboxing.html).
Diff
diff --git a/eks/latest/userguide/eks-architecture.md b/eks/latest/userguide/eks-architecture.md index 7ce0595..46dce8b 100644 --- a//eks/latest/userguide/eks-architecture.md +++ b//eks/latest/userguide/eks-architecture.md @@ -76,0 +77,2 @@ With [Amazon EKS Hybrid Nodes](./hybrid-nodes-overview.html), you can use your o +Regardless of the node type, pods on a node run in standard containers that share the node’s Linux kernel by default. With Nitro Sandboxes, you can instead run selected pods inside their own hardware-isolated virtual machine on the AWS Nitro System. This provides a hardware trust boundary between pods on the same node. You opt in per pod by setting a runtime class. For more information, see [Sandboxing on Amazon EKS with isolated and confidential pods](./sandboxing.html). +