Infrastructure as Code and Jenkins

# CHAPTER 17

Infrastructure as Code and Jenkins #

1. Introduction #

2. Learning Objectives #

• Define Infrastructure as Code (IaC) and its operational benefits.

• Differentiate between Provisioning (Terraform) and Configuration Management (Ansible).

• Understand how Jenkins orchestrates the execution of IaC tools.

• Configure a declarative pipeline to deploy AWS infrastructure automatically.

• Understand the concept of "Immutable Infrastructure."

3. Beginner-Friendly Explanation #

• Terraform (The Architect & Construction Crew): Terraform looks at a blueprint (Code) and builds the physical structure. It pours the concrete, builds the walls, and installs the plumbing. (In the cloud, it creates the raw Linux server, the database, and the firewall).

• Ansible (The Interior Designer): Ansible walks into the empty rooms built by Terraform. It paints the walls, arranges the furniture, and stocks the mini-fridge. (In the cloud, it logs into the empty Linux server, installs Apache, configures PHP, and starts the web service).

• Jenkins (The General Contractor): Jenkins is the boss. Jenkins reads the master plan and tells Terraform to build the building, and the moment it is finished, tells Ansible to furnish it.

4. Terraform Basics (Provisioning) #

# Example main.tf
resource "aws_instance" "web" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "HelloWorld"
  }
}

If you run terraform apply, Terraform talks to the AWS API and creates this exact server.

5. Ansible Basics (Configuration) #

# Example playbook.yml
- hosts: webservers
  tasks:
    - name: Ensure Apache is installed
      apt:
        name: apache2
        state: present

6. Mini Project: Deploy Infrastructure Automatically #

Step-by-Step Pipeline Concept:

pipeline {
    agent any
    stages {
        stage('Initialize Terraform') {
            steps {
                // Downloads necessary cloud provider plugins
                sh 'terraform init'
            }
        }
        stage('Terraform Plan') {
            steps {
                // Calculates what will change (e.g., "I will create 1 server")
                sh 'terraform plan -out=tfplan'
            }
        }
        stage('Approval') {
            steps {
                // Pauses the pipeline. A human must review the plan and click "Approve"
                input message: 'Review the plan. Approve deployment to AWS?'
            }
        }
        stage('Terraform Apply') {
            steps {
                // Executes the plan and actually builds the server
                // We use withCredentials (Chapter 14) to inject the AWS API keys!
                withCredentials([aws(credentialsId: 'my-aws-keys', accessKeyVariable: 'AWS_ACCESS_KEY_ID', secretKeyVariable: 'AWS_SECRET_ACCESS_KEY')]) {
                    sh 'terraform apply -auto-approve tfplan'
                }
            }
        }
    }
}

7. Real-World Scenarios #

8. Best Practices #

• Immutable Infrastructure: When a server needs a software update, do not use SSH to log in and update it. Instead, use Jenkins and Terraform to destroy the old server entirely and instantly replace it with a brand-new server containing the updated software. This prevents "Configuration Drift," where servers slowly degrade over time due to manual tweaks.

9. Security Recommendations #

• State File Security: Terraform relies on a "State File" (terraform.tfstate) to remember what it built. This file often contains highly sensitive data, including plaintext database passwords generated during infrastructure creation. Never commit the state file to Git. Jenkins must configure Terraform to store this file in a secure, encrypted remote backend (like an AWS S3 bucket with strict IAM access).

10. Troubleshooting Tips #

• Jenkins Plugins: To make managing AWS credentials easier, install the "CloudBees AWS Credentials" plugin in Jenkins. It provides the withCredentials([aws(...)]) syntax used in the mini-project, automatically handling the secure injection of the environment variables Terraform requires.

11. Exercises #

1. 1. Contrast the operational purposes of Terraform (Provisioning) and Ansible (Configuration Management).

1. 2. Explain the concept of "Configuration Drift" and how Infrastructure as Code (IaC) prevents it.

12. FAQs #

13. Interview Questions #

• Q: Describe a comprehensive CI/CD pipeline architecture that integrates Terraform and Ansible. How do you handle the handoff of dynamically generated infrastructure IPs from Terraform to the Ansible inventory file within the Jenkins workspace?

• Q: Why is the manual input approval stage critical between a terraform plan and terraform apply step within a Jenkins pipeline? What risk does it mitigate?

14. Summary #

15. Next Chapter Recommendation #