The Future of Artificial Intelligence

Infrastructure as Code (IaC)

Introducing Terraform

Installing Terraform

Set-ExecutionPolicy Bypass -Scope Process -Force;
[System.Net.ServicePointManager]::SecurityProtocol=[System.Net.ServicePointManager]::SecurityProtocol -bor 3072;
iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

choco install terraform

terraform --version

on the CLI.

Agenda

Terraform Providers

providers.tf

file, and add in the following.

terraform {
    required_version="~> 1.9.5"required_providers {
        aws= {
            source="hashicorp/aws"version="~> 5.64.0"
        }
    }
}

provider "aws" {
    region="us-east-1"default_tags {
        tags= {
            Environment="staging"Owner="Mukesh Murugan"Project="codewithmukesh"
        }
    }
}

us-east-1

and mention some default tags that will be added to every resource we create. We will be adding tags such as Environment, Owner, and Project. This instructs Terraform to use AWS as the provider and deploy the resources to the

us-east-1

region.

Writing Your First S3 Bucket on Terraform

buckets.tf

and add the following.

resource "aws_s3_bucket""codewithmukesh" {
    bucket="codewithmukesh-bucket"
}

Terraform Lifecycle & CLI Commands

terraform init

terraform plan

terraform apply

terraform apply -auto-approve

to skip the prompt. However, use this with caution.

terraform show

terraform destroy

terraform state

terraform fmt

terraform validate

terraform output

Workflow

1. terraform init

   .

2. terraform plan

   .

3. plan

   command, you would want to apply these changes to your actual infrastructure by running the

   terraform apply

   command.

4. terraform destroy

   command.

Authenticate Terraform to Manage Resources in AWS

providers

block to include the AWS Credentials (Secret Key & Access Key) or make use of the AWS CLI Profile to ensure that your development machine is authenticated.

provider "aws" {
    region="us-west-2"access_key="my-access-key"secret_key="my-secret-key"
}

provider "aws" {
    region="us-west-2"profile="mukesh"
}

mukesh

and referred to it under the provider block. This allows Terraform CLI to use the AWS Profile configuration and authenticate into AWS to manage resources.

Deploy S3 Bucket

1. terraform init

   .

2. terraform plan

   command.

aws_s3_bucket.codewithmukesh will be created

along with its internal properties.

terraform plan

command is used to create an execution plan, which is essentially a preview of the changes Terraform will make to your infrastructure. Terraform retrieves the current state of your infrastructure (from the state file or the actual infrastructure) and compares it to the desired state defined in the configuration files. Based on the comparison, Terraform determines the actions needed to align the current infrastructure with the desired state. These actions can include creating, updating, or deleting resources.

terraform plan

only generates the plan; it does not make any changes to the infrastructure. It simply shows you the proposed changes, allowing you to review them before applying.

3. terraform plan

   , run a

   terraform apply

   to apply your infrastructure changes. In the next prompt, type in

   yes

   to confirm the deployment. I usually use

   terraform apply -auto-approve

   to skip this confirmation prompt.

Terraform Variables

.tf

files.

Types of Variables

• true

  or

  false

  ).

• ["a", "b", "c"]

  ).

• { key1="value1", key2="value2" } 

  ).

Defining Variables

.tf

file using the

variable

block. Let’s learn this by implementing it. Create a new file named

variables.tf

and add in the following.

variable "region" {
    description="The AWS region to deploy resources in"type=string default="us-east-1"
}

var. { variable_name } 

. In our case, the right place to use the

region

variable would be the

providers.tf

file, where we have hard-coded the region property to

us-east-1

. You can modify the provider block as follows.

provider "aws" {
    region=var.region default_tags {
        tags= {
            Environment="staging"Owner="Mukesh Murugan"Project="codewithmukesh"
        }
    }
}

Setting Variables

2. terraform apply -var="region=us-east-1"

   .

3. TF_VAR_< variable_name> 

   environment variable. Run

   export TF_VAR_region="us-east-1"

   .

4. terraform apply -var-file="variables.tfvars"

   .

Terraform Output

Defining Outputs

output "bucket_name" {
    description="The name of the S3 bucket"value=aws_s3_bucket.my_bucket.id
}

terraform apply

command is completed. Here is what shows up after I apply my Terraform changes.

terraform output

command to retrieve outputs at any time.

State Management

terraform plan

or

terraform apply

, Terraform compares the real-world infrastructure to the state file to determine what changes are necessary.

terraform.tfstate

,

terraform.tfstate.backup

, and so on.

Why is the State Important?

Remote Backend with S3 & DynamoDB

Setting Up a Remote Backend with S3 & DynamoDB

cwm-tfstates

for this purpose.

cwm-state-locks

with the partition key as

LockID

(string) using the Management Console. This table will handle locking, ensuring safe, concurrent use of the state.

terraform destroy

command that your resources are cleaned up, and delete the

terraform.tfstate

files.

main.tf

and add in the following.

terraform {
    backend "s3" {
        bucket="cwm-tfstates"key="demo/beginners-guide/terraform.tfstate"region="us-east-1"dynamodb_table="cwm-state-locks"encrypt=true
    }
}

terraform init

command. But before that, run a

terraform destroy

command that your resources are cleaned up, and delete the

terraform.tfstate

files.

terraform plan

or

terraform apply

, terraform will cross-check the state file present in the remote backend (s3 & dynamodb) to decide on how the resource has to be modified. With every

terraform apply

command, the state file available on S3 is updated.

Benefits of Remote State Management with S3 and DynamoDB

Deploy EC2 Instance

ec2.tf

and try to find out the required code from the terraform documentation.

resource "aws_instance""demo" {
    ami="ami-066784287e358dad1"instance_type="t3.micro"
}

Destroy Resources

terraform destroy

to destroy all the resources created via terraform for the current state.

What’s Next?