Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Managing Amazon MQ for RabbitMQ engine versions

RabbitMQ organizes version numbers according to semantic versioning specification as X.Y.Z. In Amazon MQ for RabbitMQ implementations, X denotes the major version, Y represents the minor version, and Z denotes the patch version number. Amazon MQ considers a version change to be major if the major version numbers change. For example, upgrading from version 3.13 to 4.0 is considered a major version upgrade. A version change is considered minor if only the minor or patch version number changes. For example, upgrading from version 3.11.28 to 3.12.13 is considered a minor version upgrade.

Amazon MQ for RabbitMQ recommends all brokers use the latest supported minor version. For instructions on how to upgrade your broker engine version, see Upgrading an Amazon MQ broker engine version.

Supported engine versions on Amazon MQ for RabbitMQ

The Amazon MQ version support calendar indicates when a broker engine version will reach end of support. When a version reaches end of support, Amazon MQ upgrades all brokers on this version to the next supported version automatically. You cannot create new brokers on versions scheduled for end of support within 30 days of the end of support date. You also cannot unschedule an upgrade from a version in end of support to a supported version.

Amazon MQ provides at least a 90 day notice before a version reaches end of support.

When you create a new Amazon MQ for RabbitMQ broker, you can specify any supported RabbitMQ engine version. If you use the Amazon Web Services Management Console to create a broker, Amazon MQ automatically defaults to the latest engine version number. If you use the Amazon CLI or the Amazon MQ API to create a broker, the engine version number is required. If you don't provide a version number, the operation will result in an exception. To learn more, see create-broker in the Amazon CLI Command Reference and CreateBroker in the Amazon MQ REST API Reference.

Engine version upgrades

You can manually upgrade your broker at any time to the next supported major or minor version. When you turn on automatic minor version upgrades, Amazon MQ will upgrade your broker to the latest supported patch version during the maintenance window.

For more information about manually upgrading your broker, see Upgrading an Amazon MQ broker engine version.

For all brokers using engine version 3.13 and above, Amazon MQ manages upgrades to the latest supported patch version during the maintenance window.

Single instance brokers will be offline while being rebooted. For cluster brokers, the mirrored queues must be synced during reboot. With longer queues, the queue-sync process can take longer. During the queue-sync process, the queue is unavailable to consumers and producer. When the queue-sync process is complete, the broker becomes available again. To minimize the impact, we recommend upgrading during a low traffic time. For more information on best practices for version upgrades, see Amazon MQ for RabbitMQ best practices.

Listing supported engine versions

You can list all supported minor and major engine versions by using the describe-broker-instance-options Amazon CLI command.

aws mq describe-broker-instance-options

To filter the results by engine and instance type use the --engine-type and --host-instance-type options as shown in the following.

aws mq describe-broker-instance-options --engine-type engine-type --host-instance-type instance-type

For example, to filter the results for RabbitMQ, and mq.m5.large instance type, replace engine-type with RABBITMQ and instance-type with mq.m5.large.