AWS Security ChangesHomeSearch

AWS eks: EKS doc history: ACK capability config options, cross-namespace off by default

Service: eks · 2026-10-09 · Documentation medium

File: eks/latest/userguide/doc-history.md · Type: authz

Summary

Adds a changelog entry for new ACK capability type-specific configuration options, including the enableCrossNamespace setting (disabled by default) and the ability to disable controllers for specific ACK services.

Security assessment

The entry documents a security-relevant default: cross-namespace resource resolution by ACK controllers is disabled by default, reducing the risk of controllers accessing resources across namespace boundaries. It is new-feature documentation rather than a fix for a specific disclosed vulnerability.

Evidence

[ACK configuration options](https://docs.aws.amazon.com/eks/latest/userguide/create-ack-capability.html#ack-configuration-options)| The Amazon EKS capability for AWS Controllers for Kubernetes (ACK) now accepts type-specific configuration. You can control whether ACK controllers resolve cross-namespace resource references (`enableCrossNamespace`, which is disabled by default), and disable the controllers for specific ACK services (`disabledServices`), when you create or update a capability.

Diff

diff --git a/eks/latest/userguide/doc-history.md b/eks/latest/userguide/doc-history.md
index c44e0ed..186206e 100644
--- a//eks/latest/userguide/doc-history.md
+++ b//eks/latest/userguide/doc-history.md
@@ -24,0 +25 @@ Change| Description| Date
+[ACK configuration options](https://docs.aws.amazon.com/eks/latest/userguide/create-ack-capability.html#ack-configuration-options)| The Amazon EKS capability for AWS Controllers for Kubernetes (ACK) now accepts type-specific configuration. You can control whether ACK controllers resolve cross-namespace resource references (`enableCrossNamespace`, which is disabled by default), and disable the controllers for specific ACK services (`disabledServices`), when you create or update a capability. Turning services off is now the recommended way to run the capability alongside ACK controllers that you manage yourself, and to migrate to the capability one service at a time.| August 28, 2026