AWS msk documentation change
Summary
Replaced references to 'MSK Express brokers' with 'MSK Provisioned' throughout the migration guide.
Security assessment
Terminology update from 'Express brokers' to 'Provisioned' with no security-related content changes. Authentication methods (SASL/SCRAM, mTLS) remain unchanged.
Diff
diff --git a/msk/latest/developerguide/msk-replicator-migrate-external.md b/msk/latest/developerguide/msk-replicator-migrate-external.md index 7e44c23e1..d81596286 100644 --- a//msk/latest/developerguide/msk-replicator-migrate-external.md +++ b//msk/latest/developerguide/msk-replicator-migrate-external.md @@ -7 +7 @@ -# Migrate from non-MSK Apache Kafka clusters to Amazon MSK Express brokers +# Migrate from non-MSK Apache Kafka clusters to Amazon MSK Provisioned @@ -9 +9 @@ -You can use MSK Replicator to migrate Apache Kafka workloads from self-managed environments to Amazon MSK Provisioned clusters with Express brokers. MSK Replicator supports data migration from Kafka deployments (Kafka version 2.8.1 or later) that have SASL/SCRAM or mutual TLS (mTLS) authentication enabled. +You can use MSK Replicator to migrate Apache Kafka workloads from self-managed environments to Amazon MSK Provisioned clusters. MSK Replicator supports data migration from Kafka deployments (Kafka version 2.8.1 or later) that have SASL/SCRAM or mutual TLS (mTLS) authentication enabled. @@ -34 +34 @@ For detailed instructions, see [Set up prerequisites for MSK Replicator with sel -###### Step 1: Create an Amazon MSK Express cluster +###### Step 1: Create an Amazon MSK Provisioned cluster @@ -36 +36 @@ For detailed instructions, see [Set up prerequisites for MSK Replicator with sel -Create an MSK Provisioned cluster with Express brokers with IAM authentication enabled. Minimum three brokers across three AZs. See [Prepare the target cluster](./msk-replicator-prepare-clusters.html#msk-replicator-prepare-target). +Create an MSK Provisioned cluster with IAM authentication enabled. Minimum three brokers across three AZs. See [Prepare the target cluster](./msk-replicator-prepare-clusters.html#msk-replicator-prepare-target). @@ -56 +56 @@ Use `CreateReplicator` API with `EARLIEST` starting position, Identical topic na -Create a reverse Replicator from the MSK Express cluster back to the self-managed cluster for rollback capabilities. See [CreateReplicator API examples for self-managed Kafka clusters](./msk-replicator-external-api-examples.html). +Create a reverse Replicator from the MSK Provisioned cluster back to the self-managed cluster for rollback capabilities. See [CreateReplicator API examples for self-managed Kafka clusters](./msk-replicator-external-api-examples.html). @@ -83 +83 @@ Follow these steps to migrate your applications: - 2. Reconfigure producers to MSK Express cluster with IAM authentication + 2. Reconfigure producers to MSK Provisioned cluster with IAM authentication @@ -89 +89 @@ Follow these steps to migrate your applications: - 5. Reconfigure consumers to MSK Express cluster + 5. Reconfigure consumers to MSK Provisioned cluster @@ -96 +96 @@ Follow these steps to migrate your applications: -If bidirectional replication was configured, you can reverse the migration steps to roll back to the self-managed cluster. The reverse Replicator (MSK Express → External) will have been keeping the self-managed cluster in sync, so consumers can be redirected back without data loss. +If bidirectional replication was configured, you can reverse the migration steps to roll back to the self-managed cluster. The reverse Replicator (MSK Provisioned → External) will have been keeping the self-managed cluster in sync, so consumers can be redirected back without data loss.