Announcing in-place ZooKeeper-to-KRaft cluster upgrades for Amazon MSK
Amazon MSK ยท 2026-08-26
Actions
Technical Details
| Affected Versions | 3.9.x |
|---|---|
| Regions | all |
| Migration Required | Yes |
| Cost Impact | Neutral |
| IaC Impact | High |
What This Means
For DevOps Teams
Migrate your Amazon MSK clusters from ZooKeeper to KRaft by following the in-place upgrade workflow, ensuring your cluster is running Kafka 3.9.x, disabling ZooKeeper access, and monitoring the upgrade progress to minimize operational impact and ensure a smooth transition.
For Platform Teams
Adopt the in-place ZooKeeper-to-KRaft upgrade for Amazon MSK to streamline metadata management, reduce external dependencies, and enhance cluster resilience and scalability, leveraging AWS-managed transition and validation processes.
For Executives
Plan the migration of your Amazon MSK clusters from ZooKeeper to KRaft to modernize metadata management, enhance scalability, and prepare for future Kafka releases, ensuring minimal downtime and maintaining cluster availability during the upgrade process.
Source
Related Amazon MSK Updates
- Amazon MSK now supports configuring custom domain names for MSK Provisioned clusters (2026-08-17)
- AWS Glue Schema Registry is now available in ten more AWS regions (2026-08-06)
- Amazon MSK now delivers Kafka Authorizer Logs to customers (2026-08-06)
- Amazon MSK Express brokers now deliver data to streaming tables for Apache Iceberg (2026-07-30)
- Amazon MSK Express Brokers adds support for Apache Kafka version 4.2 (2026-07-15)