Virtual hosts for isolation in RabbitMQ - Commands & Configuration

Introduction

Virtual hosts in RabbitMQ let you create separate spaces inside the server to keep different applications or teams isolated. This helps avoid conflicts and keeps data and permissions separate.

When you want to run multiple applications on the same RabbitMQ server without them interfering with each other

When different teams need their own isolated messaging environment on a shared RabbitMQ server

When you want to apply different access controls and permissions for different groups using the same RabbitMQ instance

When testing new features or apps without affecting the main production messaging setup

When organizing your messaging setup by project or environment (like dev, test, and production) inside one RabbitMQ server

Commands

This command creates a new virtual host named 'my_vhost' to isolate resources for a specific application or team.

Terminal

rabbitmqctl add_vhost my_vhost

Expected Output

No output (command runs silently)

This command lists all virtual hosts on the RabbitMQ server so you can verify that 'my_vhost' was created.

Terminal

rabbitmqctl list_vhosts

Expected Output

Listing vhosts ...

/my_vhost

/

This command sets full permissions for user 'my_user' on the 'my_vhost' virtual host, allowing them to configure, write, and read.

Terminal

rabbitmqctl set_permissions -p my_vhost my_user ".*" ".*" ".*"

Expected Output

No output (command runs silently)

→

-p my_vhost - Specifies the virtual host where permissions apply

This command shows the permissions for all users on the 'my_vhost' virtual host to confirm the settings.

Terminal

rabbitmqctl list_permissions -p my_vhost

Expected Output

Listing permissions for vhost "my_vhost" ...

my_user	.*	.*	.*

→

-p my_vhost - Specifies the virtual host to list permissions for

Key Concept

If you remember nothing else from this pattern, remember: virtual hosts create separate spaces inside RabbitMQ to keep apps and teams isolated and secure.

Common Mistakes

Trying to use a virtual host before creating it

RabbitMQ will reject connections or commands because the virtual host does not exist yet

Always create the virtual host first using 'rabbitmqctl add_vhost' before assigning permissions or connecting clients

Not setting permissions for users on the new virtual host

Users cannot access or use the virtual host without proper permissions, causing connection failures

Use 'rabbitmqctl set_permissions' to grant users the needed rights on the virtual host

Summary

Create a virtual host with 'rabbitmqctl add_vhost' to isolate resources.

List virtual hosts with 'rabbitmqctl list_vhosts' to verify creation.

Set user permissions on the virtual host with 'rabbitmqctl set_permissions'.

Check permissions with 'rabbitmqctl list_permissions' to confirm access.