playbook-ec2

This is a role-based Ansible Playbook to provision EC2 instances with list and terminate plays. All the roles are submodules. They are idempotent which means it is safe to run them multiple times. Currenly, it supports Ubuntu and CentOS only. Two web applications, idservice and mbservice, have been fully tested with Nginx and Apache. Within these web applications, roles for Nginx, Apache, Tomcat, ActiveMQ and Postgresql are used.

This playbook treats the EC2 instance immutable on most of the EC2 properties, such as Region, AMI, Type, VPC, Subnet, Volume, etc. It means if any of them needs to be changed, a new instance has to be created with the old instance destroyed. But for other server configurations, such as packages, applications, etc, they will be treated as mutable.

This playbook depends on the default artifact repo for for artifacts such as qblite-1.0.1.tgz for QBroker. Alternatively, you can set up AWS S3 service as the artifact repo. If that is the case, it is assumed that the artifacts have been already uploaded to an S3 bucket and a role to access S3 is already set up for the user account. By default, the role of S3GetRole is assigned to the EC2 instance at the creation. Make sure to overwrite the name of the role via iam_role if it has a different name. You may also overwrite the variables such as qbroker_repo_url in case they are different from the default values.

Status

Tested with images of Ubuntu 16.04 and CentOS 7 only

Description

To run the playbook to provision an EC2 instance of Ubuntu 16.04 LTS on the default AWS profile and with the default web application, idservice, plus the database of Postgresql and the web frontend of Nginx:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname provision.yml

where your.pem is the pem file for your private key, your_keyname the name of the keypair. Make sure to replace them with the right ones for you.

To run the playbook to provision an EC2 instance of Ubuntu 16.04 LTS with the default web application, idservice, plus the database of MySQL and the web frontend of Apache:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname -e idservice_db=mysql -e web_frontend=apache provision.yml

To run the playbook to provision an EC2 instance of Ubuntu 16.04 LTS with the web application of mbservice and the web frontend of Nginx:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname -e wrapper_service=mbservice provision.yml

To terminate the launched instances in a specific region, such as us-east-1:

ansible-playbook -i hosts -e key_name=your_keyname -e region=us-east-1 terminate.yml

To list the launched instances on a specific profile, say the profile of aws_test:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname -e profile=aws_test list.yml

To run the playbook to provision an EC2 instance of CentOS 7 with the default web application, idservice, and the web frontend of Apache:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname -e wrapper_service=idservice -e web_frontend=apache -e image_id=ami-9cbf9bf9 provision.yml

To run the playbook to provision an EC2 instance of CentOS 7 with the default web application, idservice, in a different region of us-east-1:

ansible-playbook -i hosts -e pem_file=~/.ssh/your.pem -e key_name=your_keyname -e region=us-east-1 -e image_id=ami-ae7bfdb8 provision.yml

In order to run this playbook, the path of the ssh private key file for the key_name has to be specified in the command line under the var name of pem_file. The correct name for the keypair should be specified for key_name. It is also assumed that ~/.aws/credentials is set up with the access_key and secret_key for either the default profile or a specific profile. Further more, it is also assuemd that the ssh key pair has been set up on the AWS region. The default values of the following variables may need to be customized to fit your choice:

The playbook also requires boto and boto3 installed.

Author

Yannan Lu [email protected]

See Also

• [Ansible Docs] (http://docs.ansible.com)
• [CentOS EC2 AMI List] (https://wiki.centos.org/Cloud/AWS)
• [Ubuntu EC2 AMI Finder] (https://cloud-images.ubuntu.com/locator/ec2/)
• [Ansible Lab for EC2] (https://yannanlu.github.io/playbook-ec2.txt)
• [Ansible Lab for ActiveMQ] (https://yannanlu.github.io/ec2-activemq.txt)