← Back to all announcements
★★★★☆ 22/06/2026

Amazon MSK now offers AI Agent Skills to help developers operate MSK efficiently and accelerate migrations to MSK

AI coding agents can now guide MSK sizing, troubleshooting, and Kafka migrations—no Kafka expertise required.

View original announcement →

Visual Summary

graph TD A{{MSK AI Agent Skills}}:::announced B((Developer)):::external C([Agent Toolkit for AWS]):::feature D(AWS MCP Server):::compute E(Kiro / Claude Code / Cursor):::compute F([Troubleshooting & Sizing]):::feature G([Migration Guidance]):::feature H(Amazon MSK Express):::storage I(AWS CLI):::compute B ==>|"asks question"| E E ==>|"loads skills"| A A -->|"delivered via"| C C -->|"connects to"| D B -->|"configures"| I I -->|"sets up"| C A -->|"guides"| F A -->|"accelerates"| G G -.->|"migrates to"| H classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0 classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32 classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100 classDef external fill:#f5f5f5,stroke:#616161,color:#616161

What's New

Amazon MSK now offers AI Agent Skills, a set of curated guidance packages that plug into popular AI coding assistants to provide expert, up-to-date operational knowledge for Amazon MSK. The skills cover common tasks including troubleshooting, cluster sizing, configuration, monitoring, and migrating external Kafka workloads to MSK Express. They are delivered through the Agent Toolkit for AWS and work with Kiro, Claude Code, and Cursor without requiring developers to change their existing tooling.

How It Works

  • Agent Toolkit for AWS acts as the delivery mechanism, providing AI coding agents with secure access to AWS services, up-to-date documentation, and curated skills via the Model Context Protocol (MCP) through a single managed endpoint.
  • MSK Agent Skills are packaged as curated bundles of instructions, code scripts, and reference materials; agents discover and load only the skills relevant to the current task, avoiding unnecessary context consumption.
  • Setup is CLI-driven: running aws configure agent-toolkit launches an interactive wizard that detects installed agents (Kiro, Cursor, Claude Code), installs default AWS skills, and configures the AWS MCP Server in one step; AWS CLI version 2.35.0 or later is required.
  • Individual skill management is available via aws agent-toolkit add-skill, update, remove, list, and search commands, with options to target a specific agent or pin a skill version.
  • IAM-based authentication controls execution of AWS API calls and Python scripts, while documentation search and service information retrieval require no authentication, preserving security boundaries.
  • Natural-language interaction is the primary interface: developers ask their coding agent questions like "What broker type and size should I use?" and the skill provides step-by-step, context-aware guidance drawn from authoritative MSK documentation.

Why It's Important

  • Democratizes MSK expertise: operational tasks that previously required deep Kafka and MSK knowledge—sizing, tuning, troubleshooting—can now be completed by developers without specialized backgrounds, reducing dependency on platform engineers.
  • Accelerates MSK Express adoption: the skills provide guided migration paths from self-managed or third-party Kafka clusters to MSK Express, which offers up to 3× more throughput per broker, 20× faster scaling, and 90% faster recovery compared to Standard Apache Kafka brokers.
  • Reduces operational risk: AI-guided, guardrail-enforced workflows lower the chance of misconfiguration that commonly occurs when agents attempt complex multi-step AWS tasks without curated context.
  • Keeps guidance current: skills are loaded on demand from a managed server, meaning developers always receive up-to-date best practices rather than relying on potentially stale model training data.
  • Fits existing developer workflows: compatibility with Kiro, Claude Code, and Cursor means teams adopt the capability without tool sprawl or retraining.

How It's Different

  • Skill-based context injection vs. generic LLM knowledge: unlike asking a general-purpose AI assistant about Kafka, MSK skills deliver authoritative, AWS-curated instructions that reflect current service capabilities and limits rather than training-data snapshots.
  • On-demand loading vs. always-on context: skills are fetched only when relevant, so they do not bloat the agent's context window—a meaningful advantage over approaches that pre-load large documentation corpora.
  • Integrated with IAM and CloudWatch: the underlying MCP Server enforces IAM-based access controls and emits CloudWatch metrics, giving enterprises the auditability and governance they require—something ad-hoc prompt engineering cannot provide.
  • MSK Express migration focus: the skills are specifically tuned to assess compatibility with and guide migration to MSK Express, a serverless-style broker tier not yet widely covered by general AI training data.
  • Single CLI setup path: aws configure agent-toolkit handles multi-agent detection and configuration in one command, whereas competing approaches typically require per-tool manual MCP configuration.

When to Prefer It

  • Migrating from self-managed Kafka: use the MSK skills to assess cluster compatibility with MSK Express and receive a step-by-step migration plan, reducing the risk of downtime or data loss during cutover.
  • Right-sizing a new MSK cluster: when you need to choose broker type, instance size, and storage configuration without a dedicated Kafka architect on the team, the skills provide guided recommendations based on workload parameters.
  • Troubleshooting production issues: when a cluster exhibits high consumer lag, under-replicated partitions, or broker instability, ask your coding agent for a diagnostic walkthrough rather than searching scattered documentation.
  • Onboarding new developers to MSK: teams ramping up engineers unfamiliar with Kafka operations can use the skills as an interactive learning and execution tool, shortening time-to-productivity.
  • Standardizing operational runbooks: platform teams can enforce consistent procedures across squads by having all developers use the same skill-guided workflows rather than tribal knowledge.
  • Evaluating MSK Express performance benefits: before committing to a migration, use the skills to model expected throughput, scaling, and recovery improvements against your current workload profile.

Availability

  • General Availability: announced June 22, 2026; the MSK AI Agent Skills are generally available.
  • Supported AI coding agents: Kiro, Claude Code, and Cursor; the Agent Toolkit CLI also lists Codex as a supported agent for other skills.
  • Prerequisites: AWS CLI version 2.35.0 or later must be installed; one or more supported coding agents must be present on the developer's machine.
  • Skill installation scope: skills are installed globally to agent configuration directories (e.g., ~/.kiro), not per project.
  • Pricing: the Agent Toolkit for AWS documentation indicates pricing details are available in the toolkit user guide; no additional MSK-specific skill licensing fee is mentioned in the announcement.
  • Regional availability: no region restrictions are called out in the announcement; availability is expected to follow standard MSK and AWS CLI regional support, but customers should verify in the AWS Regional Services table.
  • Limitations: skills require IAM credentials for API execution; documentation search is unauthenticated but read-only; skill guidance is specific to MSK and does not cover self-managed Kafka environments.

Tags

Servicesother-aws
Typenew-featureintegration
Conceptsagentic-aicoding-assistant
Use Casesdeveloper-toolsdevopsmigrationopen-source
Providersanthropic
GeographyGlobal

Related Resources

AI Radar AWS

AWS AI/ML news — curated, researched, explained

An automated intelligence platform that curates, researches, and analyzes AWS AI/ML/GenAI announcements daily. Every report is backed by real research — the system reads linked blog posts and documentation to provide accurate, in-depth analysis.

How Each Report Is Generated

  1. Collection — Daily monitoring of the AWS "What's New" RSS feed
  2. Filtering — AI-powered relevance detection for AI/ML/GenAI topics
  3. Taxonomy Tagging — LLM-based classification across 6 dimensions
  4. Importance Scoring — Point-based system with tag bonuses (1-5 stars)
  5. Research Phase — Follows links to blog posts and documentation
  6. Report Generation — Claude Sonnet produces structured 6-section analysis
  7. Visual Summary — Claude Opus generates Mermaid diagrams for key items
  8. Publishing — Static website rebuilt and deployed via CloudFront

Features

  • Faceted filtering by service, type, concept, and more
  • Multi-dimensional taxonomy with 80+ tags across 6 dimensions
  • Geographic availability badges (Global, APJ, EMEA, AMER) with filtering
  • Timeline visualization of announcement volume
  • PDF export for offline reading
  • Mermaid visual summaries for key announcements
  • Daily automated updates — no manual curation
What makes this different: Each report involves a dedicated research phase where the system reads linked blog posts and AWS documentation pages. This produces analysis that goes beyond the original announcement text.

Technology

Built with Python, AWS Lambda, Amazon Bedrock (Claude Sonnet 4.6, Opus 4.6, Haiku 4.5), S3, CloudFront, WAF, EventBridge, and CDK.

Open Source

This project is open source. Fork it, customize it for your needs, and deploy your own instance.
📦 github.com/bbonik/ai-radar-aws

How Importance Scoring Works

Each announcement receives a point score based on multiple factors. The total score maps to a 1-5 star rating:

1★ < 2 pts 2★ ≥ 2 pts 3★ ≥ 3.5 pts 4★ ≥ 5 pts 5★ ≥ 6.5 pts

Point Breakdown

FactorPointsWhen
Core AI service (Bedrock, AgentCore, SageMaker AI)+4Service named in title
Key AI service (SageMaker, Kiro, QuickSight)+2Service named in title
Other AI-related service+1Default
Blog post link+3Link to aws.amazon.com/blogs/
GitHub samples link+2Link to github.com/aws*
Documentation link+1Link to docs.aws.amazon.com/
New model+1.5Tagged as "new-model"
New service+1Tagged as "new-service"
New feature+0.5Tagged as "new-feature"
Anthropic / OpenAI provider+2Provider explicitly mentioned
Instance / notebook announcement-2Hardware/capacity, not feature
Performance / pricing / security-0.5Incremental updates
Region expansion to APJ+1Expands to Asia Pacific
Region expansion (non-APJ only)-1.5Only expands to other regions

Geographic Relevance Badges

Each announcement card shows a small badge indicating whether the feature is available in your region:

🌐 Global Available in all regions
🌏 APJ Asia Pacific
🌍 EMEA Europe / Middle East / Africa
🌎 AMER Americas (US, Canada, South America)
No badge Geography unknown
How geography is detected: The system detects ALL geographies mentioned in each announcement. If the text mentions specific regions (Tokyo, Frankfurt, Oregon, etc.), the corresponding geography badges are shown. If it says "all regions" or is a new feature with no region specified, it gets the Global badge. Geography is also filterable — click a geo chip to see only announcements available in that region.