AWS eks documentation change

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

File: eks/latest/userguide/managed-node-groups.md

Summary

Removed the sentence 'We can publish a fix.' from a paragraph about the shared responsibility model for CVEs and security patches.

Security assessment

The change clarifies the shared responsibility model by removing a redundant statement. While the topic involves security patches (CVEs), the edit is a clarification of existing security documentation, not a response to a new security issue or addition of new security features.

Diff

diff --git a/eks/latest/userguide/managed-node-groups.md b/eks/latest/userguide/managed-node-groups.md
index 414eae7bc..9bb03d7f4 100644
--- a//eks/latest/userguide/managed-node-groups.md
+++ b//eks/latest/userguide/managed-node-groups.md
@@ -49 +49 @@ If you are running a stateful application across multiple Availability Zones tha
-  * Amazon EKS follows the shared responsibility model for CVEs and security patches on managed node groups. When managed nodes run an Amazon EKS optimized AMI, Amazon EKS is responsible for building patched versions of the AMI when bugs or issues are reported. We can publish a fix. However, you’re responsible for deploying these patched AMI versions to your managed node groups. When managed nodes run a custom AMI, you’re responsible for building patched versions of the AMI when bugs or issues are reported and then deploying the AMI. For more information, see [Update a managed node group for your cluster](./update-managed-node-group.html).
+  * Amazon EKS follows the shared responsibility model for CVEs and security patches on managed node groups. When managed nodes run an Amazon EKS optimized AMI, Amazon EKS is responsible for building patched versions of the AMI when bugs or issues are reported. However, you’re responsible for deploying these patched AMI versions to your managed node groups. When managed nodes run a custom AMI, you’re responsible for building patched versions of the AMI when bugs or issues are reported and then deploying the AMI. For more information, see [Update a managed node group for your cluster](./update-managed-node-group.html).