Ansible Playbooks to deploy projects to their EC2 server from Jenkins
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Ansible Project Deploy

These are the scripts and Anible playbooks that I use to deploy my projects to their proper AWS EC2 host using Jenkins. It was designed to be included as a `git submodule` for my projects and handle the basic build and deployment. This works well for my projects and could be used as a very basic deployment playbook for EC2. It has a few assumptions that are detailed below.


  • Python 2.7
  • Ansible 2.4
  • Git
  • An EC2 LAMP Server
  • A Private Key PEM file for the above server
  • AWS Access Key ID
  • AWS Secret Access Key

How To Install

In the root folder for your project, run the following:

git submodule add ./ansible/

How To Set Up

Whether you are running this locally or on a remote server, Ansible assumes that your host has CLI access to AWS configured. This script will help set that up, but you will need two files: the PEM file that was used to create the EC2 host and a configuration file that contains the following:


DO NOT commit these files to your project and put them under version control, rather install these files outside of your project directory in a place where Jenkins can access them. During one of your CI build steps, the files should be copied into the proper place. An Ansible variable file is also needed. This can be stored inside of version control and copied into the proper place during runtime. Sample Ansible config:

ec2_instance_name: "EC2 INSTANCE NAME TAG"
full_domain_path: "example: /var/www/vhosts/"
composer_build: false

How To Use

Prior to running the `` command, copy your configuration files into place:

cp YOURANSIBLECONFIG.yaml ./ansible/inventory/group_vars/all.yaml
cp ~/.ssh/YOURKEYFILE.pem ./ansible/inventory/ansible-deploy-key.pem
cp ~/.ssh/YOURAWSKEYS ./ansible/inventory/aws_keys

Once your configuration is in place, simply run `./`

Sample Jenkins Configuration

  • General: Can be any Project setting. I've used both GitHub and BitBucket.
  • Source Code Management: Git. Specify which branch to build.
  • Build Triggers: Can be anything, I use When changes are made on the Source Branch.
  • Build Environment: Delete workspace before build starts.
  • Build: This is where the magic happens. This is done in two steps. First to get the submodule and then to run the build script. Set up two Execute Shell steps like below.

First Execute Shell Step

git submodule add ./ansible/
touch ./ansible/inventory/group_vars/all.yaml
echo '---' >> ./ansible/inventory/group_vars/all.yaml
echo 'ec2_instance_name: "HOST_BOX_NAME"' >> ./ansible/inventory/group_vars/all.yaml
echo 'full_domain_path: "/var/www/vhosts/"' >> ./ansible/inventory/group_vars/all.yaml
echo 'composer_build: false' >> ./ansible/inventory/group_vars/all.yaml

Second Execute Shell Step


set -u # Variables must be explicit
set -e # If any command fails, fail the whole thing
set -o pipefail

export PATH=$PATH:/usr/local/bin

cp ansible_config.yaml ./ansible/inventory/group_vars/all.yaml
cp ~/.ssh/mypemfile.pem ./ansible/inventory/ansible-deploy-key.pem
cp ~/.ssh/aws_keys ./ansible/inventory

cd ansible
  • Post-build Actions: Your preference. I like the Slack Notifier, personally.