Amazon MSK Now Supports In-Place Migration from Apache ZooKeeper to KRaft
Amazon MSK now supports in-place migration from Apache ZooKeeper to KRaft, allowing customers to upgrade existing clusters without provisioning new infrastructure or reconfiguring client applications. This change eliminates the dependency on ZooKeeper for metadata management, storing it directly within Kafka brokers for improved scalability and a simplified architecture. The migration path facilitates upgrades to Kafka 4.x, which exclusively uses KRaft. This new capability is available today in most AWS regions, with the cluster remaining available throughout the process.
Features (1) ›
- In-place migration from Apache ZooKeeper to KRaft
Existing Amazon MSK clusters can now transition to KRaft without provisioning new infrastructure, migrating data, or reconfiguring client applications. KRaft improves scalability and simplifies architecture by managing metadata within Kafka brokers, removing the Apache ZooKeeper dependency. This also provides an easy path to upgrade to Kafka 4.x, which only supports KRaft.
https://aws.amazon.com/about-aws/whats-new/2026/08/aws-msk-zk-kraft-migration/
Related releases
- Amazon EC2 Marks 20 Years of Cloud Compute Innovation AWS News Blog ·
- GPU-accelerated Apache Spark on Amazon EMR with EC2 G7 instances runs up to 3.7x faster AWS Big Data Blog ·
- AWS Lambda functions now support full IAM resource-based policies AWS What's New ·
- Amazon MSK 3.7 reaches end of life in 7 days endoflife.date ·
- Amazon ECS adds automated agent connectivity detection and repair AWS What's New ·
- AWS Neuron 2.32 Enhances NKI, MXFP8 Training, and Variable-Size Collectives AWS What's New ·