Skip to content

Latest commit

 

History

History
57 lines (42 loc) · 3.16 KB

README.md

File metadata and controls

57 lines (42 loc) · 3.16 KB
Raw

#Steps to setup RabbitMQ servers cluster using EC2 [With SSL for Security]

###Note: Before running the python scripts mentioned here make sure you have paramiko 2.1.1 installed. To install the same try: sudo pip install paramiko --upgrade

  1. Create a new security key which shall be same for all the AWS instances. Let this be named "rabbitmqkey". Any description can be added. Also change permission of the key file eg : chmod 400 rabbitmqkey.pem

  2. Create a new security group on AWS, with following under inbound ports: This shall be used by our EC2 RMQ instances.

SSH                TCP             22         0.0.0.0/0
Custom TCP Rule    TCP         0-65535        sg-x.x.x.x (your security group)

In above step adding your own security group id might not happen in first time. So crete SG with SSH rule only and later add the 2nd rule.

  1. Create a new AWS EC2 instance

    1. I used Ubuntu 16.04 server with t2.micro instance type
    2. Use the same security group and security key for the instance when prompted.
    3. Open set_RMQ_EC2.py and replace public DNS or instance's name with your instance's name in the "hostnames" list.
    4. In path_key give the path to the security key used to create your instance.
    5. In path_ssl_keys give the server side ssl keys that you wish to be trasfered to your remote RMQ server. [please keep the folder name as "keys-server" as it will be copied directly to your EC2 instance].
    6. Also provide the RMQ_user_name and RMQ_password that you will be using to access your RMQ cluster nodes later.
    7. Run set_RMQ_EC2.py to build rabbitMQ server up and running on this instance. It shall also copy the rabbitmq.config file to your instance so as to enable ssl.

  2. Create an image of your AWS EC2 instance.

  3. After the image is constructed, create a new instance using that image. Make sure this instance also belongs to the same security group.

  4. After the instance gets created, this should be our slave machine. Replace in set_RMQ_cluster_AMI.py the master and slave hostnames with the public DNS [instance names of your master and slave instances]. Also make the required changes at required places.

  5. Replace the path_key with the one present at your computer.

  6. Run the script set_RMQ_cluster_AMI.py. This shall create the cluster of master and slave between these two instances and also set the mirroring policy between the queues.

  7. To check whether the rabbitmq queues are working on their dedicated servers. In your web browser type:

    rabbit@<pub-ip-addr-of-your-EC2>:15671

    This shall load up the managemnt plugin

  8. Launch an elastic load balncer (ELB) with the same security group as was used to create the EC2 instances. For listening to SSl: Set LB Protocol to TCP/5671 And Instance protocol to TCP/5671

For listening management plugin: Set LB Protocol to TCP/15671 And Instance protocol to TCP/15671

Then in 2nd step choose our security group Also configure Health Check ping to TCP/5671 Then add all EC2 instances to the LB Review and Launch

  1. Update the BROKER_URL in settings.py file to point to ELB instance. Use A-record address shown on ELB's description page for the same.