What is Amazon MQ?

Amazon MQ is a managed message broker service for Apache ActiveMQ Classic and RabbitMQ that manages the setup, operation, and maintenance of message brokers. You can create a new Amazon MQ broker using industry standard messaging protocols, or migrate existing message brokers to Amazon MQ without rewriting messaging code.

A broker is a message broker environment running on Amazon MQ. It is the basic building block of Amazon MQ. A message broker allows software applications and components to communicate using various programming languages, operating systems, and formal messaging protocols. You can use Amazon MQ brokers for communication between large scale, cloud native applications and components.

Amazon MQ features

Managed maintenance and version upgrades

Amazon MQ performs maintenance and version upgrades for a message broker during your scheduled maintenance window.

Monitor brokers with CloudWatch

Amazon MQ is integrated with Amazon CloudWatch so you can view and analyze metrics for your brokers and queues. You can view and analyze metrics from the Amazon MQ console, the CloudWatch console, command line, and API. Metrics are automatically collected and pushed to CloudWatch every minute.

Security

Amazon MQ provides encryption of your messages at rest and in transit. Connections to the broker use SSL, and access can be restricted to a private endpoint within your Amazon VPC. Additonality, you can use AWS Identity and Access Management (IAM) to control the actions your IAM users and groups can take on specific Amazon MQ brokers.

Quorum queues for RabbitMQ on Amazon MQ

Quorum queues are a replicated queue type made up of a leader node (primary replica) and follower nodes (other replicas). Each node is in a different availability zone, so if one node is temporarily unavailable, message delivery continues with a newly elected leader replica in another availability zone. Quorum queues are useful for handling poison messages, which occur when a message fails and is requeued multiple times.

Cross-Region data replication for ActiveMQ on Amazon MQ

Cross-Region data replication (CRDR) allows for asynchronous message replication from the primary broker in a primary AWS Region to the replica broker in a replica Region. By issuing a failover request to the Amazon MQ API, the current replica broker is promoted to the primary broker role, and the current primary broker is demoted to the replica role.

How can I get started with Amazon MQ?

To get started with ActiveMQ on Amazon MQ, review the following documentation:

• Getting started: Creating and connecting to an ActiveMQ broker

• Deployment options for Amazon MQ for ActiveMQ brokers

• ActiveMQ tutorials

• Amazon MQ for ActiveMQ best practices

To get started with RabbitMQ on Amazon MQ, review the following documentation:

• Getting started: Creating and connecting to a RabbitMQ broker

• Deployment options for Amazon MQ for RabbitMQ brokers

• RabbitMQ tutorials

• Amazon MQ for RabbitMQ best practices

To learn about Amazon MQ REST APIs, see the Amazon MQ REST API Reference.

To learn about Amazon MQ AWS CLI commands, see Amazon MQ in the AWS CLI Command Reference.

How can I provide feedback to Amazon MQ?

We welcome and encourgae your feedback on the documentation. You can use the thumbs up and thumbs down icons on the right hand side to submit feedback, or you can use the "Provide feedback" form linked below.

To contact the Amazon MQ team, use the Amazon MQ Discussion Forum.