AWS Security ChangesHomeSearch

AWS eks documentation change

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

File: eks/latest/userguide/update-cluster.md

Summary

Fixed grammatical error in subnet requirements sentence (changed 'allows' to 'allow')

Security assessment

The change corrects subject-verb agreement but doesn't alter security requirements or address vulnerabilities. The security implications of subnet configuration remain unchanged.

Diff

diff --git a/eks/latest/userguide/update-cluster.md b/eks/latest/userguide/update-cluster.md
index 3fd704477..8aff4c1b0 100644
--- a//eks/latest/userguide/update-cluster.md
+++ b//eks/latest/userguide/update-cluster.md
@@ -29 +29 @@ The update process consists of Amazon EKS launching new API server nodes with th
-To update the cluster, Amazon EKS requires up to five available IP addresses from the subnets that you specified when you created your cluster. Amazon EKS creates new cluster elastic network interfaces (network interfaces) in any of the subnets that you specified. The network interfaces may be created in different subnets than your existing network interfaces are in, so make sure that your security group rules allow [required cluster communication](./sec-group-reqs.html) for any of the subnets that you specified when you created your cluster. If any of the subnets that you specified when you created the cluster don’t exist, don’t have enough available IP addresses, or don’t have security group rules that allows necessary cluster communication, then the update can fail.
+To update the cluster, Amazon EKS requires up to five available IP addresses from the subnets that you specified when you created your cluster. Amazon EKS creates new cluster elastic network interfaces (network interfaces) in any of the subnets that you specified. The network interfaces may be created in different subnets than your existing network interfaces are in, so make sure that your security group rules allow [required cluster communication](./sec-group-reqs.html) for any of the subnets that you specified when you created your cluster. If any of the subnets that you specified when you created the cluster don’t exist, don’t have enough available IP addresses, or don’t have security group rules that allow necessary cluster communication, then the update can fail.