AWS Security ChangesHomeSearch

AWS eks documentation change

Service: eks · 2026-05-22 · Documentation low

File: eks/latest/userguide/auto-troubleshoot.md

Summary

Fixed grammar in node diagnostics, pod scheduling, and network analysis sections

Security assessment

Clarity improvements only. No changes to security troubleshooting procedures or content.

Diff

diff --git a/eks/latest/userguide/auto-troubleshoot.md b/eks/latest/userguide/auto-troubleshoot.md
index f7f98a63e..42d4dbff7 100644
--- a//eks/latest/userguide/auto-troubleshoot.md
+++ b//eks/latest/userguide/auto-troubleshoot.md
@@ -91 +91 @@ First, you need to determine the EC2 Instance ID of the instance associated with
-The recommended way of retrieving logs from an EKS Auto Mode node is to use `NodeDiagnostic` resource. For these steps, see [Retrieve node logs for a managed node using kubectl and S3](./auto-get-logs.html).
+The recommended way of retrieving logs from an EKS Auto Mode node is to use a `NodeDiagnostic` resource. For these steps, see [Retrieve node logs for a managed node using kubectl and S3](./auto-get-logs.html).
@@ -172 +172 @@ Look for errors related to your EKS cluster. Use the error messages to update yo
-If pods staying in the `Pending` state and aren’t being scheduled onto an auto mode node, verify if your pod or deployment manifest has a `nodeSelector`. If a `nodeSelector` is present, ensure that it is using `eks.amazonaws.com/compute-type: auto` to be scheduled on nodes that are made by EKS Auto Mode. For more information about the node labels that are used by EKS Auto Mode, see [Control if a workload is deployed on EKS Auto Mode nodes](./associate-workload.html).
+If pods are staying in the `Pending` state and aren’t being scheduled onto an auto mode node, verify if your pod or deployment manifest has a `nodeSelector`. If a `nodeSelector` is present, ensure that it is using `eks.amazonaws.com/compute-type: auto` to be scheduled on nodes that are made by EKS Auto Mode. For more information about the node labels that are used by EKS Auto Mode, see [Control if a workload is deployed on EKS Auto Mode nodes](./associate-workload.html).
@@ -271 +271 @@ With these two pieces of information, you can perform the analysis. First naviga
-  11. The analysis might take a few minutes to complete. If the analysis results indicates failed reachability, it will indicate where the failure was in the network path so you can resolve the issue.
+  11. The analysis might take a few minutes to complete. If the analysis results indicate failed reachability, it will indicate where the failure was in the network path so you can resolve the issue.