AWS Security ChangesHomeSearch

AWS msk medium security documentation change

Service: msk · 2026-05-22 · Security-related medium

File: msk/latest/developerguide/msk-replicator-migrate-external.md

Summary

Clarified service execution role requirements for Secrets Manager/KMS and added API caller permission requirements during replicator creation.

Security assessment

Added inline permission requirements for Secrets Manager and KMS when using SASL/SCRAM or CMKs. Specifying these prevents secret access failures and potential data exposure. Mandating API caller permissions ensures proper authorization controls during replicator setup.

Diff

diff --git a/msk/latest/developerguide/msk-replicator-migrate-external.md b/msk/latest/developerguide/msk-replicator-migrate-external.md
index 7dc793bf6..e349a09d9 100644
--- a//msk/latest/developerguide/msk-replicator-migrate-external.md
+++ b//msk/latest/developerguide/msk-replicator-migrate-external.md
@@ -40 +40 @@ Create an MSK Provisioned cluster with Express brokers with IAM authentication e
-Attach `AWSMSKReplicatorExecutionRole` and `AWSSecretsManagerClientReadOnlyAccess` managed policies. Configure trust policy for `kafka.amazonaws.com`. See [Set up prerequisites for MSK Replicator with self-managed Apache Kafka clusters](./msk-replicator-external-prereqs.html).
+Attach the `AWSMSKReplicatorExecutionRole` managed policy and configure the trust policy for `kafka.amazonaws.com`. Add inline permissions for AWS Secrets Manager (and AWS KMS if your secrets are CMK-encrypted) per [Additional SER permissions for SASL/SCRAM and customer managed keys](./msk-replicator-ser-additional-perms.html). See [Set up prerequisites for MSK Replicator with self-managed Apache Kafka clusters](./msk-replicator-external-prereqs.html).
@@ -52 +52 @@ Create secret with `username`, `password`, and `certificate` key-value pairs. Se
-Use `CreateReplicator` API with `EARLIEST` starting position, Identical topic name replication, and `synchroniseConsumerGroupOffsets` set to `true`. If you plan to set up bidirectional replication for rollback capability (Step 6), also set `consumerGroupOffsetSyncMode` to `ENHANCED` on both the forward and reverse Replicators. Allow approximately 30 minutes for the Replicator to reach RUNNING status. See [CreateReplicator API examples for self-managed Kafka clusters](./msk-replicator-external-api-examples.html).
+Use `CreateReplicator` API with `EARLIEST` starting position, Identical topic name replication, and `synchroniseConsumerGroupOffsets` set to `true`. The IAM principal that calls `CreateReplicator` must have the API caller permissions described in [IAM permissions required to create an MSK Replicator](./msk-replicator-create-iam-perms.html). If you plan to set up bidirectional replication for rollback capability (Step 6), also set `consumerGroupOffsetSyncMode` to `ENHANCED` on both the forward and reverse Replicators. Allow approximately 30 minutes for the Replicator to reach RUNNING status. See [CreateReplicator API examples for self-managed Kafka clusters](./msk-replicator-external-api-examples.html).