Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News AWS Announces Amazon MQ Will Support RabbitMQ

AWS Announces Amazon MQ Will Support RabbitMQ

This item in japanese

AWS announced Amazon MQ will now support RabbitMQ, a popular open-source message broker. With the support for RabbitMQ, customers can migrate their existing RabbitMQ message brokers to AWS without rewriting code.

In 2017, AWS released Amazon MQ as a managed message broker service for Apache ActiveMQ, an open-sourced, enterprise-grade message broker compatible with most industry-standard protocols like JMS, NMS, AMQP 1.0 and 0-9-1, STOMP, MQTT, and WebSocket. Since then, the public cloud vendor enhanced the service with new features to improve high scalability and availability, such as vertical scaling, throughput-optimized message brokers with a 99.9% Service Level Agreement (SLA), and LDAP Authentication and Authorization support. The company now expands Amazon MQ with an additional message broker providing customers an option to reduce their operational overhead managing RabbitMQ message brokers by moving their existing brokers to AWS.

Users can create a new RabbitMQ message broker in AWS through Amazon MQ console, Command Line Interface (CLI), or SDK, and launch a new message broker in minutes. The RabbitMQ message broker instance offers native support for AMQP 0.9.1 protocol with client libraries for various platforms, including Ruby, Python, Node.js, .NET, and more. Furthermore, Amazon MQ currently supports RabbitMQ version 3.8.6 and has support for version upgrades.


In an AWS News Blog on Amazon MQ bringing support for RabbitMQ, Channy Yun, a principal developer advocate for AWS, wrote:

Not only ActiveMQ, but RabbitMQ is also one of the most popular open-source message brokers and a critical component of distributed applications, like commodities trading and order processing software. Some customers choose RabbitMQ for its feature richness, active community support, and a broad range of supported clients and frameworks. However, RabbitMQ message brokers require significant investment in the expertise needed for creating and patching complex clustered deployments. Companies willing to change to a different broker, and to migrate to a managed service, had to invest weeks in changing their application.

Clemens Vasters, Microsoft messaging architect, stated in a tweet:

For a while, I was indeed worried that AWS would turn Amazon MQ into a serious, transactional, hyperscale AMQP message broker offering, but now it's clear that it's just a host for OSS broker projects without them being particularly principled about it.

And by principled, Clemens explains in another tweet:

Principled: Committing to a broker model and evolving it, maybe also contributing back into the client and/or server ecosystem, and getting involved in further protocol standardization efforts.

However, on a Hacker News thread, a respondent stated:

I've seen growing levels of AWS contribution back to upstream projects over the past four years. Teams start out by operating a piece of software at scale, whether it is Redis, Kubernetes, etc. After they have operated it for a while they discover the bugs or performance issues, or customers of the service complain about something. At that point the team now has enough real world experience with that software to begin to contribute back to upstream.

Currently, Amazon MQ for RabbitMQ is available in all AWS regions where Amazon MQ is available. More details and guidance is available on the landing page of Amazon MQ and the pricing page.

Rate this Article