AWS Security ChangesHomeSearch

AWS msk: Note lack of controller DNS endpoints after ZooKeeper-to-KRaft migration

Service: msk · 2026-10-23 · Documentation low

File: msk/latest/developerguide/zk-to-kraft-migration.md

Summary

Updates post-migration notes to state that MSK does not create DNS endpoints for KRaft controllers of a migrated cluster, so controller JMX metrics are unavailable via open monitoring, and advises scraping only broker endpoints. Also changes a related link label to 'Kafka cluster ID for KRaft clusters'.

Security assessment

The edit documents monitoring endpoint behavior after a migration and recommends scraping only broker endpoints. It is operational/monitoring guidance with no security control, vulnerability fix, or exposure implication.

Evidence

+  * Amazon MSK doesn't create DNS endpoints for the KRaft controllers of a migrated cluster, so controller JMX metrics aren't available through open monitoring.

Diff

diff --git a/msk/latest/developerguide/zk-to-kraft-migration.md b/msk/latest/developerguide/zk-to-kraft-migration.md
index e7781e4..b81cad4 100644
--- a//msk/latest/developerguide/zk-to-kraft-migration.md
+++ b//msk/latest/developerguide/zk-to-kraft-migration.md
@@ -101 +101 @@ After the migration completes:
-  * You can view KRaft controller endpoints using the `ListNodes` API if you need them for open monitoring.
+  * Amazon MSK doesn't create DNS endpoints for the KRaft controllers of a migrated cluster, so controller JMX metrics aren't available through open monitoring.
@@ -105,0 +106,2 @@ After the migration completes:
+If you use open monitoring, scrape only your broker endpoints. You don't need controller metrics to monitor the health of your cluster. For more information, see [Monitor an MSK Provisioned cluster with Prometheus](./open-monitoring.html).
+
@@ -112 +114 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Metadata management
+Kafka cluster ID for KRaft clusters