AWS eks documentation change
Summary
Fixed a grammatical error ('add an access entries' to 'add access entries') in the section about IAM principal access configuration
Security assessment
The change is purely grammatical and does not alter any security guidance or configurations. It maintains existing documentation about IAM access management without introducing new security concepts or addressing vulnerabilities.
Diff
diff --git a/eks/latest/userguide/eks-outposts-local-cluster-create.md b/eks/latest/userguide/eks-outposts-local-cluster-create.md index 8956481d9..a25a87f31 100644 --- a//eks/latest/userguide/eks-outposts-local-cluster-create.md +++ b//eks/latest/userguide/eks-outposts-local-cluster-create.md @@ -186 +186 @@ The `eksctl` command automatically created an [access entry](./access-entries.ht -If you want a different IAM principal than the principal creating the cluster to have administrator access to Kubernetes cluster objects, choose the disallow option. After cluster creation, any IAM principal that has IAM permissions to create access entries can add an access entries for any IAM principals that need access to Kubernetes cluster objects. For more information about the required IAM permissions, see [Actions defined by Amazon Elastic Kubernetes Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonelastickubernetesservice.html#amazonelastickubernetesservice-actions-as-permissions) in the Service Authorization Reference. If you choose the disallow option and don’t create any access entries, then no IAM principals will have access to the Kubernetes objects on the cluster. +If you want a different IAM principal than the principal creating the cluster to have administrator access to Kubernetes cluster objects, choose the disallow option. After cluster creation, any IAM principal that has IAM permissions to create access entries can add access entries for any IAM principals that need access to Kubernetes cluster objects. For more information about the required IAM permissions, see [Actions defined by Amazon Elastic Kubernetes Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonelastickubernetesservice.html#amazonelastickubernetesservice-actions-as-permissions) in the Service Authorization Reference. If you choose the disallow option and don’t create any access entries, then no IAM principals will have access to the Kubernetes objects on the cluster.