RabbitMQ - Installation & Configuration at AWS EC2

1.   Choose instance type

Ø  RabbitMQ will work on 32-bit operating system, but for production usage we recommend 64-bit instances.

Ø  Launched an ami instance Ubuntu Server 14.04 LTS (HVM), SSD Volume Type - ami-864d84ee, 64-bit OS.

2.   Install Erlang

RabbitMQ is a message broker based on Erlang. So, before installing RabbitMQ server, we need to install Erlang.
2.1   Adding repository entry 

To add Erlang Solutions repository (including our public key for apt-secure) to your system, call the following commands:

wget http://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb sudo dpkg -i erlang-solutions_1.0_all.deb

2.2   Installing Ergang

Refresh the repository cache and install the erlang package.

sudo apt-get update sudo apt-get install erlang

3.   Install RabbitMQ

For installing latest version of RabbitMQ, use the debian repository and run the below shell script.

#!/bin/sh cat <<EOF > /etc/apt/sources.list.d/rabbitmq.list deb http://www.rabbitmq.com/debian/ testing main EOF curl http://www.rabbitmq.com/rabbitmq-signing-key-public.asc -o /tmp/rabbitmq-signing-key-public.asc apt-key add /tmp/rabbitmq-signing-key-public.asc rm /tmp/rabbitmq-signing-key-public.asc apt-get -qy update apt-get -qy install rabbitmq-server

We can verify that the RabbitMQ broker is actually working using the standard service command:

 

The default folders where the package has installed files are

configuration files	/etc/rabbitmq
application files	/usr/lib/rabbitmq
data files	/var/lib/rabbitmq
Log files	/var/log/rabbitmq

4.   Testing RabbitMQ

Once RabbitMQ has been started, confirm that it actually works. You can do this by installing the RabbitMQ Java client and running the test scripts that come with it. Use the following instructions to install the required packages on the instance:

4.1        Installing Oracle JDK

sudo apt-get install python-software-properties sudo add-apt-repository ppa:webupd8team/java sudo apt-get update sudo apt-get install oracle-java7-installer

 4.2        Installing RabbitMQ Java Client

curl http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.3.4/rabbitmq-java-client-bin-3.3.4.tar.gz \ -o rabbitmq-java-client-bin-3.3.4.tar.gz tar xzf rabbitmq-java-client-bin-3.3.4.tar.gz cd rabbitmq-java-client-bin-3.3.4

When the dependencies are available, we can run the test:

5.   Installing the management plugin

We need to restart RabbitMQ as follows:

The management console can be navigated by using the url - http://<hostname>:15672 as shown below:

Note: If the above url is not accessible, add an entry for TCP (port: 15672) in Inbound rules of Security Groups of your EC2 instance.

5.1        Configuring users

By navigating back to the management console login screen, we are now able to log in with ccm-admin and admin. The management dashboard can be displayed as below:

We can add another user for development purposes, i.e. ccm-dev as below:

RabbitMQ supports the notion of virtual hosts, which are logical subdivisions of its execution space. We're going to create a virtual host, also known as vhost, for the development environment. So, anything that happens in it happens in isolation from any other environments we can create in the future (such as a QA environment). So, let's create a vhost named ccm-dev-vhost as follows:

As it currently is, neither the ccm-admin nor ccm-dev users have permission to do anything on ccm-dev-vhost. Let's fix this by giving the vhost full rights on it as follows:

We can see user’s configuration on management console:

6.   Stop RabbitMQ Server

7.   Restart RabbitMQ Server

8.   Start RabbitMQ Server