AWS msk documentation change
Summary
Added details about an optional simulation phase that provisions temporary MSK Express clusters and EC2 fleets for load testing, including cost warnings and resource requirements.
Security assessment
The changes describe a new simulation feature for performance testing, not security vulnerabilities. No evidence of security fixes or vulnerabilities addressed. Focuses on operational testing and cost management.
Diff
diff --git a/msk/latest/developerguide/msk-replicator-migrate-ai-assist.md b/msk/latest/developerguide/msk-replicator-migrate-ai-assist.md index 1da0bb51f..f1506ab49 100644 --- a//msk/latest/developerguide/msk-replicator-migrate-ai-assist.md +++ b//msk/latest/developerguide/msk-replicator-migrate-ai-assist.md @@ -11 +11 @@ How the skill worksSkill outputs -You can use the migrate-to-msk AI skill to assess your source cluster's compatibility with Amazon MSK Express and generate a right-sized target cluster recommendation before you begin migration. The skill simplifies the analysis that you would otherwise perform manually by comparing your Apache Kafka configuration against Express requirements. +You can use the migrate-to-msk AI skill to assess your source cluster's compatibility with Amazon MSK Express and generate a right-sized target cluster recommendation before you begin migration. The skill simplifies the analysis that you would otherwise perform manually by comparing your Apache Kafka configuration against Express requirements. You can also run an optional simulation that deploys a temporary Express cluster at your target size and drives a synthetic load at a throughput you choose, so you can see how that cluster behaves under load before you migrate. @@ -22,0 +23,2 @@ To use the migrate-to-msk skill, you need the following: + * For the optional Simulation phase only: an AWS account with the AWS CLI configured and permissions to deploy the simulation resources (an MSK Express cluster, an EC2 load-generation fleet, IAM roles, a VPC, and a CloudWatch dashboard). This phase creates real resources in your account; the Discovery and Assessment phases need no AWS access. + @@ -47 +49 @@ The skill guides you through the process interactively by gathering information -The skill provides a two-phase assessment of your migration path. It does not make API calls to your cluster or modify your infrastructure. All analysis runs locally on data that you provide, and all outputs are saved to your working directory. +The skill provides three phases: Discovery, Assessment, and an optional Simulation. The Discovery and Assessment phases do not make API calls to your cluster or modify your infrastructure — all analysis runs locally on the data that you provide, and all outputs are saved to your working directory. The optional Simulation phase is different: after you confirm the target account and consent to the deployment, it provisions temporary resources in your AWS account so you can measure how an Express cluster of your target size performs under a synthetic load. @@ -91,0 +94,19 @@ Each pillar produces one of the following finding types: +###### Phase 3: Simulation (optional) + +The skill can provision a temporary, isolated MSK Express cluster and a load-generation client fleet in your AWS account so you can see how an Express cluster of your target size behaves under load before you migrate. This phase is optional and runs only after you confirm the target account and explicitly consent to the deployment. Only one simulation can exist per account at a time. + +###### Important + +The Simulation phase deploys real resources in your AWS account — an MSK Express cluster and an EC2 fleet — that continue to incur charges until you delete them. When you finish, ask the skill to tear down the simulation, or delete its CloudFormation stack yourself, to stop incurring cost. + +You choose the cluster sizing — Express instance type, broker count, and Kafka version — from your assessment results or directly. The skill deploys the cluster and fleet, and you install a Kafka client that you provide. You then run one of two tests: + + * **End-to-End Latency** — Producers drive a steady target throughput while the skill samples produce-to-consume round-trip latency. + + * **Broker Restart Under Load** — The cluster sustains target throughput while one broker is rebooted, so you can observe failover behavior and recovery. + + + + +The skill creates an Amazon CloudWatch dashboard where the test metrics — cluster throughput, broker health, client-side latency, and consumer lag — appear. You interpret the results against your own performance targets. + @@ -108,0 +130,2 @@ Use these artifacts to plan your migration timeline, estimate costs, and identif +If you run the optional Simulation phase, it instead deploys an AWS CloudFormation stack (the Express cluster, load-generation fleet, and supporting resources) and an Amazon CloudWatch dashboard in your account, rather than writing local files. +