AWS eks documentation change
Summary
Fixed subject-verb agreement in IAM policy descriptions and historical policy requirement notes
Security assessment
Changes correct grammar ('allows' → 'allow', 'was' → 'were') without modifying security semantics. No new security guidance or vulnerability fixes introduced.
Diff
diff --git a/eks/latest/userguide/cluster-iam-role.md b/eks/latest/userguide/cluster-iam-role.md index 3125111ce..e7b6f2601 100644 --- a//eks/latest/userguide/cluster-iam-role.md +++ b//eks/latest/userguide/cluster-iam-role.md @@ -21 +21 @@ Before you can create Amazon EKS clusters, you must create an IAM role with eith - * A custom IAM policy. The minimal permissions that follow allows the Kubernetes cluster to manage nodes, but doesn’t allow the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider) to create load balancers with Elastic Load Balancing. Your custom IAM policy must have at least the following permissions: + * A custom IAM policy. The minimal permissions that follow allow the Kubernetes cluster to manage nodes, but doesn’t allow the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider) to create load balancers with Elastic Load Balancing. Your custom IAM policy must have at least the following permissions: @@ -61 +61 @@ Prior to October 3, 2023, [AmazonEKSClusterPolicy](https://docs.aws.amazon.com/a -Prior to April 16, 2020, [AmazonEKSServicePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSServicePolicy.html) and [AmazonEKSClusterPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSClusterPolicy.html) was required and the suggested name for the role was `eksServiceRole`. With the `AWSServiceRoleForAmazonEKS` service-linked role, the [AmazonEKSServicePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSServicePolicy.html) policy is no longer required for clusters created on or after April 16, 2020. +Prior to April 16, 2020, [AmazonEKSServicePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSServicePolicy.html) and [AmazonEKSClusterPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSClusterPolicy.html) were required and the suggested name for the role was `eksServiceRole`. With the `AWSServiceRoleForAmazonEKS` service-linked role, the [AmazonEKSServicePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSServicePolicy.html) policy is no longer required for clusters created on or after April 16, 2020.