Amazon MQ looks simple on the bill until you pull it apart. Most teams spin up a managed ActiveMQ or RabbitMQ broker, send a few messages, and move on. Then the invoice arrives with line items they didn't expect.
Let's break down exactly where the money goes — and what catches people off guard.
The Broker Instance: It's Not a Flat Rate
Amazon MQ charges per broker instance-hour based on the instance type and engine. There's no single "broker fee." The range is wide:
| Instance Type | Engine | Hourly Rate | Monthly (730 hrs) |
|---|---|---|---|
| mq.t3.micro | ActiveMQ | $0.034 | $24.82 |
| mq.t3.micro | RabbitMQ | $0.034 | $24.82 |
| mq.m5.large | ActiveMQ | $0.276 | $201.48 |
| mq.m5.large | RabbitMQ | $0.276 | $201.48 |
| mq.m5.xlarge | ActiveMQ | $0.552 | $402.96 |
| mq.m5.2xlarge | ActiveMQ | $1.104 | $805.92 |
| mq.m5.4xlarge | ActiveMQ | $2.208 | $1,611.84 |
Prices shown for us-east-1, On-Demand.
A common mistake is assuming the smallest broker is "cheap." Even an mq.t3.micro runs 24/7, costing roughly $25/month before anything else. An mq.m5.large — the default many teams pick — is over $200/month per broker.
High Availability Doubles the Compute Cost
ActiveMQ supports active/standby deployment for high availability. This means two broker instances in different Availability Zones. Your compute cost doubles immediately:
- Single-instance mq.m5.large: $201.48/month
- Active/standby mq.m5.large: $402.96/month
RabbitMQ achieves HA through a three-node cluster deployment, which means you're paying for three instances. An mq.m5.large RabbitMQ cluster costs roughly $604/month in compute alone.
Teams often enable HA for production brokers and forget about it on dev/staging environments — where a single instance would be fine.
Storage: EBS vs. EFS Is a 3× Price Difference
ActiveMQ brokers on Amazon MQ offer two storage backends:
| Storage Type | Cost | Use Case |
|---|---|---|
| EBS | $0.10/GB-month | Standard durability, faster throughput |
| EFS | $0.30/GB-month | Shared storage for active/standby pairs |
EFS is required for active/standby deployments since both brokers need access to the same persistent store. That's a 3× premium over EBS.
A broker with 50 GB of message storage on EFS costs $15/month in storage alone. Not huge, but it adds up across multiple brokers and environments.
RabbitMQ brokers use EBS exclusively — no EFS option.
Data Transfer: The Silent Multiplier
Standard AWS data transfer charges apply to Amazon MQ:
- Same AZ: Free
- Cross-AZ (typical for HA): $0.01/GB each way
- Cross-Region: $0.02/GB
- Internet outbound: $0.09/GB (first 10 TB)
For active/standby deployments, replication traffic between AZs is cross-AZ data transfer. High-throughput brokers processing millions of messages per day can accumulate meaningful cross-AZ charges that don't appear under the "AmazonMQ" line item on your bill — they show up under general data transfer.
The Real Problem: Idle Brokers
Here's what actually burns money with Amazon MQ: brokers that nobody is using.
It's remarkably common. A team provisions a broker for a proof of concept, connects a few services, then the project pivots. The broker sits there at $200+/month with zero messages flowing through it. No consumers, no producers, no connections — just a running instance charging by the hour.
Unlike Lambda or SQS, Amazon MQ has no scale-to-zero capability. A broker with zero messages costs the same as one processing thousands per second.
The pattern we see most often:
- Dev/staging brokers left running after the sprint ends
- Migration brokers kept "just in case" after switching to SQS or EventBridge
- HA-enabled brokers in non-production environments
How to Spot the Waste
Look at these CloudWatch metrics for each broker:
- TotalMessageCount: If this is zero over 7–14 days, the broker is idle
- CurrentConnectionsCount: Zero connections means nothing is even trying to talk to it
- TotalConsumerCount / TotalProducerCount: Both at zero confirms no active clients
If all three are zero for more than a week, you're paying for a parking spot nobody is using.
CloudWise detects idle Amazon MQ brokers automatically by analyzing CloudWatch connection and message metrics. If your broker has had zero activity for 14 days, CloudWise flags it with the full monthly cost so you can decide whether to keep it or shut it down.
CloudWise automates AWS cost analysis across 145+ waste detectors. Try it at cloudcostwise.io
Top comments (0)