Skip to content

Terraform Learning Tracker

Use this page while learning Terraform from KodeKloud.

After each lesson, try to capture:

  • what the topic was
  • what command or block syntax you saw
  • 3 to 8 keywords to revise later
  • one small thing that was confusing
  • one thing you can now explain without looking

Suggested learning topics

  • Infrastructure as Code (IaC) basics
  • Terraform workflow: init, plan, apply, destroy
  • Providers
  • Resources
  • Variables
  • Output values
  • Data sources
  • Locals
  • State file
  • Remote backend
  • State locking
  • Modules
  • Input validation
  • Functions and expressions
  • count
  • for_each
  • depends_on
  • lifecycle
  • Workspaces
  • Provisioners
  • Import existing resources
  • Drift detection
  • Terraform formatting and validation

Keyword bank

Add new words here whenever you hear them in class.

Topic Keywords
Terraform basics IaC, declarative, provider, resource block, execution plan, state
Variables and outputs input variable, default, type, sensitive, output, tfvars
State and backend terraform.tfstate, remote state, backend, locking, DynamoDB, migration
Modules reusable code, root module, child module, source, version, composition
Meta-arguments count, for_each, depends_on, lifecycle, provider
Validation and quality terraform fmt, terraform validate, linting, policy, drift

Lesson log

Lesson 01

Topic learned:
Summary:
Commands / syntax:
Keywords:
What confused me:
What I understand now:

Lesson 02

Topic learned:
Summary:
Commands / syntax:
Keywords:
What confused me:
What I understand now:

Reusable template

Copy this block whenever you finish a new lesson:

### Lesson XX

**Topic learned:**  
**Summary:**  
**Commands / syntax:**  
**Keywords:**  
**What confused me:**  
**What I understand now:**

Quick topic hints

Use these prompts when you want to expand a lesson into a proper note:

  • Why do we need this Terraform feature?
  • What problem does it solve?
  • What is the most common command or block used with it?
  • What can go wrong in real projects?
  • How would I explain this in an interview?