AWS eks documentation change
Summary
1. Fixed grammatical error in node group naming rules 2. Corrected typo in IMDSv1 documentation ('MDSv1' to 'IMDSv1')
Security assessment
The grammatical fixes have no security impact. The IMDSv1 typo correction improves accuracy but doesn't address a vulnerability or change security guidance. IMDS documentation already existed.
Diff
diff --git a/eks/latest/userguide/launch-windows-workers.md b/eks/latest/userguide/launch-windows-workers.md index 9b887135f..12e1c7332 100644 --- a//eks/latest/userguide/launch-windows-workers.md +++ b//eks/latest/userguide/launch-windows-workers.md @@ -56 +56 @@ This procedure only works for clusters that were created with `eksctl`. -Create your node group with the following command. Replace `region-code` with the AWS Region that your cluster is in. Replace `my-cluster` with your cluster name. 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. Replace `ng-windows` 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. You can replace `2019` with `2022` to use Windows Server 2022 or `2025` to use Windows Server 2025. Replace the rest of the example values with your own values. +Create your node group with the following command. Replace `region-code` with the AWS Region that your cluster is in. Replace `my-cluster` with your cluster name. 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. Replace `ng-windows` 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. You can replace `2019` with `2022` to use Windows Server 2022 or `2025` to use Windows Server 2025. Replace the rest of the example values with your own values. @@ -147 +147 @@ This name must exactly match the name that you used in [Step 1: Create your Amaz - * **NodeGroupName** : Enter a name for your node group. This name can be used later to identify the Auto Scaling node group that’s created for your nodes. 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. + * **NodeGroupName** : Enter a name for your node group. This name can be used later to identify the Auto Scaling node group that’s created for your nodes. 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. @@ -175 +175 @@ If you don’t provide a key pair here, the AWS CloudFormation stack fails to be - * **DisableIMDSv1** : By default, each node supports the Instance Metadata Service Version 1 (IMDSv1) and IMDSv2. You can disable IMDSv1. To prevent future nodes and Pods in the node group from using MDSv1, set **DisableIMDSv1** to **true**. For more information about IMDS, see [Configuring the instance metadata service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html). + * **DisableIMDSv1** : By default, each node supports the Instance Metadata Service Version 1 (IMDSv1) and IMDSv2. You can disable IMDSv1. To prevent future nodes and Pods in the node group from using IMDSv1, set **DisableIMDSv1** to **true**. For more information about IMDS, see [Configuring the instance metadata service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html).