Today marks the start of my #30daysofAWSTerraform challenge! 🚀 Before writing code, I focused on understanding why we need Infrastructure as Code (IaC) and setting up a robust development environment.
We often underestimate the pain of manual clicking in the AWS Console—until we have to replicate an environment for Production and everything breaks. Terraform solves this by treating infrastructure as software.
✅ Tasks Completed:
Mastered IaC Concepts: Learned how Terraform solves the "It works on my machine" problem by ensuring consistency across Dev, Staging, and Prod.
Tooling Setup: Successfully installed Terraform CLI and verified the version.
Workflow Optimisation: Set up shell aliases (tf=terraform) and autocompletion to save time on future commands.
IDE Setup: Configured VS Code with the HashiCorp extension for better syntax support.
📝 Notes:
The Problem: Manual infrastructure takes hours/days and is prone to human error.
The Solution: Terraform interacts with Cloud APIs (like AWS) to provision resources automatically using HCL (HashiCorp Configuration Language).
Core Workflow: Write -> Plan (Dry Run) -> Apply (Create) -> Destroy (Clean up).
🔗 Resources:
My Code & Progress: https://github.com/Gokulprasath-N/Terraform-Full-Course-Aws
Video I watched: https://www.youtube.com/watch?v=xUtGqC-NXJE
I am excited to start writing actual HCL code tomorrow!
Top comments (0)