AWS eks documentation change
Summary
Fixed typos and improved documentation clarity for access entry management
Security assessment
Typo corrections and language clarity improvements without security impact.
Diff
diff --git a/eks/latest/eksctl/access-entries.md b/eks/latest/eksctl/access-entries.md index d2b772c21..b412daec6 100644 --- a//eks/latest/eksctl/access-entries.md +++ b//eks/latest/eksctl/access-entries.md @@ -13 +13 @@ This topic covers how to use eksctl to manage access entries. For general inform -You can attach Kubernetes access policies defined by AWS, or assocoiate an IAM Identity with a Kubernetes group. +You can attach Kubernetes access policies defined by AWS, or associate an IAM Identity with a Kubernetes group. @@ -17 +17 @@ For more information about the available pre-defined policies, see [Associate ac -If you need to define customer Kubernetes policies, associate the IAM Identity with a Kubernetes group, and grant permissions to that group. +If you need to define custom Kubernetes policies, associate the IAM Identity with a Kubernetes group, and grant permissions to that group. @@ -111 +111 @@ Each access entry has a type. For authorizing self-managed nodegroups, `eksctl` -When creating your own access entries, you can also specify `EC2_LINUX` (for an IAM role used with Linux or Bottlerocket self-managed nodes), `EC2_WINDOWS` (for an IAM roles used with Windows self-managed nodes), `FARGATE_LINUX` (for an IAM roles used with AWS Fargate (Fargate)), or `STANDARD` as a type. If you don’t specify a type, the default type is set to `STANDARD`. +When creating your own access entries, you can also specify `EC2_LINUX` (for an IAM role used with Linux or Bottlerocket self-managed nodes), `EC2_WINDOWS` (for IAM roles used with Windows self-managed nodes), `FARGATE_LINUX` (for IAM roles used with AWS Fargate (Fargate)), or `STANDARD` as a type. If you don’t specify a type, the default type is set to `STANDARD`. @@ -133 +133 @@ For an example config file for creating access entries, see [40-access-entries.y -The user can retieve all access entries associated with a certain cluster by running one of the following: +The user can retrieve all access entries associated with a certain cluster by running one of the following: