Set up RabbitMQ exchange federation with an upstream policy to bridge a queue across two independent broker clusters

domain: rabbitmq.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Enable the federation plugin on both brokers: rabbitmq-plugins enable rabbitmq_federation rabbitmq_federation_management
  2. On the downstream broker, define the upstream connection parameter: rabbitmqctl set_parameter federation-upstream my-upstream '{"uri": "amqp://user:pass@upstream-host", "ack-mode": "on-confirm", "trust-user-id": false}'
  3. Create a policy on the downstream broker that applies federation to the target exchange: rabbitmqctl set_policy federate-orders 'orders' '{"federation-upstream": "my-upstream"}' --apply-to exchanges
  4. Declare the exchange with identical type and durability settings on both brokers; federation creates an internal binding and upstream queue automatically
  5. Verify the federation link status: GET /api/federation-links on the management HTTP API; confirm state=running and last_changed timestamp
  6. Test: publish to the exchange on the upstream broker and confirm consumers on the downstream broker receive messages

Known gotchas

Related routes

Choose between RabbitMQ federation and shovel for cross-broker message bridging
rabbitmq · 6 steps · unrated
Bridge topics bidirectionally between two HiveMQ Enterprise brokers using the HiveMQ Bridge Extension
docs.hivemq.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans