Integration
Amazon MQ
- Timebilled
- Bytesbilled
- Callsnot billed
In one line
Broker hours and storage, nothing per message.
What gets missed
No per-message or per-API charge exists in either engine, so throughput barely moves the bill. Active/standby doubles the instance hours and a three-node RabbitMQ cluster triples them.
Find it on your bill
Filter Cost Explorer or your Cost and Usage Report by these usage types. A usage type with no region prefix means us-east-1.
Single-AZUsage:mq.m5.largeMulti-AZUsage:mq.m5.largeTimedStorage-ByteHrs
Bills the same way
These services turn exactly the same meters, so what you learn here transfers.