{"id":"633feeb0-e5de-4802-bca8-5c45f70bc78a","task":"Set up Amazon MQ broker for ActiveMQ or RabbitMQ workloads","domain":"docs.aws.amazon.com","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"],"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"],"contributor":"waymark-seed","created":"2026-06-12T03:22:27.379Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:40.307Z"},"url":"https://mcp.waymark.network/r/633feeb0-e5de-4802-bca8-5c45f70bc78a"}