Migrating to Amazon MQ for RabbitMQ - Amazon MQ
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).

Migrating to Amazon MQ for RabbitMQ

Amazon MQ supports migration from self managed Classic Mirrored Queues to Amazon MQ managed Classic Mirrored Queues on all supported cluster instances running RabbitMQ version 3.10.x or higher.

You can export the configuration from your self-managed RabbitMQ cluster and import it into Amazon MQ for RabbitMQ. Queue, exchange, user, and policy definitions are imported. You can edit the exported JSON from the existing RabbitMQ cluster to remove the definitions that are not supported. The current default queue type is Classic Mirrored Queues. We recommend Customers use the latest Amazon MQ for RabbitMQ supported version when using Classic Mirrored Queues.


Amazon MQ for RabbitMQ has an enforced policy of ha-mode=all and ha-sync-mode=automatic which will override any custom policy.


Complete the following prerequisites before migrating to Amazon MQ for RabbitMQ:

Exporting definitions

To export the definitions from a self-managed RabbitMQ cluster and import them into Amazon MQ for RabbitMQ, do the following:

  1. Go to the RabbitMQ console of your existing self-managed cluster by signing on to any of the brokers. Choose the overview tab, then select Export Definitions to produce a link to export the definition.

  2. Next, login to the Amazon MQ RabbitMQ console. Navigate to the existing broker you would like to apply the configurations to. Click on the overview tab, then click import definitions to upload the configuration file that you exported in the previous step.

  3. Once the configuration file is imported, you can view all the queues and exchange definitions that were defined in the self-managed broker.

Moving existing messages to your new Amazon MQ managed broker

Amazon MQ for RabbitMQ currently supports the Federation and Shovel plugins for moving messages from a self-managed RabbitMQ broker to an Amazon MQ for RabbitMQ broker.


The Shovel plugin is used to move messages from an on-premises RabbitMQ broker without internet access to a private Amazon MQ managed broker. The Shovel plug in is configured on the on-premises broker to push messages to the Amazon MQ managed broker. Using the Shovel plug in requires a VPN connection between the Amazon Managed VPC and the on-premises network. For more information on using the Shovel plug in, see How do I set up the RabbitMQ Shovel plugin on my Amazon MQ broker?


The Federation plugin facilitates moving messages from a public upstream broker to a downstream broker. The plugin is configured on the downstream broker, which in this case is the new Amazon MQ for RabbitMQ broker created in the previous section. For more information on using the RabbitMQ federation plug in, see the RabbitMQ Federation Plugin documentation.

Additional resources


When you create a new Amazon MQ for RabbitMQ broker, you can specify any supported RabbitMQ engine version. The different engine versions support certain features. For optimal performance, we suggest using the latest engine version.


The broker instance type determines system throughput. Before migrating, review the sizing documentation to determine the best broker instance type for your application.


Amazon MQ for RabbitMQ brokers, configurations, users, data storage, and API throttling have default limits. To request an increase for a limit, see Amazon Service Quotas in the Amazon Web Services General Reference.

Best practices

Learn more about ensuring effective performance in all areas of your RabbitMQ application by reviewing the RabbitMQ best practices documentation.