Objective

Build the following architecture:

Prerequisites

Create S3 Buckets

Set up S3 buckets to store the Terraform state files and the image used by the web servers.

The Terraform state is stored in a bucket called acs730-final-nh in this project. You can use any globally unique name and update the value in the backend.tf files located under staging/aws_network and prod/aws_network. The buckets are already set in a way that the remote file of different environments is saved under different folders.

Another bucket named ansibleprojectassets has been created for this project. The ansible_terraform.jpeg image located under the assets folder has been uploaded to that bucket. This image will be displayed on the web servers deployed by Ansible. You can upload your own image to your own bucket and ensure you have access to it.

Install Terraform

Make sure you have Terraform installed. Refer to this documentation based on the environment you are using.

Deployment Instructions

Clone the repository using the command

git clone https://github.com/haingo-raz/terraform-git-automation.git

And navigate to the root directory.

Manual Deployment Instructions

Deploy the Network Infrastructure

1. Navigate to the staging/aws_network directory.
2. Initialize Terraform with the command: terraform init.
3. Deploy the network infrastructure by running: terraform apply.

Generate a Key Pair for Web Servers and Deploy Webservers

1. Navigate to the staging/aws_webservers directory.
2. Delete the nh.pub from the staging/aws_webservers directory because you will create your own keypair.
3. Create a key pair named nh in the aws_webservers folder using the command: ssh-keygen -t rsa -f nh.
4. Initialize Terraform with the command: terraform init.
5. Deploy the web server infrastructure by running: terraform apply.

Install Ansible and required libraries

1. Install ansible using the command: sudo yum install -y ansible
2. Install Python and Required Libraries (boto3, botocore)
   First, make sure pip3 is installed: sudo yum install -y python3-pip
   Then, install the required Python libraries: pip3 install boto3 botocore

Install Amazon AWS Collection for Ansible

Install the Amazon AWS Ansible collection using:ansible-galaxy collection install amazon.aws

Run the Playbook

• Make sure you have access to the keypair you created when deploying the terraform infrastructure.
• Change the path of the inventory file in the ansible.cfg file according to your file organization.
• Once everything is installed, navigate in the ansible directory and run the playbook to set up the web server: ansible-playbook playbooks/webserver_setup.yml

Automatic Deployment with GitHub Actions

The GitHub Actions workflow will automatically deploy your infrastructure whenever changes are pushed/merged to the prod branch.

Configure AWS Credentials in GitHub

1. Go to the repository's Settings > Environments
   
2. Create two environments prod and staging.
3. Add the following Environment secrets in each environment:
   

AWS_ACCESS_KEY_ID="your-access-key-id"
AWS_SECRET_ACCESS_KEY="your-secret-access-key"
AWS_SESSION_TOKEN="your-session-token" 

These credentials will allow GitHub Actions to interact with AWS during the deployment process.

Push Changes to Trigger Deployment

1. Create Pull Request from Staging to prod branch. After merging changes to the prod from staging branch, the GitHub Actions workflow will automatically:
   Initialize Terraform: Run terraform init in both aws_network and aws_webservers directories.
   Plan Changes: Run terraform plan to preview the changes.
   Apply Changes: Run terraform apply to deploy the infrastructure to AWS.
   

Changes to the staging/aws_network and staging/aws_webservers directories will trigger this workflow.

Branch Protection

Direct pushes to prod are prohibited to ensure all changes are thoroughly reviewed and tested through GitHub Actions workflows before deployment.

Monitor Deployment

You can monitor the progress of the GitHub Actions workflow directly in the Actions tab of the GitHub repository.

Clean Up Instructions

Destroy the Infrastructure

1. Navigate to the staging/aws_webservers directory.
2. Destroy the infrastructure with command: terraform destroy -auto-approve.
3. Navigate to the staging/aws_network directory.
4. Destroy the infrastructure with command: terraform destroy -auto-approve.

Clean Your Workspace

1. Delete the S3 bucket used to store the Terraform remote state files.
2. Delete the S3 bucket containing the image displayed on the web servers if relevant.