Amazon MSK Enables In-Place Migration from ZooKeeper to KRaft for Apache Kafka Clusters

Amazon Managed Streaming for Kafka added support to migrate existing Kafka clusters to the KRaft consensus protocol without new infrastructure or client reconfiguration.

By Adrian Cole · Editorial pseudonym · 2026-08-10 · 1 min read

AI-ASSISTED REPORTING · RETROSPECTIVE ARCHIVE

Retrospective edition: 2026-08-10. Source published: 2026-08-10. Added to this archive: 2026-11-03. This briefing was prepared later from the linked announcement; it was not published on this website on the historical edition date.

KRaft replaces the older ZooKeeper dependency by managing metadata internally within Kafka brokers as replicated topics, improving scalability and simplifying cluster architecture.

The migration process is available through MSK’s management interfaces and maintains cluster availability. Customers first upgrade to Kafka 3.9.x then migrate, easing transition ahead of Kafka 4.x which supports only KRaft, thereby future-proofing deployments across most AWS regions.

Source & further reading

Amazon MSK now supports in-place migration from Apache ZooKeeper to KRaft ↗

Source published 2026-08-10. This report was prepared with AI assistance from the linked primary-source material. Claims and limitations should be checked against the original announcement or research.