Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Amazon MQ is AWS’s managed message broker service for two messaging engines, Apache ActiveMQ Classic and RabbitMQ. AWS runs and maintains the broker infrastructure. You still choose the engine, decide how messages flow between your applications, configure access, and decide how you will monitor and pay for the service.
This guide follows the structure of a beginner’s workshop write-up, “M for Moha, M for Amazon MQ,” by Moha Prasath SA on DEV Community. Its campus scenario is an illustration. It is not described as a system the author built, load-tested, or deployed, and the explanation below keeps that distinction clear.
As an Amazon Associate I earn from qualifying purchases.
The campus scenario, as an illustration
The workshop imagines a college with several separate software components: a registration application, an attendance system, an examination system, an email service, and a notification component. Without a broker, the registration application would call each of the others directly, so every new component adds another direct dependency.
In the illustration, the registration application instead publishes a registration event to a broker, and the notification component consumes that event. The registration application no longer needs to know who is listening. That decoupling is the idea the example is meant to teach. It does not show that the architecture is reliable, scalable, or secure. Those outcomes depend on how the applications are written and how the broker is configured and operated.
#1 Best Overall
What a message broker does
A message broker is a piece of software that sits between applications and carries messages from the components that send them to the components that process them. Applications talk to the broker using a messaging protocol rather than to each other directly.
Brokers are useful when a sender should not wait for a receiver, when a receiver may be temporarily unavailable, or when several different components need to react to the same kind of event. The exact behavior, including how messages are stored, routed, acknowledged, and retried, depends on the broker engine and on the design of your application.
What Amazon MQ manages and what you still own
Amazon Web Services describes Amazon MQ as a managed message broker service for Apache ActiveMQ Classic and RabbitMQ that manages the setup, operation, and maintenance of message brokers. The official overview is in the Amazon MQ developer guide.
Recommended Free Tools
Managed does not mean hands-off. The split between AWS and your team looks roughly like this:
Rank #2
| Area | Handled by Amazon MQ | Your responsibility |
|---|---|---|
| Broker setup and maintenance | AWS manages setup, operation, and maintenance of the broker. | Choose the engine, deployment option, and broker size. |
| Metrics | Broker and queue metrics are collected and pushed to Amazon CloudWatch every minute. | Create dashboards and alarms, and decide what counts as a problem. |
| Encryption | Encryption at rest and in transit is available, and SSL broker connections are supported. | Confirm the settings you need and manage client certificates and credentials. |
| Network access | You can restrict access to a private endpoint in an Amazon VPC. | Design the VPC, subnets, and which clients can reach the broker. |
| Permissions | IAM controls limit which actions users and groups can take on brokers. | Define those policies and application-level authorization. |
| Messaging design | Not applicable; the engine carries messages as configured. | Design queues, topics, or exchanges, acknowledgements, retries, and ordering. |
| Migration | AWS documents that existing brokers can be migrated without rewriting messaging code. | Verify protocols, engine versions, features, and application behavior before cutover. |
The migration row deserves emphasis. The documentation states that existing brokers can be migrated without rewriting messaging code, but that is a general statement. It does not remove the need to check whether your protocols, engine version, and features are supported and whether your applications behave the same way afterward.
Choosing an engine: ActiveMQ Classic or RabbitMQ
Amazon MQ supports two engines. Choosing between them is the first real decision, and it usually depends on what your existing applications already use.
Apache ActiveMQ Classic
ActiveMQ Classic is the engine to choose when your applications already use it or depend on its features. Keep the name precise: Amazon MQ supports ActiveMQ Classic, not every ActiveMQ product or version. Check the engine version your application needs against what Amazon MQ offers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For ActiveMQ, AWS documents two deployment patterns:
- Single-instance: one broker in one Availability Zone.
- Active/standby: a pair of brokers in two Availability Zones, ordinarily with one active and one standby. AWS says a failover caused by a broker reboot takes a few seconds. That timing describes that scenario in the AWS documentation; do not assume it applies to every kind of failure.
The deployment options are described in the Amazon MQ deployment options guide for ActiveMQ brokers.
RabbitMQ
RabbitMQ is the other supported engine. AWS documents it separately, with its own tutorials and best-practice pages, so do not assume that ActiveMQ’s deployment patterns or failover behavior describe RabbitMQ. Check the RabbitMQ documentation in the Amazon MQ developer guide for the options that apply to your use case.
Decision axes for comparing the two
AWS does not provide a head-to-head ranking of the two engines in the material this guide relies on, and this guide does not establish one. When you compare them for a real project, evaluate these axes:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- Compatibility with your existing applications, protocols, and client libraries
- Broker features your application depends on
- Deployment and availability pattern you need
- Operational behavior you are prepared to run
- Security and network requirements
- Expected throughput and message patterns
- Total cost in the AWS Region you plan to use
How a message moves through a broker
The simplest mental model has three roles: a producer, a broker, and a consumer. Using the campus scenario:
Rank #4
- The producer publishes. The registration application connects to the broker using a supported protocol and sends a registration event.
- The broker holds the message. The message is placed in a destination. Whether that destination is a queue, a topic, or an exchange, and how it is routed, depends on the engine and your configuration.
- The consumer receives. The notification component receives the message and processes it.
- Acknowledgement and failure handling. Whether a message is acknowledged, redelivered, or retried, and whether ordering is preserved, depends on the engine, your client library, and your application design. Confirm each of these against the documentation for your chosen engine before you rely on them.
This is a conceptual flow. It is not a universal Amazon MQ message pattern that every workload can copy without changes.
Security and network setup
Amazon MQ documents several security controls: encryption at rest and in transit, SSL broker connections, the option to restrict access to a private endpoint in an Amazon VPC, and IAM controls over the actions users and groups can take on brokers. These are available controls, and turning them on or configuring them is part of your job.
They do not replace application-level authorization, careful credential management, or sound network design. A broker that is encrypted and reachable only from a private network can still accept messages from a client that should not be sending them, if your application does not check who is sending.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Monitoring with Amazon CloudWatch
Broker and queue metrics are available through Amazon CloudWatch and are collected and pushed every minute, according to AWS. That is a product capability. It does not mean that alerting is configured for you. Dashboards, alarms, and thresholds are your responsibility, and they are where most of the operational value comes from.
Best Value
What it costs
Amazon MQ is a paid service, so review cost before creating a broker, especially when following a workshop. The cost has three main parts:
- Broker runtime. Billed hourly at one-second resolution. The rate varies with broker size and deployment option, and by Region.
- Storage. Billed monthly.
- Data transfer. May apply, depending on how your traffic moves.
AWS pricing examples use particular Regions, broker sizes, storage amounts, and configurations. Use them only with those assumptions, and recheck the Amazon MQ pricing page for your Region before you estimate a budget. Delete brokers you no longer need, because runtime charges accrue while a broker exists.
The pricing page also describes an AWS Free Tier offer beginning July 15, 2025 for new AWS customers: up to $200 in credits, a free plan option lasting six months after account creation, and credits expiring within 12 months. That start date is more than a year before this article’s update, so the offer may no longer be available. Read the current terms on the pricing page before you rely on any credit or free plan.
Quick Recap
Decision checklist before you create a broker
- Compatibility: Does your application use ActiveMQ Classic or RabbitMQ, and is the version and protocol supported?
- Application needs: Which queue, topic, or exchange behavior, acknowledgement model, and ordering guarantees does your design require, and does the chosen engine provide them?
- Availability: Is a single-instance broker acceptable, or do you need an active/standby pair for ActiveMQ, or the RabbitMQ option that fits your requirements?
- Security and network: Have you planned encryption, SSL connections, private VPC access, and IAM policies, along with application-level authorization?
- Monitoring: Have you set up CloudWatch dashboards and alarms for the metrics that matter to you?
- Cost: Have you confirmed broker size, storage, data transfer, and Region, and do you have a plan to remove resources when you finish?
|
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
