AWS msk documentation change
Summary
Title changed from 'Migrate from one Amazon MSK cluster to another using MSK Replicator' to 'Migrate between Amazon MSK clusters'. Added clarification that migration is supported between clusters in the same AWS account.
Security assessment
These are editorial changes and scope clarifications. The addition of 'in the same AWS account' clarifies the supported configuration but doesn't indicate a security fix or vulnerability. No security-related content was added or modified.
Diff
diff --git a/msk/latest/developerguide/msk-replicator-migrate-cluster.md b/msk/latest/developerguide/msk-replicator-migrate-cluster.md index e45e68c04..f3ec7705f 100644 --- a//msk/latest/developerguide/msk-replicator-migrate-cluster.md +++ b//msk/latest/developerguide/msk-replicator-migrate-cluster.md @@ -7 +7 @@ -# Migrate from one Amazon MSK cluster to another using MSK Replicator +# Migrate between Amazon MSK clusters @@ -9 +9 @@ -You can use Identical topic name replication for cluster migration, but your consumers must be able to handle duplicate messages without downstream impact. This is because MSK Replicator provides at-least-once replication, which can lead to duplicate messages in rare scenarios. If your consumers meet this requirement, follow these steps. +Amazon MSK Replicator supports migrations between Amazon MSK clusters in the same AWS account. You can use Identical topic name replication for cluster migration, but your consumers must be able to handle duplicate messages without downstream impact. This is because MSK Replicator provides at-least-once replication, which can lead to duplicate messages in rare scenarios. If your consumers meet this requirement, follow these steps. @@ -13 +13 @@ You can use Identical topic name replication for cluster migration, but your con - 2. Configure cluster-level settings and permissions on the new cluster. You do not need to configure topic-level settings and “literal” read ACLs, as MSK Replicator automatically copies them. + 2. Configure cluster-level settings and permissions on the new cluster. You do not need to configure topic-level settings and "literal" read ACLs, as MSK Replicator automatically copies them. @@ -15 +15 @@ You can use Identical topic name replication for cluster migration, but your con - 3. Monitor the `MessageLag` metric in Amazon CloudWatch until it reaches 0 which indicates all data has been replicated. + 3. Monitor the `MessageLag` metric in Amazon CloudWatch until it reaches 0, which indicates all data has been replicated. @@ -36 +36 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Create an active-active setup +Migration @@ -38 +38 @@ Create an active-active setup -Migrate from self-managed MirrorMaker2 to MSK Replicator +Migrate from self-managed Kafka