# Amazon MQ

Cloud service · AWS. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-services-hub/amazon-mq

> Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easy to set up and operate message brokers in the cloud, facilitating the integration of different software systems and components.

Practice exams covering Amazon MQ: [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C02 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 5 key features of Amazon MQ

Amazon MQ is a managed message broker service that supports industry-standard messaging protocols such as MQTT, AMQP, and STOMP, enabling secure and scalable communication between distributed software components and microservices.

1. **Managed Service**: Amazon MQ is a managed messaging service for Apache ActiveMQ and RabbitMQ that makes it easy to set up and operate message brokers in the cloud. It manages the administration and maintenance tasks, allowing developers to focus on their application logic.
2. **High Availability**: Amazon MQ supports multi-AZ high availability through three-node RabbitMQ clusters and ActiveMQ active/standby deployments.
3. **Security**: Amazon MQ integrates with AWS Identity and Access Management (IAM), allowing you to control access to your message brokers. It also supports encryption at rest and in-transit to ensure that your messages are securely transferred and stored.
4. **Easy Integration**: With Amazon MQ, you can quickly migrate your existing applications that use message brokers by changing the endpoints of your applications to connect to Amazon MQ, simplifying the migration process with minimal code changes.
5. **Monitoring and Logging**: Amazon MQ is integrated with Amazon CloudWatch and AWS CloudTrail, providing detailed monitoring and logging capabilities that allow you to track and analyze messages, and audit and monitor your message brokers.

## Where Amazon MQ is used

Amazon MQ is used to facilitate the seamless migration and operation of message broker services, encouraging decoupling in microservices, distributed systems, and serverless applications for reliable communication and coordination.

1. **Decoupling Microservices**: Amazon MQ is utilized to decouple microservices, enabling them to communicate asynchronously and be independently developed, deployed, and scaled. This use case focuses on enhancing system resilience and agility, making it easier to update and maintain parts of the system without impacting others.
2. **Disaster Recovery**: Amazon MQ acts as a critical component in disaster recovery strategies by ensuring messages can be replicated across different regions or availability zones. This use case provides a durable and reliable way to maintain business operations by ensuring that messaging systems can withstand regional failures.
3. **Third-party Integration**: Leveraging Amazon MQ for third-party application integration enables seamless communication and data exchange between disparate systems. This use case is particularly valuable in ecosystems where legacy systems need to interact with new cloud-based applications, facilitating smoother interoperability and data consistency.
4. **Load Balancing Workloads**: Amazon MQ is used to distribute workloads evenly across multiple consumers, ensuring no single service is overwhelmed. This use case is essential for maintaining system performance and reliability, especially during spikes in demand, by leveraging message queuing to prioritize and manage requests efficiently.
5. **Financial Transactions**: In the financial sector, Amazon MQ ensures the secure and reliable transfer of transaction data between services. This use case highlights the platform's ability to handle sensitive information, providing guaranteed delivery, transaction integrity, and the sequential processing of messages critical for financial operations.

## How Amazon MQ is priced

Amazon MQ pricing is based primarily on the chosen broker instance type and the number of active mq brokers, with additional costs for data transfer, storage, and metrics data emitted by brokers.

- **On-Demand Broker Instances**: Message broker instance usage is charged hourly and billed at one-second resolution, with rates depending on instance size and whether the deployment is single-instance, a three-node cluster, or active/standby.
- **Storage**: Broker storage is charged according to average monthly usage in GB-months, calculated by summing hourly GB usage and dividing by the number of hours in the month.
- **Data Transfer**: Inbound bandwidth to an AWS Region is free. Traffic forwarded between brokers across Availability Zones in the same Region costs $0.01/GB in each direction, and cross-Region outbound bandwidth follows EC2 data transfer pricing. RabbitMQ clusters have no additional intra-cluster data transfer fees.
- **Cross-Region Data Replication**: ActiveMQ cross-Region data replication has an additional hourly charge per broker, on top of the instance and storage charges for the primary and replica brokers.
- **Public IPv4 Addresses**: Standard public IPv4 address charges apply to addresses consumed by Amazon MQ endpoints.
- **RabbitMQ Private Networking**: RabbitMQ private networking connects brokers across VPCs and accounts over AWS PrivateLink using VPC Lattice Resource Gateway. Amazon MQ charges $0.01 per GB processed, and VPC Lattice Resource Gateway adds $0.006 per GB processed through the gateway.
- **AWS Free Tier**: New AWS customers signing up from July 15, 2025 receive up to $200 in Free Tier credits applicable to eligible services including Amazon MQ. The free plan lasts six months after account creation, and all credits must be used within twelve months of account creation.

## Services Amazon MQ works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon MQ brokers run on Amazon EC2 instances, leveraging its underlying compute resources for hosting the message brokers.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon MQ integrates with Amazon CloudWatch for monitoring, allowing you to view metrics, set alarms, and gain insights into the performance of your message brokers.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon MQ brokers can be hosted within an Amazon Virtual Private Cloud (VPC), giving you control over the network configuration such as subnets, security groups, and access control.

## What is Amazon MQ

Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easier for developers to set up and operate message brokers in the cloud. Message brokers are crucial components in many distributed systems, enabling components to communicate with each other through messages. This form of communication is essential for building scalable, loosely coupled architectures.

Amazon MQ is designed to take care of the heavy lifting involved in managing a message broker, such as maintenance, setup, and patching, allowing developers to focus on building and optimizing their applications. Amazon MQ supports industry-standard APIs and protocols, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket, allowing it to easily integrate with existing applications. This broad support means that many applications can switch to Amazon MQ with minimal changes to their codebase, making it a convenient option for teams looking to migrate their message broker to the cloud.

Moreover, since Amazon MQ is compatible with popular message brokers like Apache ActiveMQ and RabbitMQ, developers can leverage their existing skills and tools with the service. Amazon MQ does not automatically scale broker resources to meet application demand. Customers must explicitly change broker instance sizes or deployment configurations when additional capacity is needed.

Additionally, Amazon MQ is a managed service, meaning that Amazon handles the administration of your message broker, including updates and patches. This managed aspect of the service significantly reduces the operational burden on your team, allowing them to concentrate on developing new features and improving the application. Amazon MQ provides high availability and durability by storing messages redundantly across multiple Availability Zones (AZs) within a region. This design ensures that your messages are preserved and available even if one of the data centers fails, providing a robust foundation for building reliable applications.

For cross-Region disaster recovery, Amazon MQ for ActiveMQ supports cross-Region data replication between a primary broker and a replica broker.

Furthermore, Amazon MQ is fully integrated with AWS CloudWatch, giving developers detailed monitoring capabilities for their message brokers. This integration allows teams to track metrics, set alarms, and automatically react to changes in their messaging infrastructure's performance. Security is another critical aspect of Amazon MQ.

The service includes features such as encryption at rest and in transit, using AWS Key Management Service (KMS) for managing encryption keys. Additionally, Amazon MQ supports AWS Identity and Access Management (IAM) for controlling access to resources, allowing for fine-grained permissions and security policies.

In conclusion, Amazon MQ offers a reliable, scalable, and secure solution for managing message brokers in the cloud. By providing a managed service that is compatible with popular messaging protocols and APIs, Amazon MQ significantly simplifies the task of implementing and operating a messaging infrastructure. This ease of use, combined with its robust feature set, makes Amazon MQ an attractive option for developers looking to build or migrate distributed applications to the cloud.

## Concepts related to Amazon MQ

- [Message Queuing](https://blowstack.com/tools/cloud-concepts-hub/message-queuing): Message queuing is asynchronous communication in which producers place messages in a queue for consumers to retrieve and process independently.
