skills.rest
ricardolui
ricardoluiCOMMUNITY
Explore all skills by this author →
GitHub

msk-migration

Assess and plan migrations from AWS MSK to Confluent Cloud.

Updated Jul 7, 2026
Search Tags:#assessment#sizing#confluent cloud#kcp#aws msk#kafka migration#cluster linking
One-click install
npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill msk-migration-ricardolui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: msk-migration
Source: https://github.com/ricardolui/gcp-custom-agent-skills/tree/main/msk-migration
Command: npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill msk-migration-ricardolui

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Migrating from AWS MSK to Confluent Cloud requires environment discovery, sizing math, auth and networking decisions, and switchover planning that are easy to get wrong without structured guidance. This Skill turns a KCP scan or manual intake into a grounded assessment and technical migration plan. ## Core Features & Use Cases - Environment Assessment: Parse a KCP state file or manual migration profile to produce a scan-coverage audit, environment summary, topic-level readiness buckets, and a 17-row red flags checklist. - Technical Migration Plan: Generate a structured plan covering cluster type (Enterprise vs Dedicated), eCKU sizing, networking, auth migration paths, switchover approach, pre-migration workstream, risks, and open questions. - Grounded Q&A: Answer MSK-to-Confluent-Cloud concept and comparison questions with citations to live docs.confluent.io pages and the KCP repository. - Use Case: A platform engineer runs kcp discover and kcp scan clusters against their MSK fleet, hands the resulting state file to the Skill, and receives a red-flag audit plus a sizing and cluster-type recommendation for the target Confluent Cloud environment. ## Quick Start Ask the assistant to assess your MSK environment for migration to Confluent Cloud, either by providing a KCP state file or by describing your clusters manually.

Frequently Asked Questions about msk-migration

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

FAQPage Schema
How do I migrate from AWS MSK to Confluent Cloud?▼

Start with an assessment: scan your MSK environment with KCP (Confluent's open-source migration CLI) or describe it manually, then review red flags and build a technical plan covering cluster type, sizing, networking, auth, and switchover. Execution stages like Cluster Linking setup and cutover are done with Confluent's documented tooling and account team.

What is KCP and how does it scan an MSK environment?▼

KCP is Confluent's open-source command-line tool (github.com/confluentinc/kcp) for assessing AWS MSK environments and generating migration assets. It runs a sequence of commands — discover, scan clusters, scan schema-registry, scan client-inventory, report metrics, report costs — that append findings to a kcp-state.json file used for planning.

Should I choose Confluent Cloud Enterprise or Dedicated for my MSK migration?▼

Enterprise is the recommended default for MSK migrations. Escalate to Dedicated only when a hard limit triggers, such as projected eCKU exceeding the Enterprise cap, ACL count over the cap, VPC Peering or Transit Gateway requirements, or broker-side schema validation needs — verified against the live cluster-types documentation.

Does this migration approach work for non-MSK Kafka sources?▼

No. The skill is scoped to AWS MSK sources only, including MSK Provisioned and MSK Serverless. Migrations from open-source Kafka, Confluent Platform, Aiven, or Redpanda are out of scope, as are greenfield Confluent Cloud projects with no existing Kafka source.

Why did my KCP scan show zero topics on a private MSK cluster?▼

An empty topics list with populated cluster config usually means the deep scan silently failed due to private-network unreachability, not a zero-topic cluster. kcp scan clusters needs Kafka-protocol access from inside the VPC, via VPN, or Direct Connect; re-scan from a reachable host or use manual intake for the missing topic data.

Can the skill estimate what my Confluent Cloud migration will cost?▼

No dollar figures are produced. Pricing questions route to Confluent's public cost estimator for self-service list-price ranges, and deal-specific quotes go to the Confluent account team. Feature comparisons and cost line-item enumeration from KCP scans are supported.

Related Skills

Explore More Software Engineering Skills→
ms-moarms-moar

aws-cost-watchdog

Monitors AWS Cost Explorer, CloudWatch Bedrock usage metrics and budgets via CLI scripts.

Community
Intermediate
thititongumpunthititongumpun
1

confluent-kafka-admin

Administers Confluent and Kafka clusters covering provisioning, RBAC, networking, scaling, and disaster recovery.

Community
Advanced
ajurcenkajurcenk
1

redpanda-migrator

Generate Redpanda Migrator YAML configurations for Kafka-compatible cluster migrations.

Community
Advanced
diberrydiberry
1

azure-partner-solutions

Troubleshoot and configure Azure Partner Solutions like Confluent Kafka and Datadog.

Community
Intermediate