Set up Amazon MQ broker for ActiveMQ or RabbitMQ workloads
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an Amazon MQ broker via console or CLI, choosing broker engine (ActiveMQ or RabbitMQ) and deployment mode (single-instance or active/standby)
Place the broker in a VPC with security groups restricting access to known CIDR ranges; Amazon MQ brokers are not publicly accessible by default without enabling public accessibility
Retrieve the broker endpoint URLs from the Amazon MQ console under Connections; use the appropriate protocol endpoint (AMQP, STOMP, OpenWire, MQTT for ActiveMQ; AMQP for RabbitMQ)
Connect your client using the broker-specific wire protocol and the credentials set during broker creation
For ActiveMQ, configure network-of-brokers settings in the broker XML configuration if connecting multiple brokers; for RabbitMQ, use the cluster endpoint
Known gotchas
Amazon MQ is a managed service but does not support all configuration options available in self-hosted ActiveMQ or RabbitMQ; review the restrictions in the service documentation before migrating
Active/standby deployment provides automatic failover but clients must handle reconnection; the standby broker endpoint is the same but the failover may cause a brief connection drop
Storage and instance costs apply even when the broker is idle; size the broker instance type to your throughput needs to avoid over-provisioning
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?