What problem does it solve? Migrating a self-managed Apache Kafka cluster to Amazon MSK Express requires knowing whether your topology, Kafka version, configs, authentication, and workload quotas are compatible, and what Express instance type and broker count you need. This Skill inventories your source cluster, runs a five-pillar compatibility assessment, and fills the AWS-published MSK Sizing/Pricing workbook to produce a concrete target specification. ## Core Features & Use Cases - Discovery: Builds a cluster-config.json inventory from IaC files (Terraform, CDK, CloudFormation, Kubernetes manifests, Docker Compose), Kafka CLI output, or manual input. - Compatibility Assessment: Validates the source against MSK Express across five pillars (topology, Kafka version, configs, auth, quotas) with INFO/ADVISORY/ACTION_REQUIRED verdicts anchored to AWS documentation. - Sizing & Costing: Computes six workload inputs and fills the AWS-published MSK Sizing/Pricing workbook so its formulas recommend instance type, broker count, and monthly cost. - Use Case: You run a self-managed Kafka cluster on Kubernetes and want to move to MSK Express. Point the Skill at your manifests to get a cluster inventory, then run the assessment to learn that your SASL/OAUTHBEARER auth needs remediation and which Express instance type fits your peak throughput. ## Quick Start Ask the assistant to assess your Kafka cluster for migration to MSK Express by pointing it at your infrastructure files or an existing cluster-config.json.
