This capability simplifies RabbitMQ maintenance by preserving configuration, queues, exchanges, bindings, users, and policies during upgrades executed via the AWS console, CLI, or API. RabbitMQ 4.2 brings architectural changes including the removal of classic mirrored queues and adoption of the Khepri metadata store, requiring broker compliance with instance types and queue migration prior to upgrade.
While upgrades cause broker downtime, they eliminate complex data migrations, reducing operational overhead. Patch updates for RabbitMQ 4.2 brokers are managed automatically, easing ongoing maintenance for users leveraging Amazon MQ across supported regions.
Source & further reading
Amazon MQ now supports in-place major version upgrades for RabbitMQ 4 ↗Source published 2026-05-05. 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.