AWS Security ChangesHomeSearch

AWS msk: Clarify Prometheus targets for MSK brokers vs KRaft controllers

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

File: msk/latest/developerguide/set-up-prometheus-host.md

Summary

Rewrites the Prometheus host setup guidance to explain that 'Brokers only' targets apply to ZooKeeper-mode clusters, KRaft clusters on Apache Kafka 4.1+, and migrated clusters (which have no controller DNS endpoints), while controller DNS targets are only available for pre-4.1 KRaft clusters. Adds a note that controller metrics aren't needed for cluster health and points to CloudWatch metrics like ActiveControllerCount.

Security assessment

The change is purely about which Prometheus scrape targets to configure for broker vs controller nodes and which CloudWatch metrics to use for health monitoring. It corrects endpoint availability guidance but does not address a vulnerability, credential handling, encryption, or access control.

Evidence

+You don't need controller metrics to monitor the health of your cluster. Amazon MSK monitors and manages the KRaft controllers for you. For cluster-level health, use Amazon MSK CloudWatch metrics such as `ActiveControllerCount`. For more information, see [Amazon MSK metrics for monitoring Standard brokers with CloudWatch](./metrics-details.html) and [Amazon MSK metrics for monitoring Express brokers with CloudWatch](./metrics-details-express.html).

Diff

diff --git a/msk/latest/developerguide/set-up-prometheus-host.md b/msk/latest/developerguide/set-up-prometheus-host.md
index 9bfc0d1..6ec9324 100644
--- a//msk/latest/developerguide/set-up-prometheus-host.md
+++ b//msk/latest/developerguide/set-up-prometheus-host.md
@@ -39 +39 @@ This procedure describes how to set up a Prometheus host using a prometheus.yml
-ZooKeeper mode targets.json
+Brokers only
@@ -71 +71 @@ ZooKeeper mode targets.json
-KRaft mode targets.json
+Brokers and controllers
@@ -109 +109,5 @@ KRaft mode targets.json
-To scrape JMX metrics from KRaft controllers, add controller DNS names as targets in the JSON file. For example: `controller_dns_1:11001`, replacing `controller_dns_1` with the actual controller DNS name.
+Use the **Brokers only** targets for clusters in ZooKeeper mode. Also use them for KRaft clusters created on Apache Kafka version 4.1 or later, and for clusters migrated from ZooKeeper mode to KRaft mode. These clusters don't have controller DNS endpoints, and `ListNodes` doesn't return endpoints for their controller nodes.
+
+Only KRaft clusters created on Apache Kafka versions earlier than 4.1 have controller DNS endpoints, and they keep them after a version upgrade. For these clusters, you can optionally add the controller DNS names that `ListNodes` returns as targets. The **Brokers and controllers** tab shows an example.
+
+You don't need controller metrics to monitor the health of your cluster. Amazon MSK monitors and manages the KRaft controllers for you. For cluster-level health, use Amazon MSK CloudWatch metrics such as `ActiveControllerCount`. For more information, see [Amazon MSK metrics for monitoring Standard brokers with CloudWatch](./metrics-details.html) and [Amazon MSK metrics for monitoring Express brokers with CloudWatch](./metrics-details-express.html).