AWS eks documentation change
Summary
Fixed grammatical errors ('in' to 'is' and added missing article 'a') in node group creation documentation
Security assessment
These are minor grammatical corrections that don't change technical content. The policy attachment guidance for Outposts remains unchanged, and there's no evidence of security vulnerability fixes or new security features being documented.
Diff
diff --git a/eks/latest/userguide/eks-outposts-self-managed-nodes.md b/eks/latest/userguide/eks-outposts-self-managed-nodes.md index 113a5a2b2..3df826a45 100644 --- a//eks/latest/userguide/eks-outposts-self-managed-nodes.md +++ b//eks/latest/userguide/eks-outposts-self-managed-nodes.md @@ -73 +73 @@ You can create a self-managed node group for local cluster with the following to - 2. If your cluster is on the AWS Cloud and the **AmazonEKS_CNI_Policy** managed IAM policy is attached to your [Amazon EKS node IAM role](./create-node-role.html), we recommend assigning it to an IAM role that you associate to the Kubernetes `aws-node` service account instead. For more information, see [Configure Amazon VPC CNI plugin to use IRSA](./cni-iam-role.html). If your cluster in on your Outpost, the policy must be attached to your node role. + 2. If your cluster is on the AWS Cloud and the **AmazonEKS_CNI_Policy** managed IAM policy is attached to your [Amazon EKS node IAM role](./create-node-role.html), we recommend assigning it to an IAM role that you associate to the Kubernetes `aws-node` service account instead. For more information, see [Configure Amazon VPC CNI plugin to use IRSA](./cni-iam-role.html). If your cluster is on your Outpost, the policy must be attached to your node role. @@ -75 +75 @@ You can create a self-managed node group for local cluster with the following to - 3. The following command creates a node group in an existing cluster. The cluster must have been created using `eksctl`. Replace `al-nodes` with a name for your node group. The node group name can’t be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. Replace `my-cluster` with the name of your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can’t be longer than 100 characters. The name must be unique within the AWS Region and AWS account that you’re creating the cluster in. If your cluster exists on an Outpost, replace `id` with the ID of an Outpost subnet. If your cluster exists on the AWS Cloud, replace `id` with the ID of a subnet that you didn’t specify when you created your cluster. Replace the remaining example values with your own values. The nodes are created with the same Kubernetes version as the control plane, by default. + 3. The following command creates a node group in an existing cluster. The cluster must have been created using `eksctl`. Replace `al-nodes` with a name for your node group. The node group name can’t be longer than 63 characters. It must start with a letter or digit, but can also include hyphens and underscores for the remaining characters. Replace `my-cluster` with the name of your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can’t be longer than 100 characters. The name must be unique within the AWS Region and AWS account that you’re creating the cluster in. If your cluster exists on an Outpost, replace `id` with the ID of an Outpost subnet. If your cluster exists on the AWS Cloud, replace `id` with the ID of a subnet that you didn’t specify when you created your cluster. Replace the remaining example values with your own values. The nodes are created with the same Kubernetes version as the control plane, by default.