AWS Security ChangesHomeSearch

AWS eks documentation change

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

File: eks/latest/userguide/alb-ingress.md

Summary

Minor grammatical corrections and typo fixes (e.g., 'node' to 'nodes', 'based' to 'based on', removed duplicate 'the')

Security assessment

Changes are purely grammatical/typographical with no security context. No vulnerabilities, security features, or security implications are mentioned or modified.

Diff

diff --git a/eks/latest/userguide/alb-ingress.md b/eks/latest/userguide/alb-ingress.md
index 0b2b74889..7c3b737d6 100644
--- a//eks/latest/userguide/alb-ingress.md
+++ b//eks/latest/userguide/alb-ingress.md
@@ -40 +40 @@ Before you can load balance application traffic to an application, you must meet
-If you’re using multiple security groups attached to worker node, exactly one security group must be tagged as follows. Replace `my-cluster` with your cluster name.
+If you’re using multiple security groups attached to worker nodes, exactly one security group must be tagged as follows. Replace `my-cluster` with your cluster name.
@@ -129 +129 @@ You can add an order number of your ingress resource.
-The number can be 1-1000. The lowest number for all ingresses in the same ingress group is evaluated first. All ingresses without this annotation are evaluated with a value of zero. Duplicate rules with a higher number can overwrite rules with a lower number. By default, the rule order between ingresses within the same ingress group is determined lexicographically based namespace and name.
+The number can be 1-1000. The lowest number for all ingresses in the same ingress group is evaluated first. All ingresses without this annotation are evaluated with a value of zero. Duplicate rules with a higher number can overwrite rules with a lower number. By default, the rule order between ingresses within the same ingress group is determined lexicographically based on namespace and name.
@@ -219 +219 @@ If your ingress wasn’t successfully created after several minutes, run the fol
-  2. When you finish experimenting with your sample application, delete it by running one of the the following commands.
+  2. When you finish experimenting with your sample application, delete it by running one of the following commands.