Day 3 of TerraWeek Challenge! 🔥

Task 1:- Create a Terraform configuration file to define a resource of AWS EC2 instance.

👉 Here's a basic Terraform configuration file (main.tf) to define an AWS EC2 instance resource:

# Configure the AWS provider
provider "aws" {
  region = "us-east-1" # Update with your desired region
}

# Define the AWS EC2 instance resource
resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0" # Update with your desired AMI ID
  instance_type = "t2.micro"              # Update with your desired instance type

  # Optionally, you can define more configurations such as tags, security groups, etc.
  tags = {
    Name = "ExampleInstance"
  }
}

In this configuration:

• We first configure the AWS provider to specify the region where the resources will be provisioned.

• Then, we define an AWS EC2 instance resource using the aws_instance block. Within this block, we specify the AMI ID (ami) and instance type (instance_type) for the EC2 instance.

• Additionally, we can provide optional configurations such as tags to further customize the instance.

Remember to replace placeholder values like AMI ID and region with your actual values. Also, ensure that you have appropriate AWS credentials configured either through environment variables or AWS shared credentials file (~/.aws/credentials).

Task 2 :- Check state files before running plan and apply commands & Use validate command to validate your tf file for errors and provide the Output generated by each commands.

👉 To check state files before running plan and apply commands and to use the validate command to validate your Terraform file for errors follow these steps:

1. Check State Files: Before running the plan or apply commands, it's essential to ensure that your Terraform state files are in a consistent and valid state. You can perform this check by using the terraform state list command.

    terraform state list
   

   This command lists all resources tracked in the Terraform state.

2. Validate Terraform Configuration: Before applying changes, it's crucial to validate your Terraform configuration files for syntax errors and potential issues. You can use the terraform validate command for this purpose.

    terraform validate
   

   This command checks the configuration files in the current directory for syntax errors and validates the configuration against provider requirements.

Here's the output generated by each command:

• Output of terraform state list:

    No state files found; aborting state list operation. This command can only be run in a directory with at least one state file. If you are using remote state, ensure that the remote state is available and then try again.
  

  This output indicates that no state files were found in the current directory, which is expected if you haven't initialized Terraform or applied any changes yet.

• Output of terraform validate:

    Success! The configuration is valid.
  

  

• This output indicates that the Terraform configuration files in the current directory are valid and contain no syntax errors.

By following these steps and validating your Terraform configuration files before applying changes, you can ensure that your infrastructure changes are based on a consistent and error-free configuration.

Task 3:- Add a provisioner to the configuration file to configure the resource after it is created and use Terraform commands to apply for changes and destroy to remove resources.

👉 To add a provisioner to the Terraform configuration file and use Terraform commands to apply changes and destroy resources, you can modify the main.tf file as follows:

# Configure the AWS provider
provider "aws" {
  region = "us-east-1" # Update with your desired region
}

# Define the AWS EC2 instance resource with a provisioner
resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0" # Update with your desired AMI ID
  instance_type = "t2.micro"              # Update with your desired instance type

  # Provisioner to execute a shell command after the instance is created
  provisioner "remote-exec" {
    inline = [
      "echo 'Hello, Terraform!' > /tmp/terraform_hello.txt"
    ]
  }

  # Optionally, you can define more configurations such as tags, security groups, etc.
  tags = {
    Name = "ExampleInstance"
  }
}

In this modified configuration:

• We've added a provisioner to the aws_instance resource using the provisioner block. The remote-exec provisioner allows you to execute shell commands on the newly created EC2 instance.

• The provisioner is configured to execute a simple shell command (echo 'Hello, Terraform!' > /tmp/terraform_hello.txt) after the instance is created. This command writes a message to a file (/tmp/terraform_hello.txt) on the instance.

• You can customize the provisioner and shell command as needed for your specific use case.

After adding the provisioner, you can use Terraform commands to apply changes and destroy resources:

1. Apply Changes: To apply the changes and create the AWS EC2 instance with the provisioner, use the terraform apply command:

    terraform apply
   

2. Destroy Resources: To remove the created resources (in this case, the AWS EC2 instance), use the terraform destroy command:

    terraform destroy
   

These commands will prompt you to confirm the changes before proceeding. Follow the prompts and review the changes carefully before applying or destroying resources.

Task 4:-Add lifecycle management configurations to the configuration file to control the creation, modification and deletion of the resource and use Terraform commands to apply the changes.

👉 To add lifecycle management configurations for controlling the creation, modification and deletion of resources in Terraform, you can use the lifecycle block within your resource definitions. Below is an example of adding lifecycle management configurations to an aws_instance resource in a main.tf configuration file:

# Configure the AWS provider
provider "aws" {
  region = "us-east-1"  # Update with your desired region
}

# Define the AWS EC2 instance resource
resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"  # Update with your desired AMI ID
  instance_type = "t2.micro"               # Update with your desired instance type

  # Optionally, you can define more configurations such as tags, security groups, etc.
  tags = {
    Name = "ExampleInstance"
  }

  # Lifecycle management configurations
  lifecycle {
    create_before_destroy = true

    # Ignore changes to specific attributes during updates
    ignore_changes = [
      # Ignore changes to the instance type
      instance_type,
      # Ignore changes to the tags
      tags,
    ]
  }
}

In this configuration:

• We've added a lifecycle block to the aws_instance resource.

• create_before_destroy = true ensures that Terraform creates a new instance before destroying the existing one during updates.

• ignore_changes specifies the attributes that Terraform should ignore when determining whether to update the resource. In this case, we're ignoring changes to the instance_type and tags.

After adding the lifecycle management configurations, you can use Terraform commands to apply the changes.

Apply Changes :- To apply the changes and update the resource with the new lifecycle configurations, use the terraform apply command:

terraform apply

This command will prompt you to confirm the changes before proceeding. Follow the prompts and review the changes carefully before applying them.

🚀 Ready to level up your Terraform skills? Stay tuned for Day 4 of our Terraform adventure, where we'll delve into more concepts . Whether you're a beginner or seasoned pro, there's always something new to discover in the world of Terraform. 🛠️💻

Let's connect and grow on Linkedin :Click Here

Let's connect and grow on Twitter :Click Here

Happy Terraform!!!!!

Happy Reading!!!!!

Sudha Yadav