migrate-to-msk

Assess and migrate self-managed Apache Kafka clusters to Amazon MSK Express.

Updated Jul 21, 2026
Ready to run
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill migrate-to-msk-richardnroman
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: migrate-to-msk
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/migrate-to-msk
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill migrate-to-msk-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Migrating a self-managed Apache Kafka cluster to Amazon MSK Express requires inventorying brokers, topics, configs, and security settings, then checking them against Express's compatibility rules and sizing constraints — a manual, error-prone process. ## Core Features & Use Cases - Discovery: Builds a cluster-config.json inventory from IaC files (Terraform, CDK, Docker Compose, Kubernetes), Kafka CLI output, or manual input. - Compatibility Assessment: Runs a five-pillar check (topology, Kafka version, configs, auth, quotas) against MSK Express rules and emits INFO/ADVISORY/ACTION_REQUIRED verdicts. - Sizing & Costing: Fills the AWS-published MSK Sizing/Pricing workbook with workload inputs to produce broker count and monthly cost recommendations. - Simulation: Optionally deploys a temporary MSK Express cluster with load-testing infrastructure and a CloudWatch dashboard. - Use Case: A platform team with an on-premises Kafka 3.6 cluster points the skill at their Terraform directory, receives a compatibility report flagging an unsupported Kerberos auth mechanism, and gets a filled sizing workbook recommending an Express instance type. ## Quick Start Ask the assistant to migrate your Kafka cluster to MSK Express and point it at your infrastructure code directory to start discovery.

Frequently Asked Questions about migrate-to-msk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a self-managed Kafka cluster to Amazon MSK Express?▼

Run the three-phase flow: discovery builds a cluster-config.json inventory from your IaC files or Kafka CLI output, assessment checks compatibility and fills the AWS sizing workbook, and an optional simulation deploys a test Express cluster. Data replication uses MSK Replicator.

What Kafka versions does MSK Express support?▼

MSK Express supports Apache Kafka versions 3.6, 3.8, and 3.9. Other versions trigger an advisory to validate client compatibility, and sources older than 2.8.1 cannot use MSK Replicator for data migration and need MirrorMaker 2 instead.

Which authentication mechanisms work with MSK Express?▼

MSK Express supports unauthenticated access, TLS client certificates, SASL/SCRAM via Secrets Manager, and IAM authentication. Custom SASL/OAUTHBEARER providers and mechanisms like Kerberos or SASL/PLAIN are not supported and require client changes before migrating.

Can I migrate from MSK Provisioned to MSK Express with this skill?▼

No. The skill covers only migrations from self-managed Apache Kafka (on-premises, EC2, Docker, Kubernetes) to MSK Express. MSK Standard (Provisioned) to Express migrations are explicitly out of scope.

Why does the sizing workbook show blank cost recommendations?▼

The recommendation and cost cells are spreadsheet formulas that populate when the filled workbook is opened in Excel, LibreOffice, or Google Sheets. The script sets fullCalcOnLoad so recalculation happens automatically; if disabled, trigger a manual recalculation.