AWS eks medium security documentation change
Summary
Added IPv4-only listener fix for Pod Identity Agent and corrected KMS key configuration typo
Security assessment
The IPv4 listener fix addresses potential network connectivity issues that could prevent security components from functioning properly. The KMS key configuration change ('configued' to 'configured') improves clarity but doesn't introduce new security content.
Diff
diff --git a/eks/latest/userguide/auto-change.md b/eks/latest/userguide/auto-change.md index 1c1dfb640..efeaa83d0 100644 --- a//eks/latest/userguide/auto-change.md +++ b//eks/latest/userguide/auto-change.md @@ -5 +5 @@ -August 6, 2025June 30, 2025June 20, 2025June 13, 2025April 30, 2025April 18, 2025April 11, 2025April 4, 2025March 31, 2025March 21, 2025March 14, 2025 +August 15, 2025August 6, 2025June 30, 2025June 20, 2025June 13, 2025April 30, 2025April 18, 2025April 11, 2025April 4, 2025March 31, 2025March 21, 2025March 14, 2025 @@ -19,0 +20,4 @@ To receive notifications of all source file changes to this specific documentati +## August 15, 2025 + +**Bug Fix:** The Pod Identity Agent will now only listen on the IPv4 Link Local address in an IPv4 EKS cluster to avoid issues where the Pod can’t reach the IPv6 address. + @@ -26 +30 @@ To receive notifications of all source file changes to this specific documentati -**Feature:** The Auto Mode NodeClass now uses the configued custom KMS key to encrypt the read-only root volume of the instance, in addition to the read/write data volume. Previously, the custom KMS key was only used to encrypt the data volume. +**Feature:** The Auto Mode NodeClass now uses the configured custom KMS key to encrypt the read-only root volume of the instance, in addition to the read/write data volume. Previously, the custom KMS key was only used to encrypt the data volume.