RabbitMQ
Deploy RabbitMQ, an open source message broker that helps application components exchange data through a centralized messaging layer.
This app installs RabbitMQ with the management console available through a secure web interface.
1. Deploy RabbitMQ
Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.
For information on the app-specific configurations, see the Configuration options section.
Base distribution and plan
- Supported distribution: Ubuntu 24.04 LTS
- Recommended plans: All plan types and sizes can be used.
Configuration options
Configure the required options to deploy your instance. For additional customization, add advanced options.
The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.
StackScript ID: 688890
| UI field | API/CLI key | Description |
|---|---|---|
| Required options | ||
| Limited sudo user | user_name | Your preferred username for the limited sudo user entered without any capital letters, spaces, or special characters. When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the sudo group, which provides elevated permissions when running commands with the sudo prefix.Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an |
| Email address (for the Let's Encrypt SSL certificate) | soa_email_address | The email address used for generating SSL certificates and configuring the server and DNS records. |
| RabbitMQ version | rabbitmq_version | The RabbitMQ version to install. The only supported value is latest. |
| RabbitMQ admin username | rabbitmq_admin_username | The administrator username for the RabbitMQ management console. |
| RabbitMQ limited AMQP user | rabbitmq_username | The limited AMQP user. Use a different username than the RabbitMQ admin username. |
| Advanced options | ||
| Disable root access over SSH | disable_root | Applies to a limited sudo user. To block the root user from logging in over SSH, select Yes. Defaults to No. Note: When you disable the root user from logging in over SSH and don't provide a valid account SSH key assigned to the |
| Linode API token | token_password | Applies to a custom domain. The Linode API token if you want to use Linode's DNS Manager to manage DNS records for your custom domain. Follow Manage personal access tokens to get your token on your account with Read/Write access to Domains.
|
| Subdomain | subdomain | Applies to a custom domain. The subdomain you want to use, like blog for blog.example.com. Use it only if you specify a Domain. |
| Domain | domain | Applies to a custom domain. The domain name you want to use, like example.com. Use it only if you specify a Linode API token. |
| IP addresses allowed to access the Management UI | allowed_ips_amqp | A comma-separated list of IP addresses allowed to access the RabbitMQ management console. If left empty, no IP allow list is added. |
| Optional data exporter Add-ons | add_ons | An option to include add-ons for your deployment. Possible values are:
|
Notes:
- After the app deployment completes, the password for your limited sudo user is generated and stored in the
.credentialsfile in the home directory, along with application-specific passwords. Log in to your instance asrootthrough the Lish console or SSH, then runcat /home/$USERNAME/.credentialsto view its contents.- You can automatically configure a custom domain (optional) during deployment. To do that:
- Configure your domain to use Linode's name servers via your registrar. See Configure your domain's authoritative name servers for details.
- Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.
Use API, CLI, or Terraform
In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.
Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.
curl --location 'https://api.linode.com/v4/linode/instances' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer abc123def456hij789klm' \
--data-raw '{
"region": "us-east",
"type": "g6-dedicated-4",
"image": "linode/ubuntu24.04",
"label": "my-rabbitmq-one-click-app",
"root_pass": "@C0mpl3x#P@ssw0rd",
"stackscript_id": 688890,
"stackscript_data": {
"user_name": "jsmith",
"soa_email_address": "jsmith@example.com",
"rabbitmq_version": "latest",
"rabbitmq_admin_username": "rabbitadmin",
"rabbitmq_username": "rabbituser"
}
}'linode-cli linodes create \
--region us-east \
--type g6-dedicated-4 \
--label my-rabbitmq-one-click-app \
--image linode/ubuntu24.04 \
--root_pass @C0mpl3x#P@ssw0rd \
--stackscript_id 688890 \
--stackscript_data '{"user_name":"jsmith", "soa_email_address":"jsmith@example.com", "rabbitmq_version":"latest", "rabbitmq_admin_username":"rabbitadmin", "rabbitmq_username":"rabbituser"}'resource "linode_instance" "my-linode" {
region = "us-east"
type = "g6-dedicated-4"
label = "my-rabbitmq-one-click-app"
image = "linode/ubuntu24.04"
root_pass = "@C0mpl3x#P@ssw0rd"
stackscript_id = 688890
stackscript_data = {
"user_name" = "jsmith"
"soa_email_address" = "jsmith@example.com"
"rabbitmq_version" = "latest"
"rabbitmq_admin_username" = "rabbitadmin"
"rabbitmq_username" = "rabbituser"
}
}2. Access the RabbitMQ console
-
Open a web browser and navigate to
https://[domain], replacing [domain] with the custom domain entered during deployment or the instance's rDNS domain, such as192-0-2-1.ip.linodeusercontent.com.See the Manage IP addresses on a Linode guide for information on viewing the rDNS value.
-
Sign in to the RabbitMQ management console with the username and password from the
.credentialsfile.From here, you can use the console to configure exchanges, queues, users, permissions, and monitoring for your application.
Additional resources
For more information about the installed packages, see their official documentation.
Note that we can't vouch for the accuracy or timeliness of externally hosted resources.
Updated 19 days ago
