Skip to content



RabbitMQ is a solution for exchanging data between various applications' components or microservices. It is one of the most popular message brokers that support asynchronous communication between different systems and programming languages. RabbitMQ is based on AMQP (Advanced Message Queuing Protocol), which provides standardization and reliability in messaging. This service acts as an intermediary between senders and recipients of messages, allowing them to interact independently of each other.

RabbitMQ. Key Features

  • Message Queues: The ability to send messages to a queue and receive them asynchronously. It provides flexibility and fault tolerance in messaging between various system components.
  • Distributed: RabbitMQ supports a distributed architecture, which means that the message broker can be deployed on multiple nodes. It allows you to balance the load and provide fault tolerance
  • Delivery Guarantee: A sent message is kept in the queue until it is successfully delivered to the recipient or the timeout expires. It provides reliable communication between system components.
  • Publish/Subscribe Pattern: RabbitMQ supports a pub/sub (publish/subscribe) model where a publisher sends messages about a specific topic, and subscribers can receive messages about that topic.
  • Routing flexibility: RabbitMQ provides various options to route messages. It includes direct routing, topic routing, and more.
  • Extensibility: There are a large number of plugins that add additional functionality such as message encryption, authentication, monitoring, etc.
  • Management and monitoring tools: Admin web interface, command line, and API for automating and monitoring the work of RabbitMQ.

Features of the assembly

  • Installation on RHEL version 8 or later is possible.
  • Installed software:

    • Erlang >= 25.0
    • RabbitMQ >= 3.10.5
  • The software is installed outside the container. By default, the database is only accessible from localhost. To customize the installation, you need to make changes to the /etc/rabbitmq/rabbitmq-env.conf file, and restart the rabbitmq-server service.

The web interface will be available at the URL: https:rabbitmq{Server_ID_from_Invapi}

Getting started after deploying RabbitMQ

A notification will be sent to the e-mail specified during registration that the server is ready for work after paying for the order. It will contain the IP address of the VPS, as well as the login and password for the connection. Clients of our company manage the hardware in the server`s and API control panel - Invapi.

Here is the data for authorization:

  • Link to access the RabbitMQ dashboard with a web interface: in the webpanel tag;
  • Login: admin;
  • Password: in a letter to your e-mail upon receipt of the server.


For more information on the basic settings of RabbitMQ, see the documentation of the developers.

Ordering a server with RabbitMQ using the API

curl -s "" -X POST \
--data "action=order_instance" \
--data "token=" \
--data "deploy_period=" \
--data "deploy_notify=" \
--data "email=" \
--data "pin=" \
--data "id=" \
--data "os_id=" \
--data "root_pass=" \
--data "hostname=" \
--data "ssh_key=" \
--data "post_install_callback=" \
--data "post_install_script=" \
--data "reinstall_key=" \
--data "os_name=" \
--data "imitate_deploy=" \
--data "imitate_error=0" \
--data "own_os=" \
--data "jenkins_task=" \
--data "traffic_plan=" \
--data "invoice_relid=" \
--data "preset=" \
--data "location_name=" \