New to this? You don’t need to know Kubernetes or Helm. Qovery installs RabbitMQ on your cluster with Helm and runs it for you: you fill in a form, or paste the prompt below into your coding agent. The values it publishes, listed under Outputs, reach your other services as environment variables. Qovery tells you when a newer version of the Blueprint is available. Check the requirements in the Reference section before you start, and try it first in a development environment.
Open the environment, then New service › Blueprint.
Find RabbitMQ in the catalog and pick the major version.
Fill in the variables. Required ones are marked; the others use their defaults.
Create the service, and deploy it now or later.
List the catalog to get the latest tag, then create the service from it. qovery api signs the requests with your CLI session.
ORG_ID="REPLACE_WITH_ORGANIZATION_ID"ENV_ID="REPLACE_WITH_ENVIRONMENT_ID"qovery api "organization/$ORG_ID/blueprint/catalog" | jq '.. | objects | select(.name? == "helm-rabbitmq")'cat > blueprint.json <<'EOF'{ "name": "helm-rabbitmq", "tag": "HELM/rabbitmq/4/2.0.4", "icon": "app://qovery-console/rabbitmq", "variables": [ { "name": "password", "value": "REPLACE_WITH_PASSWORD", "is_secret": true } ]}EOFBLUEPRINT_ID=$(qovery api "environment/$ENV_ID/blueprint" --method POST --input - < blueprint.json | jq -r .id)rm blueprint.json # it can hold secret valuesqovery api "blueprint/$BLUEPRINT_ID/deploy" --method POSTqovery api "blueprint/$BLUEPRINT_ID" # status of the latest deployment
Replace each REPLACE_WITH_ value. Add optional variables to variables the same way.
Paste this into Claude Code, Cursor, Codex or another coding agent with the Qovery agent skills installed (curl -fsSL https://skill.qovery.com/install.sh | bash).
Prompt
Add the Qovery Blueprint RabbitMQ (helm-rabbitmq) to one of my Qovery environments and deploy it. Ask me for password.Ask me before deploying to a production environment.Docs: https://www.qovery.com/docs/configuration/blueprints/helm-rabbitmq.md
You don’t add any file to your repository. Qovery creates the Blueprint from the Console or the API.
Generated from qbm.yml at HELM/rabbitmq/4/2.0.4, the manifest the Console form is built from.
All 4 variables
Name
Type
Required
Default
Secret
Description
replica_count
number
1
RabbitMQ pods, 1–10
username
string
user
Letters, digits, dots, hyphens, underscores; max 64 chars.
password
string
Yes
Yes
10–128 chars.
memory_limit
string
512Mi
Kubernetes quantity, e.g. 512Mi or 1Gi
Outputs become environment variables that other services in the environment can use. By default Qovery also creates an alias for each output, prefixed with the Blueprint’s name; see Aliases Qovery creates for outputs for the naming rules and the cases where no alias is created.
From the Blueprint’s README.Deploys RabbitMQ message broker via the community groundhog2k Helm chart, which wraps the official docker.io/rabbitmq image. Data is not persisted — pod restarts will clear queues and messages. When replica_count > 1, the replicas form a cluster via Kubernetes peer discovery.
