How to Setup RabbitMQ on Windows Server in Azure/AWS/GCP
To install RabbitMQ in any of the cloud platforms, the best way is to use the available images in the marketplace that run RabbitMQ on Windows server with the recommended configuration. Production ready. Click on the links below to deploy to your preferred cloud platform.
Cloud RabbitMQ Server Windows
Setup RabbitMQ on Azure
Setup RabbitMQ on AWS
Setup RabbitMQ on GCP
Table of Contents
RabbitMQ features
RabbitMQ a messaging brokers that understands AMQP (Advanced Message Queuing Protocol)and some of the features are:
- Asynchronous Messaging
- Clusters Distributed Deployment
- Supports multiple languages such as Java, Ruby, Python, PHP, Perl Rust, Go, JavaScript, C and C++
- Uses applied protocols: RabbitMQ supports AMQP, MQTT, STOMP, HTTP and WebSockets protocols.
- Message Patters: Message Queue, PUB-SUB and RPC and Routing.
Getting Started with RabbitMQ
RDP (Remote Desktop Protocol) into new server
Once you have deployed RabbitMQ on Windows server, the first step is to RDP into the new instance once it has fully booted up. The following links explain how to connect the VM once it has finished being deployed:
- How to RDP to AWS Windows Instance
- How to RDP to Google GCP Windows Instance
- How to RDP to Azure Windows Virtual Machine
Once logged in, you’re now ready to start setting up your new server as per the following sections. Scroll down to the cloud platform section you are using:
Running RabbitMQ on Azure
Check the status of your installation. Open up the RabbitMQ Command from the desktop and run the following command:
rabbitmqctl status
If you get the following message regarding authentication failed, follow the instructions below for Erlang Cookie authentication.
If the installation is successful you will receive the following status result:
Erlang Cookie authentication
The first step is to copy the .erlang.cookie from your users profile under
c:\users\%username%
to
c:\Windows\System32\config\systemprofile
Over write the existing cookie in c:\windows\system32\config\systemprofile
Next is to restart the RabbitMQ Service. Open up the RabbitMQ Command from the desktop and run the following commands to restart the service:
rabbitmq-service.bat stop
rabbitmq-service.bat start
Now check the status, run the following command:
rabbitmqctl status
And you should see the following output:
RabbitMQ Management Login
The management login details are as follows:
http://localhost:15672
User: guest
Pass: guest
Running RabbitMQ on AWS
RabbitMQ Management URL Login
Using Microsoft Edge Browser open up the following URL:
http://localhost:15672
User: admin
Pass: Password is the VM Instance ID. To find the Instance ID you will find on the top right of the desktop or within the AWS console under the EC2 VM properties
NOTE: If you find the password doesn’t work. Wait 5 mins as during the first boot a startup script is setting the admin password and could still be running. You can see if its still running by viewing any Windows task schedule jobs. Wait for it to finish and then try logging in again.
Check the status of your installation. Open up the RabbitMQ Command from the desktop and run the following command:
rabbitmqctl status
If you get the following message regarding authentication failed, follow the instructions below for Erlang Cookie authentication.
If the installation is successful you will receive the following status result and you’re ready to start using RabbitMQ.
Erlang Cookie authentication
The first step is to copy the .erlang.cookie from your users profile under
c:\users\%username%
to
c:\Windows\System32\config\systemprofile
Over write the existing cookie in c:\windows\system32\config\systemprofile
Next is to restart the RabbitMQ Service. Open up the RabbitMQ Command from the desktop and run the following commands to restart the service:
rabbitmq-service.bat stop
rabbitmq-service.bat start
Now check the status, run the following command :
rabbitmqctl status
And you should see the following output:
Running RabbitMQ on GCP
RabbitMQ Management URL Login
http://localhost:15672
User: admin
Password is the VM Instance ID. To find the Instance ID you will find on the property details of the VM within your GCP console. Here is a screenshot of where you will find it:
NOTE: If you find the password doesn’t work. Wait 5 mins as during the first boot a startup script is setting the admin password and could still be running. You can see if its still running by viewing any Windows task schedule jobs. Wait for it to finish and then try logging in again.
Check the status of your installation. Open up the RabbitMQ Command from the desktop and run the following command:
rabbitmqctl status
If you get the following message regarding authentication failed, follow the instructions below for Erlang Cookie authentication
If the installation is successful you will receive the following status result and you’re ready to start using RabbitMQ.
Erlang Cookie authentication
The first step is to copy the .erlang.cookie from your users profile under
c:\users\%username%
to
c:\Windows\System32\config\systemprofile
Over write the existing cookie in c:\windows\system32\config\systemprofile
Next is to restart the RabbitMQ Service. Open up the RabbitMQ Command from the desktop and run the following commands to restart the service:
rabbitmq-service.bat stop
rabbitmq-service.bat start
Now check the status, run the following command :
rabbitmqctl status
And you should see the following output:
RabbitMQ Firewall Ports
For a full list of RabbitMQ firewall ports check: https://www.rabbitmq.com/install-windows.html#ports
To setup AWS firewall rules refer to – AWS Security Groups
To setup Azure firewall rules refer to – Azure Network Security Groups
To setup Google GCP firewall rules refer to – Creating GCP Firewalls
RabbitMQ Windows Documentation / Support
Refer to RabbitMQ official documentation on https://www.rabbitmq.com/documentation.html
RabbitMQ support can be found at https://www.rabbitmq.com/#support
If you have issues with installing RabbitMQ in your cloud environment leave a comment below or contact us directly and we will assist it getting the server up and running
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
