Databases And Persistence /
Deploy RabbitMQ on Northflank
This guide explains how to quickly and easily deploy and use RabbitMQ on Northflank.
|3.9.13||RabbitMQ is a lightweight, easy to deploy, open-source message broker that supports multiple messaging protocols.||Disk||Yes|
Choose addon from the create new menu in the top right corner of the dashboard
Select RabbitMQ and enter a name
Choose a version or leave as default (most recent version)
Choose whether to deploy with TLS. This can be changed later.
Choose whether to make RabbitMQ publicly accessible. This will give your addon a URL and make it available online. TLS must be enabled to select this.
If you have secret groups in your project, choose ones to link to the addon so that RabbitMQ can be used in services and jobs that inherit variables from the secret group. To link RabbitMQ to a secret group:
- Show secret groups and configure the secret groups you wish to use
- Select suggested secrets from RabbitMQ to link, or select all
- Set any required aliases for specific secrets to make them accessible by that name within your application
Select the required resources for your RabbitMQ deployment. You can scale RabbitMQ after creation, but available storage and replicas cannot be decreased once increased.
- Create addon and RabbitMQ will begin provisioning, this may take a few minutes.
You can manually copy the connection secrets for RabbitMQ from the connection details page into environment variables or build arguments of your workloads on Northflank.
However, it is much easier to link your storage's connection details to a new or existing secret group.
The necessary secrets to connect your workload will vary depending on your application and the protocols you are using.
To access the RabbitMQ management dashboard you can use the
MANAGEMENT_ENDPOINT with the the
PASSWORD secrets as credentials, which gives access to a management user . Using
ADMIN_PASSWORD to log in to the management dashboard will allow access to administrator account .
You can access RabbitMQ using the AMQP connection string and AMQP port.
|Port||TLS Port||Protocol||URL prefix|
STOMP and Streams are disabled by default, contact firstname.lastname@example.org to request that they are enabled.
Automatically inherit RabbitMQ connection details into your workload
- Create a new secret group of environment variables to connect in the running workload
- Show addons and configure your addon with either the
AMQP_PORT, or other connection details and secrets as required
- Set the aliases required in your workload to access the secrets
- Enable apply secrets to specific services/jobs and select the workloads you want to access the database
- Create secret group
- Go to one of the workloads that inherits from the group and check the environment page, you should see the inherited variables from the secret group
The connection string or secrets will now be available in your workload under the configured aliases, and your application will be able to connect to RabbitMQ using them.
To forward RabbitMQ for local access using the Northflank CLI, copy and execute the forward addon command from the local access section of the overview.
You can then use the
RABBITMQ_ADMIN_CMD from the connection details page to access your RabbitMQ deployment using the command-line client, or use the connection details in your local development environment.
To access your RabbitMQ deployment externally, ensure deploy with TLS and publicly accessible are enabled on the settings page under networking. The connection strings will be updated with the new configuration.