AWS eks documentation change
Summary
Updated instructions for enabling Kubernetes network policies, added AWS CLI command example, and removed redundant CLI steps while restructuring content.
Security assessment
The changes document how to configure Kubernetes network policies (a security feature), but there is no evidence of addressing a specific security vulnerability. Network policies are standard security controls for traffic management.
Diff
diff --git a/eks/latest/userguide/cni-network-policy-configure.md b/eks/latest/userguide/cni-network-policy-configure.md index 1b6ccf047..93d942f85 100644 --- a//eks/latest/userguide/cni-network-policy-configure.md +++ b//eks/latest/userguide/cni-network-policy-configure.md @@ -90 +90 @@ Use the following procedure to enable the network policy parameter for the add-o - 5. On the **Configure`name of add-on` ** page: + 5. On the **Configure`Amazon VPC CNI` ** page: @@ -158 +158,10 @@ For all other cluster versions, if you upgrade the Amazon EKS optimized Amazon L -Configure the cluster to use Kubernetes network policies. You can set this for an Amazon EKS add-on or self-managed add-on. +You can set this for an Amazon EKS add-on or self-managed add-on. + +Using the AWS CLI, you can configure the cluster to use Kubernetes network policies by running the following command. Replace `my-cluster` with the name of your cluster and the IAM role ARN with the role that you are using. + + + aws eks update-addon --cluster-name my-cluster --addon-name vpc-cni --addon-version v1.14.0-eksbuild.3 \ + --service-account-role-arn arn:aws:iam::123456789012:role/AmazonEKSVPCCNIRole \ + --resolve-conflicts PRESERVE --configuration-values '{"enableNetworkPolicy": "true"}' + +To configure this using the AWS Management Console, follow the below steps: @@ -168 +177 @@ Configure the cluster to use Kubernetes network policies. You can set this for a - 5. On the **Configure`name of addon` ** page: + 5. On the **Configure`Amazon VPC CNI` ** page: @@ -185,9 +193,0 @@ The following screenshot shows an example of this scenario. - 1. Run the following AWS CLI command. Replace `my-cluster` with the name of your cluster and the IAM role ARN with the role that you are using. - - aws eks update-addon --cluster-name my-cluster --addon-name vpc-cni --addon-version v1.14.0-eksbuild.3 \ - --service-account-role-arn arn:aws:iam::123456789012:role/AmazonEKSVPCCNIRole \ - --resolve-conflicts PRESERVE --configuration-values '{"enableNetworkPolicy": "true"}' - - - -