Project : aws-terraform-nginx-ansible-docker-jenkins

 list of requirements :

Automate provisioning and configuration of NGINX server in Docker container with SSL certificate in AWS cloud using Jenkins, Ansible, Terraform.
 
Assumptions:
1.  The available free version of Linux
2.  The latest available version of NGINX for Linux
3.  EC2 instance size is t2.micro (free tier)
4.  Must create and use free tier of private AWS account
5.  The SSL certificate is self-signed
6.  The AWS Security Group is default
 
Acceptance Criteria:
1.  Post-provisioning report demonstrates evidence of
a.  No provisioning errors
b.  Sequence of provisioning steps
c.  Up and running instance of NGINX
d.  Listening on ports 80 and 443
e.  Response on ports 80 and 443
f.  content of active instance configuration file
2.  Run automated pipeline 3 times in a row and receive the same result (fully remove provisioned EC2 with components after every deployment, automation is optional for removal)
 
This one was actually fun to work on. So let's try to meet each of these criteria.
 

Assumptions to complete this tutorial:

  1. You have an AWS account set up and have IAM profiles on your local.
  2. You have Jenkins installed and know how to basically use it
  3. You have Github (and CLI) with ssh keys set up.
  4. You have terraform installed
  5. You have Docker Installed
  6. Basic knowledge of EC2 and security groups
  7. A key pair already set up to utilize. In this example, mine is devops.pem
 
Our project directory will look like this by the end:
.
├── ansible
│   └── static-site
│   └── site.yaml
├── Jenkinsfile
├── nginx
│   ├── Dockerfile
│   └── static-site
│   ├── index.css
│   ├── index.html
│   └── nginx.conf
└── terraform
└── static-site
├── main.tf
├── terraform.tfstate
├── terraform.tfstate.backup
└── variables.tf
 
Prior to beginning, as always, setup your github repo and get ready to showcase your effort.
gh repo create scottyfullstack/nginx-jenkins-ansible-terraform
Then inside that git repo run the following to get the proper ignore file to ignore the terraform junk:
wget -O .gitignore https://raw.githubusercontent.com/github/gitignore/master/Terraform.gitignore

 Now here, you can go with below parts to complete the journey of the project:

Part 1: NGINX, OpenSSL, and the static site all bundled into Docker

Part 2 : Terraform

Part 3: Ansible and Dynamic Inventory

Part 4: Jenkins Pipeline

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more