Day-1 | Terraform Zero to Hero | Getting Started with Terraform | #abhishekveeramalla #terraform

Overview of the video (Day-1: Terraform Zero to Hero)

• The speaker (Abhishek) introduces a 7-day Terraform “Zero to Hero” series with no prerequisites—you don’t need prior Terraform knowledge.
• Course content (including a day-by-day syllabus) is provided in a GitHub repository via a readme.md.
• An optional “Day Zero” video is mentioned to explain the overall course structure.

---

Day 1 learning goals / tutorial breakdown

1. Infrastructure as Code (IaC)

   • Defines IaC and explains how Terraform fits into the concept.

2. Why Terraform is important for DevOps/Cloud engineers

   • Positioned as a required/mandatory skill due to multi-cloud needs and rapidly scaling infrastructure.

3. Terraform installation

   • Install Terraform on Mac, Linux, and Windows.
   • Includes a “surprise” option for users who can’t (or shouldn’t) install locally.

4. Set up Terraform for AWS

   • Covers the authentication workflow using AWS CLI / credentials before Terraform runs.

5. Write and run a first Terraform configuration

   • Demonstrates creating an AWS EC2 instance.

6. Terraform lifecycle (high-level)

   • Covers terraform init, terraform plan, terraform apply, and terraform destroy.

7. Basic Terraform state file concept

   • Introduces terraform.tfstate as the local record Terraform uses for future runs/diffs/destroy.

---

Key technological concepts explained

1. Infrastructure as Code & APIs

• Explains two ways to create AWS resources:
  • Manually in the AWS console
  • Programmatically via:
    • AWS APIs / AWS CLI (automation through code)
• Highlights a challenge: automation typically requires programming knowledge, and real infrastructure setups (e.g., VPC, EC2 HA, S3 endpoints) can become complex.

2. Cloud provider IaC tooling (comparative)

• Notes that each provider has its own IaC mechanism, including:
  • AWS CloudFormation templates (JSON/YAML)
  • Azure Resource Manager (JSON/YAML)
  • OpenStack Heat templates

3. Why Terraform specifically (universal approach)

• Terraform is presented as a universal IaC tool:
  • Learn Terraform once using HCL
  • Then target different providers (AWS/Azure/GCP) by configuring the provider
• The main pitch: Terraform reduces the need to learn multiple provider-specific IaC systems.

4. Terraform competitors

• Mentions alternatives like Crossplane and Pulumi.
• Claims Terraform has advantages such as:
  • Largest market presence
  • Mature/simpler ecosystem
  • Strong community and adoption

---

Installation + “surprise” practical setup (GitHub Codespaces)

• Provides Terraform installation steps for Mac/Linux/Windows using official download commands.
• For Windows users: recommends using Git Bash instead of default CMD to avoid common issues.
• For users who can’t use a laptop or face installation restrictions:
  • Use GitHub Codespaces (free for ~60 hours/month)
  • In Codespaces, install required tools via a Dev Container configuration, including:
    • Terraform
    • TF Lint
    • Terraform-docs-like tooling
    • AWS CLI
• Mentions typical devcontainer setup steps:
  • Adding devcontainer configuration files and rebuilding the container

---

AWS authentication workflow before Terraform

• Recommends using an IAM user instead of root (noted as best practice), though the demo uses root for illustration.
• Uses AWS Access Key ID + Secret Access Key via aws configure.
• Verifies credentials with:
  • aws s3 ls
• Key distinction:
  • AWS CLI authentication is not the same as Terraform AWS provider authentication yet.
  • Terraform provider setup (in .tf) happens next.

---

First Terraform script: creating an EC2 instance

Terraform file structure / naming

• Uses main.tf as the main configuration file (by convention).
• The code includes:
  1. Provider block
     • Specifies AWS and region (example: us-east-1, “Us East one”).
  2. Resource block
     • Defines the resource as an AWS EC2 instance.

Using Terraform documentation as a guide

• The speaker recommends copying resource syntax from Terraform documentation, e.g.:
  • Search for “terraform AWS ec2” / “ec2 instance resource”
  • Copy the example and simplify it as needed

Commands and lifecycle

• terraform init
  • Initializes provider plugins and reads config
  • Must run from the correct directory (example: into day one / project)
• terraform plan
  • Dry run showing what will be created/changed/destroyed
  • The demo intentionally triggers errors to teach debugging (e.g., missing credentials after deliberate deletion)
• terraform apply
  • Applies changes after confirmation
  • The demo again intentionally triggers errors to demonstrate common failure causes
• terraform destroy
  • Cleanup at the end to avoid leaving cloud resources running

---

Debugging lessons shown (intentional mistakes)

1. AMI missing / incorrect

   • If the AMI doesn’t exist, AWS rejects instance creation.
   • Shows using AWS Console to find the correct AMI IDs.

2. Missing subnet / VPC configuration

   • Error example: “no subnets found for default VPC… specify a subnet”
   • Fix: set subnet_id using an existing subnet from the default VPC.

3. SSH key pair requirement

   • Adds an EC2 key pair name because the instance configuration expects it.

---

Tooling/IDE support: HCL plugin

• Recommends installing VS Code extensions:
  • HashiCorp Terraform / HCL syntax support
• Demonstrates the benefit:
  • Autocomplete suggestions (e.g., when typing subnet_id)

---

Terraform state file: what it is and why it matters (basic intro)

• Terraform creates terraform.tfstate during execution.
• Terraform updates it with details about created infrastructure.
• Why it matters:
  • Future Terraform runs use the state file to understand previously managed resources
  • Enables update and destroy workflows
• Mentions upcoming topics in later parts of the series:
  • Securing sensitive info in state
  • Remote state vs local state
  • CI/CD considerations involving state

---

Assignment / recap at the end

• Suggests using the GitHub repository’s Day 1 project files (already uploaded).
• Notes the demo intentionally leaves out some configuration (like subnet/key pair) so viewers can practice fixing errors and successfully running Terraform.
• Final recap of the lifecycle:
  • init → plan → apply → destroy

---

Main speakers / sources

• Speaker: Abhishek (host/channel)
• Primary referenced sources:
  • Terraform documentation (used for copying EC2 resource syntax)
  • AWS services/docs/console concepts
• Supporting materials:
  • GitHub repo “Terraform Zero to Hero” (readme.md, install.md, and Day 1 project files)
  • GitHub Codespaces devcontainer configuration guidance