AWS Security ChangesHomeSearch

AWS msk: MSK Replicator quota guidance for bi-directional setups and SERs

Service: msk · 2026-11-04 · Documentation low

File: msk/latest/developerguide/msk-replicator-bp-quotas.md · Type: iam

Summary

Clarifies that Kafka quotas for MSK Replicator should be set on the source cluster, adds guidance to use two separate service execution roles for bi-directional replication and to apply quotas only on the corresponding source cluster, and rewords the warning about low consumer_byte_rate on the target cluster causing replication failure.

Security assessment

The change is operational guidance about Kafka quotas and IAM service execution roles for MSK Replicator. It touches IAM roles but describes correct configuration for replication to work, not a vulnerability, permission boundary, or credential exposure.

Evidence

+  * Use two separate service execution roles (SERs), one for each direction of replication. This makes sure that each Replicator works correctly and can access the internal topics that it creates on its target cluster.

Diff

diff --git a/msk/latest/developerguide/msk-replicator-bp-quotas.md b/msk/latest/developerguide/msk-replicator-bp-quotas.md
index 1d7e371..5e77203 100644
--- a//msk/latest/developerguide/msk-replicator-bp-quotas.md
+++ b//msk/latest/developerguide/msk-replicator-bp-quotas.md
@@ -11 +11 @@ Since MSK Replicator acts as a consumer for your source cluster, replication can
-You can set Kafka quotas for the Replicator on your source and target clusters to control how much capacity the MSK Replicator can use. A network bandwidth quota is recommended. A network bandwidth quota defines a byte rate threshold, defined as bytes per second, for one or more clients sharing a quota. This quota is defined on a per-broker basis.
+You can set Kafka quotas for the Replicator on your source cluster to control how much capacity the MSK Replicator can use. A network bandwidth quota is recommended. A network bandwidth quota defines a byte rate threshold, defined as bytes per second, for one or more clients sharing a quota. This quota is defined on a per-broker basis.
@@ -34,0 +35,9 @@ If you reuse a service execution role between multiple MSK Replicators, they are
+For a bi-directional setup, we recommend the following:
+
+  * Use two separate service execution roles (SERs), one for each direction of replication. This makes sure that each Replicator works correctly and can access the internal topics that it creates on its target cluster.
+
+  * For each SER, apply the quota only on the source cluster of the corresponding Replicator. If you must set a quota on the target cluster, make sure that it's higher than 10 MB/s to avoid impacting replication.
+
+
+
+
@@ -39 +48 @@ For more information on using MSK IAM authentication with quotas, see [Multi-ten
-Setting an extremely low `consumer_byte_rate` may cause your MSK Replicator to act in unexpected ways.
+Setting an extremely low `consumer_byte_rate` on the target cluster may cause MSK Replicator to behave unexpectedly and result in replication failure.