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.

Getting Started

 

RDP 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:

 

 

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

Erlang_Distribution_failed

 

If the installation is successful you will receive the following status result

Status_Success

 

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

 

erlang_cookie

 

Over write the existing cookie in c:\windows\system32\config\systemprofile

SystemProfile_cookie

 

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

 

Restart_Services

 

Now check the status, run the following command – rabbitmqctl status

 

And you should see the following output:

Status_Success

 

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

 

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

Erlang_Distribution_failed

 

If the installation is successful you will receive the following status result and you’re ready to start using RabbitMQ

Status_Success

 

 

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

erlang_cookie

 

Over write the existing cookie in c:\windows\system32\config\systemprofile

SystemProfile_cookie

 

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

Restart_Services

 

Now check the status, run the following command – rabbitmqctl status

 

And you should see the following output:

Status_Success

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:

setup RabbitMQ in GCP

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

Erlang_Distribution_failed

 

If the installation is successful you will receive the following status result and you’re ready to start using RabbitMQ

Status_Success

 

 

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

erlang_cookie

 

Over write the existing cookie in c:\windows\system32\config\systemprofile

SystemProfile_cookie

 

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

Restart_Services

 

Now check the status, run the following command – rabbitmqctl status

 

And you should see the following output:

Status_Success

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

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

 
Disclaimer: RabbitMQ is a registered trademark owned by Pivotal Software, Inc and is licensed under MOZILLA PUBLIC LICENSE V1.1 license. THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
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.
Andrew Fitzgerald

Cloud Solution Architect. Helping customers transform their business to the cloud. 20 years experience working in complex infrastructure environments and a Microsoft Certified Solutions Expert on everything Cloud

No Comments

Post a Comment

Comment
Name
Email
Website