RabbitMQ

1. Overview

The RabbitMQ add-on deploys an instance of RabbitMQ, a message broker speaking AMQP 0-9-1. It lets flows and apps exchange messages asynchronously, decoupling producers and consumers: work queues, publish/subscribe via exchanges, retries, dead-lettering, and absorbing load spikes.

Use it when you need durable messaging between components. For cache/counters use Cache (Valkey); for relational data, PostgreSQL; for vector search, Qdrant.

Catalog tags: Message broker, AMQP, Queues.

2. Prerequisites

• A squad and an environment already selected on the Add-ons screen.

3. Deploy walkthrough

The RabbitMQ deploy wizard has 3 steps:

Step 1 — General

Field	Required	Description
Add-on Name	Yes	Add-on name within the environment. Lowercase letters, numbers and hyphens only. Example: my-broker.
Virtual Host	No	Default virtual host provisioned on the instance. Default: /.
Admin Public	No	When enabled, the native RabbitMQ management UI is publicly reachable. Off by default (access restricted by the platform).

Step 2 — Admin User

Defines the admin (management) user of the instance.

Field	Required	Description
Username	Yes	Admin user name. Default: admin.
Password	Yes	Admin password.

Step 3 — Resources

Defines the compute resources allocated to the instance.

Field	Default	Suggestion/Max
Memory Limit	512Mi	1Gi
CPU Limit	500m	2000m
Storage Size	5Gi	20Gi

Clicking Deploy Add-on starts the deployment. The add-on then appears under the environment's My Add-ons tab.

4. After deploy

The add-on panel on the platform covers the full day-to-day operation cycle, organized in tabs (scoped per virtual host where it applies):

• Overview — live charts of message rates and queued messages (selectable window: 1 min to 24 h), totals (ready/unacked/total) and topology counts (queues, exchanges, connections, channels, consumers).
• Exchanges — list, declare (type, durability, arguments), inspect bindings and test-publish, and delete.
• Queues — list, declare (classic/quorum/stream) and, per queue, the full cycle: bindings, publish, get messages (peek or consume), purge and delete.
• Connections — inspect open client connections and their channels, and force-close a connection.
• Credentials — users with tags and permissions (configure/write/read per virtual host) and topic permissions; create/edit/delete and export a user's credentials to a platform secret.
• Settings — resources (memory/CPU/storage — storage only grows) and the Private/Public visibility of the management UI.

Beyond the panel, the native RabbitMQ management UI is available via the Open management UI button, with the complete feature set. When Admin Public is off (default), access is protected by the platform session (a broker login is still required).

Connecting a flow to RabbitMQ

Flows connect to the broker over AMQP, using the add-on's Internal URL (amqp://<addon-name>:5672). Connection credentials should live in secrets:

1. On the Credentials tab, create a dedicated user with least-privilege permissions (avoid sharing admin), and use Export — the platform writes host, port (AMQP), username, password, vhost and useTls into a secret (new or existing).
2. In the flow connector, reference those properties as {$.env.<secret>.<prop>}.

Export is enabled only for users whose password the platform holds (admin and users created through the panel); a user created outside the platform shows export disabled.

5. Frequently asked questions

Can I change the admin user's password?

Yes. On the Credentials tab, the management user allows changing the password (password only). The instance is updated to apply the new password; any secret already exported with the old password must be re-exported.