AWS Security ChangesHomeSearch

AWS eks documentation change

Service: eks · 2026-04-10 · Documentation low

File: eks/latest/userguide/eks-add-ons.md

Summary

Fixed a typo from 'many' to 'may' in a sentence about EKS add-ons visibility in Auto mode

Security assessment

This change is purely a grammatical correction with no security implications. It fixes a typo in a sentence describing when users can see controllers in their accounts.

Diff

diff --git a/eks/latest/userguide/eks-add-ons.md b/eks/latest/userguide/eks-add-ons.md
index 948ad8f33..2561aa8d8 100644
--- a//eks/latest/userguide/eks-add-ons.md
+++ b//eks/latest/userguide/eks-add-ons.md
@@ -106 +106 @@ With Auto mode compute, many commonly used EKS add-ons become redundant, such as
-However, if your cluster combines Auto mode with other compute options like self-managed EC2 instances, Managed Node Groups, or AWS Fargate, these add-ons remain necessary. AWS has enhanced EKS add-ons with anti-affinity rules that automatically ensure add-on pods are scheduled only on supported compute types. Furthermore, users can now leverage the EKS add-ons `DescribeAddonVersions` API to verify the supported computeTypes for each add-on and its specific versions. Additionally, with EKS Auto mode, the controllers listed above run on AWS owned infrastructure. So, you many not even see them in your accounts unless you are using EKS auto mode with other types of compute in which case, you will see the controllers you installed on your cluster.
+However, if your cluster combines Auto mode with other compute options like self-managed EC2 instances, Managed Node Groups, or AWS Fargate, these add-ons remain necessary. AWS has enhanced EKS add-ons with anti-affinity rules that automatically ensure add-on pods are scheduled only on supported compute types. Furthermore, users can now leverage the EKS add-ons `DescribeAddonVersions` API to verify the supported computeTypes for each add-on and its specific versions. Additionally, with EKS Auto mode, the controllers listed above run on AWS owned infrastructure. So, you may not even see them in your accounts unless you are using EKS auto mode with other types of compute in which case, you will see the controllers you installed on your cluster.