AWS eks documentation change
Summary
Multiple grammatical fixes (e.g., 'Identity Access and Management' to 'Identity and Access Management', verb tense corrections)
Security assessment
Changes are exclusively grammatical/typographical. No security features, vulnerabilities, or IAM policy modifications are introduced or discussed.
Diff
diff --git a/eks/latest/userguide/auto-accelerated.md b/eks/latest/userguide/auto-accelerated.md index 439ccad6c..7d164556e 100644 --- a//eks/latest/userguide/auto-accelerated.md +++ b//eks/latest/userguide/auto-accelerated.md @@ -15 +15 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -This tutorial demonstrates how Amazon EKS Auto Mode simplifies launching hardware-accelerated workloads. Amazon EKS Auto Mode streamlines operations beyond the cluster itself by automating key infrastructure components providing compute, networking, load balancing, storage, and Identity Access and Management capabilities out of the box. +This tutorial demonstrates how Amazon EKS Auto Mode simplifies launching hardware-accelerated workloads. Amazon EKS Auto Mode streamlines operations beyond the cluster itself by automating key infrastructure components providing compute, networking, load balancing, storage, and Identity and Access Management capabilities out of the box. @@ -152 +152 @@ Wait a few seconds, and check the nodes in your cluster. You should now see a ne -You can see Amazon EKS Auto Mode launched a `g6e.2xlarge` rather than an `g6.2xlarge` as the workload required an instance with l40s `GPU`, according to the following Kubernetes scheduling constraints: +You can see Amazon EKS Auto Mode launched a `g6e.2xlarge` rather than a `g6.2xlarge` as the workload required an instance with l40s `GPU`, according to the following Kubernetes scheduling constraints: @@ -167 +167 @@ You can see Amazon EKS Auto Mode launched a `g6e.2xlarge` rather than an `g6.2xl -Now, look at the containers logs, by running the following command: +Now, look at the container’s logs by running the following command: @@ -215 +215 @@ The following NodePool defines: - * The 1 hour value for `consolidateAfter` supports spiky workloads and reduce node churn. You can tune `consolidateAfter` based on your workload requirements. + * The 1 hour value for `consolidateAfter` supports spiky workloads and reduces node churn. You can tune `consolidateAfter` based on your workload requirements. @@ -254 +254 @@ The following NodePool defines: -Instead of to setting the `eks.amazonaws.com/instance-gpu-name` you might use `eks.amazonaws.com/instance-family` to specify the instance family. For other well-known labels which influence scheduling review, see [EKS Auto Mode Supported Labels](./create-node-pool.html#auto-supported-labels). +Instead of setting the `eks.amazonaws.com/instance-gpu-name` you might use `eks.amazonaws.com/instance-family` to specify the instance family. For other well-known labels which influence scheduling review, see [EKS Auto Mode Supported Labels](./create-node-pool.html#auto-supported-labels).