AWS eks medium security documentation change
Summary
Added control plane egress routing configuration option during cluster creation
Security assessment
Documents new security feature allowing customers to manage network paths for control plane egress traffic. Enables security-focused network architectures and compliance requirements.
Diff
diff --git a/eks/latest/userguide/create-cluster.md b/eks/latest/userguide/create-cluster.md index 0a441e697..56f9954ed 100644 --- a//eks/latest/userguide/create-cluster.md +++ b//eks/latest/userguide/create-cluster.md @@ -222,0 +223,2 @@ You can only specify this option when using the `IPv4` address family and only a + * (Optional) For **Control plane egress** , choose how egress traffic from the control plane to your VPC is routed. The default is Amazon EKS managed. If you select customer routed, you become responsible for the network path from the control plane to your VPC resources. For more information, see [Configuring control plane egress routing](./control-plane-egress.html). + @@ -277,0 +280,2 @@ Whether you choose any security groups or not, Amazon EKS creates a security gro + * (Optional) To manage the egress path from the control plane to your VPC yourself, add `controlPlaneEgressMode=CUSTOMER_ROUTED` to `--resources-vpc-config`. The default is `AWS_MANAGED`. You can also change this setting after cluster creation. For more information, see [Configuring control plane egress routing](./control-plane-egress.html). +