RabbitMQ Config Generator

Generate production-oriented rabbitmq.conf files. Secure the Management UI, configure clustering, and tune memory high watermarks for reliable messaging.

Output:A ready-to-use configuration file for RabbitMQ Config with best practices applied.

Quick Summary

Use a RabbitMQ Config Generator when you need a rabbitmq.conf file, Docker env config, vhost/user templates, cluster settings, or Kubernetes ConfigMap examples.

What is this tool?

The rabbitmq.conf file (introduced in RabbitMQ 3.7.0) is the modern, sysctl-style configuration format. It replaces the older, highly complex Erlang term format (advanced.config).

RabbitMQ Configuration Options

listeners.tcp.default: The port for AMQP connections (default 5672). Setting this to 127.0.0.1:5672 prevents external connections.
default_user / default_pass: Sets the credentials for the default administrator. Never use the default guest / guest in production!
default_vhost: The default virtual host, usually /. Virtual hosts separate namespaces and queues within the same broker.
disk_free_limit: If the disk space drops below this limit, RabbitMQ will block publishers to prevent a complete crash.
vm_memory_high_watermark: Determines the threshold at which RabbitMQ begins paging messages to disk or blocking publishers to avoid Out of Memory (OOM) killer terminations. (Default is often 0.4, or 40% of RAM).

How to Use This Tool

Configuration Formats

RabbitMQ actually supports three formats simultaneously: rabbitmq.conf (standard key-value), advanced.config (complex Erlang terms for deep tuning), and environment variables (great for Docker/Kubernetes).

Platform Specific Configurations

Linux / Ubuntu: Edit /etc/rabbitmq/rabbitmq.conf and run systemctl restart rabbitmq-server.
Docker: Mount the config to /etc/rabbitmq/rabbitmq.conf. For the management UI, make sure to use the rabbitmq:3-management image tag.
Kubernetes ConfigMap: Use the RabbitMQ Cluster Operator for K8s, and inject these settings into the custom resource definition (CRD), or wrap them in a standard ConfigMap for basic StatefulSets.

What This Tool Generates

rabbitmq.conf key-value configuration
Environment variables for Docker deployments
Kubernetes ConfigMap snippet
README setup notes

Example Output Explanation

# rabbitmq.conf snippet
listeners.tcp.default = 5672

# Default credentials (change these!)
default_user = YOUR_ADMIN_USER
default_pass = YOUR_SECURE_PASSWORD

# Limits and Performance
vm_memory_high_watermark.relative = 0.4
disk_free_limit.absolute = 2GB

# Management Plugin
management.tcp.port = 15672

Security Notes

Do not use default guest/guest in production. By default, the guest user can only connect from localhost, but it's a massive security risk if exposed.
Do not put real passwords in config examples. Always substitute them with secure secrets when moving to production.
Secure management UI. The Management UI (port 15672) should never be exposed to the public internet.
Use TLS where appropriate. Configure AMQPS (port 5671) if producers and consumers are communicating across untrusted networks.

Frequently Asked Questions

What is a RabbitMQ Config Generator?

A RabbitMQ Config Generator is a tool to safely construct the modern rabbitmq.conf file. It helps you quickly establish secure listeners, set default credentials, define vhosts, and configure cluster nodes without navigating complex Erlang syntax.

How do I create rabbitmq.conf?

Use the interactive form above to define your TCP ports, users, and clustering strategy. Copy the generated properties and save them to your server, generally at /etc/rabbitmq/rabbitmq.conf.

Where is RabbitMQ config file?

Depending on your OS, the primary config file is located at /etc/rabbitmq/rabbitmq.conf (Linux), /usr/local/etc/rabbitmq/rabbitmq.conf (macOS Homebrew), or %APPDATA%\RabbitMQ\rabbitmq.conf (Windows).

How do I configure RabbitMQ user and password?

In the config file, you can set the default_user and default_pass variables. However, it's safer to configure this via Docker environment variables (RABBITMQ_DEFAULT_USER) or use the rabbitmqctl command line tool after startup.

How do I configure RabbitMQ vhost?

You can define the default virtual host in the config file using 'default_vhost = /'. For additional vhosts, you should use the rabbitmqctl add_vhost command or the Management UI.

How do I configure RabbitMQ Docker?

When using Docker, you can pass environment variables like RABBITMQ_DEFAULT_USER and RABBITMQ_DEFAULT_PASS directly. Alternatively, you can mount your generated rabbitmq.conf file into the container at /etc/rabbitmq/rabbitmq.conf.

Can I generate RabbitMQ ConfigMap?

Yes, you can paste the generated rabbitmq.conf directly into the data block of a Kubernetes ConfigMap, and then mount it into your RabbitMQ StatefulSet.

How do I configure RabbitMQ cluster?

In rabbitmq.conf, you define cluster discovery using the cluster_formation.peer_discovery_backend setting. You can hardcode nodes using classic config, or use DNS/Kubernetes plugins for automatic peer discovery.

How We Keep Your Configs Safe & Valid

Built-in Error Checking

Every file is checked against official rules. We catch missing fields and bad syntax. YAML indentation errors are flagged right away. Kubernetes, Terraform, and Docker specs are all covered. API versions and labels are verified too. You get valid output every time you generate.

100% Private & Local

All tools run in your browser only. Your API keys never leave your machine. We do not use any tracking scripts. No data is sent to any server. Passwords and secrets stay on your device. Crypto operations use the Web Crypto API. Your privacy is fully protected at all times.

Secure Settings by Default

Configs use safe defaults out of the box. Containers run as non-root users. Root filesystems are set to read-only. Dangerous Linux capabilities are dropped. Network policies limit pod-to-pod traffic. TLS 1.3 is enabled for web servers. Security headers are added where needed.

Ready for CI/CD & Git

Output files are ready for your Git repo. Use them with ArgoCD, Flux, or GitHub Actions. Files use clear formatting and comments. Code review is easy for your team. Indentation and key order are consistent. Test in staging before going to production. Every file is clean and well-structured.

Infrastructure as Code

Store configs in Git alongside your code. Terraform modules include typed variables. Backend configs support remote state locking. Outputs work across multiple modules. Ansible playbooks use clear task steps. Chef and Puppet configs are also supported. Every file works with version control tools.

Monitoring & Tracing

Set up Prometheus with auto-discovery rules. Create Grafana dashboards with template variables. Add alerting rules with severity labels. Use OpenTelemetry for trace collection. Forward logs to Loki or Elasticsearch. Connect to Jaeger or Tempo for tracing. Monitor metrics, logs, and traces together.

Container & Docker Safety

Dockerfiles use multi-stage builds for small images. Base images are pinned to exact versions. Dev files are excluded from final images. Health checks are added for orchestrator use. Containers switch to non-root users. Docker Compose uses named volumes and networks. Resource limits are set in deploy configs.

Multiple Output Formats

Export as YAML, JSON, HCL, or TOML. Kubernetes uses YAML with proper separators. Terraform uses HCL with correct escaping. JSON output has consistent indentation. Copy to clipboard with one click. Preview output with syntax highlighting. Line numbers help you review quickly.