AWS eks documentation change
Summary
Minor grammatical corrections: added missing article 'a' before 'group' and corrected 'don't require' to 'doesn't require'.
Security assessment
Changes are purely grammatical improvements without altering security meaning or addressing vulnerabilities. The content still explains that EKS doesn't validate RBAC group existence and access policies can replace RBAC management.
Diff
diff --git a/eks/latest/userguide/creating-access-entries.md b/eks/latest/userguide/creating-access-entries.md index e885126d7..0eb7250f5 100644 --- a//eks/latest/userguide/creating-access-entries.md +++ b//eks/latest/userguide/creating-access-entries.md @@ -69 +69 @@ You can change the username after the access entry is created. -Amazon EKS doesn’t confirm that any Kubernetes RBAC objects that exist on your cluster include any of the group names that you specify. For example, if you create an access entry for group that currently doesn’t exist, Amazon EKS will accept the configuration without returning an error, but the IAM principal won’t have any permissions until matching Kubernetes RBAC resources are created. +Amazon EKS doesn’t confirm that any Kubernetes RBAC objects that exist on your cluster include any of the group names that you specify. For example, if you create an access entry for a group that currently doesn’t exist, Amazon EKS will accept the configuration without returning an error, but the IAM principal won’t have any permissions until matching Kubernetes RBAC resources are created. @@ -71 +71 @@ Amazon EKS doesn’t confirm that any Kubernetes RBAC objects that exist on your -Instead of, or in addition to, Kubernetes authorizing the IAM principal access to Kubernetes objects on your cluster, you can associate Amazon EKS _access policies_ to an access entry. Amazon EKS authorizes IAM principals to access Kubernetes objects on your cluster with the permissions in the access policy. You can scope an access policy’s permissions to Kubernetes namespaces that you specify. Use of access policies don’t require you to manage Kubernetes RBAC objects. For more information, see [Associate access policies with access entries](./access-policies.html). +Instead of, or in addition to, Kubernetes authorizing the IAM principal access to Kubernetes objects on your cluster, you can associate Amazon EKS _access policies_ to an access entry. Amazon EKS authorizes IAM principals to access Kubernetes objects on your cluster with the permissions in the access policy. You can scope an access policy’s permissions to Kubernetes namespaces that you specify. Use of access policies doesn’t require you to manage Kubernetes RBAC objects. For more information, see [Associate access policies with access entries](./access-policies.html).