AWS eks documentation change
Summary
Fixed typos in two sentences: corrected 'an entry for with' to 'an entry with', and added comma in script download instruction
Security assessment
Minor grammatical fixes without security implications; no vulnerability addressed or security features documented
Diff
diff --git a/eks/latest/userguide/troubleshooting.md b/eks/latest/userguide/troubleshooting.md index cf67095ac..cfc6dc827 100644 --- a//eks/latest/userguide/troubleshooting.md +++ b//eks/latest/userguide/troubleshooting.md @@ -77 +77 @@ This could be due to one of the following reasons: - * If your cluster doesn’t meet the minimum platform requirements in [Grant IAM users access to Kubernetes with EKS access entries](./access-entries.html), an entry with your IAM principal doesn’t exist in the `aws-auth` `ConfigMap`. If it exists, it’s not mapped to Kubernetes group names that are bound to a Kubernetes `Role` or `ClusterRole` with the necessary permissions. For more information about Kubernetes role-based authorization (RBAC) objects, see [Using RBAC authorization](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) in the Kubernetes documentation. You can view your current `aws-auth` `ConfigMap` entries by replacing `my-cluster` in the following command with the name of your cluster and then running the modified command: `eksctl get iamidentitymapping --cluster `my-cluster` `. If an entry for with the ARN of your IAM principal isn’t in the `ConfigMap`, enter `eksctl create iamidentitymapping --help` in your terminal to learn how to create one. + * If your cluster doesn’t meet the minimum platform requirements in [Grant IAM users access to Kubernetes with EKS access entries](./access-entries.html), an entry with your IAM principal doesn’t exist in the `aws-auth` `ConfigMap`. If it exists, it’s not mapped to Kubernetes group names that are bound to a Kubernetes `Role` or `ClusterRole` with the necessary permissions. For more information about Kubernetes role-based authorization (RBAC) objects, see [Using RBAC authorization](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) in the Kubernetes documentation. You can view your current `aws-auth` `ConfigMap` entries by replacing `my-cluster` in the following command with the name of your cluster and then running the modified command: `eksctl get iamidentitymapping --cluster `my-cluster` `. If an entry with the ARN of your IAM principal isn’t in the `ConfigMap`, enter `eksctl create iamidentitymapping --help` in your terminal to learn how to create one. @@ -324 +324 @@ Use the following command to run the script on your node: -If the script is not present at that location. You can manually download and run the script with the following command: +If the script is not present at that location, you can manually download and run the script with the following command: