AWS eks medium security documentation change
Summary
Updated pod networking documentation to recommend podSecurityGroupSelectorTerms instead of SGPP
Security assessment
Explicit guidance to use podSecurityGroupSelectorTerms instead of Security Groups per Pod (SGPP) addresses secure network segmentation practices. This helps users implement proper security group isolation for pods.
Diff
diff --git a/eks/latest/userguide/auto-networking.md b/eks/latest/userguide/auto-networking.md index 3d5c94e7c..c03f0f365 100644 --- a//eks/latest/userguide/auto-networking.md +++ b//eks/latest/userguide/auto-networking.md @@ -65 +65 @@ EKS Auto Mode does **not** support: - * Security Groups per Pod (SGPP). + * Security Groups per Pod (SGPP). To apply separate security groups to Pod traffic in Auto Mode, use `podSecurityGroupSelectorTerms` in the `NodeClass` instead. For more information, see [Separate subnets and security groups for Pods](./create-node-class.html#pod-subnet-selector). @@ -67 +67 @@ EKS Auto Mode does **not** support: - * Custom Networking in the `ENIConfig`. You can put pods in multiple subnets or exclusively isolate them from the node traffic with [Subnet selection for Pods](./create-node-class.html#pod-subnet-selector). + * Custom Networking in the `ENIConfig`. You can put pods in multiple subnets or exclusively isolate them from the node traffic with [Separate subnets and security groups for Pods](./create-node-class.html#pod-subnet-selector). @@ -98 +98 @@ The service implements a cooldown pool for prefixes or secondary IPv4 addresses -For IPv6 clusters, EKS Auto Mode provisions a `/80` IPv6 prefix per node on the primary network interface. +For IPv6 clusters, EKS Auto Mode provisions a `/80` IPv6 prefix per node on the primary network interface. When using `podSubnetSelectorTerms`, the prefix is allocated on a secondary network interface in the pod subnet instead.