Deployment Overview of RabbitMQ on Server¶

Prerequisites and Basic Requirements¶

The deployment requires a Linux operating system based on the Ubuntu distribution with the following specifications:

• Operating System: Ubuntu

• Privileges: Root access is required for installation and configuration.

• Domain Zone: hostkey.in

• Required Ports:

• Internal Management Port: 15672

• External HTTPS Port: 443

FQDN of the Final Panel¶

The RabbitMQ management interface is accessible via the Fully Qualified Domain Name (FQDN) constructed using the server-specific prefix and ID. The URL format is:

rabbitmq<Server ID>.hostkey.in:443

Where <Server ID> is the unique identifier for the specific server instance.

Application Installation Process¶

The RabbitMQ server is installed directly on the host operating system using the native package manager. The process includes:

1. Updating the local apt cache.

2. Installing the rabbitmq-server package.

3. Starting and enabling the rabbitmq-server systemd service to run on boot.

4. Enabling the rabbitmq_management plugin to provide the web interface.

5. Configuring the management listener to bind to 127.0.0.1 on port 15672.

6. Creating an administrative user and setting permissions.

The installed version corresponds to the latest version available in the Ubuntu repositories at the time of execution.

Databases¶

RabbitMQ utilizes its internal storage mechanism for message queuing and metadata. The configuration establishes the following:

• Virtual Host: /

• User Credentials:

• Username: root

• Password: Configured via the system SSH password.

• Permissions: The root user is granted full permissions (.*) on the / virtual host for configuration, write, and read operations.

Docker Containers and Their Deployment¶

A reverse proxy infrastructure is deployed using Docker Compose to manage SSL termination and routing. The deployment details are:

• Directory: /root/nginx

• Composed File: /root/nginx/compose.yml

• Service: nginx

• Image: jonasal/nginx-certbot:latest

• Restart Policy: unless-stopped

• Network Mode: host

• Volumes:

• nginx_secrets: External volume mounted at /etc/letsencrypt inside the container.

• Host directory /data/nginx/user_conf.d mounted to /etc/nginx/user_conf.d inside the container.

• DNS Servers:

• 1.1.1.1

• 8.8.8.8

• 9.9.9.9

Proxy Servers¶

The application uses an Nginx container with Certbot integration to handle HTTPS traffic and SSL certificate management.

• Container Image: jonasal/nginx-certbot:latest

• Email for Certbot: [email protected]

• Environment File: /data/nginx/nginx-certbot.env

• Configuration Location: Nginx user configurations are stored in /data/nginx/user_conf.d.

• Routing Logic: A specific Nginx configuration file named <prefix><Server ID>.hostkey.in.conf is updated to proxy requests to the internal RabbitMQ management interface.

• The proxy_pass directive is set to forward traffic to http://127.0.0.1:15672.

• The external path / maps directly to the internal RabbitMQ management interface.

Location of Configuration Files and Data¶

The following file paths contain the core configuration and data for the deployment:

Available Ports for Connection¶

The system exposes the following ports for accessing the application:

Starting, Stopping, and Updating¶

Service management for the core application and the proxy is handled via systemd and Docker Compose respectively.

RabbitMQ Service Management:

• Start/Restart: systemctl restart rabbitmq-server

• Status: systemctl status rabbitmq-server

• Enable on Boot: systemctl enable rabbitmq-server

Docker Proxy Management:

• Start/Restart: docker compose up -d (executed from /root/nginx)

• Stop: docker compose down (executed from /root/nginx)

• Status: docker compose ps (executed from /root/nginx)