📘 Terraform Series – Day 4

UpdatedApril 19, 2026

Gujjar Apurv is a passionate DevOps Engineer in the making, dedicated to automating infrastructure, streamlining software delivery, and building scalable cloud-native systems. With hands-on experience in tools like AWS, Docker, Kubernetes, Jenkins, Git, and Linux, he thrives at the intersection of development and operations. Driven by curiosity and continuous learning, Apurv shares insights, tutorials, and real-world solutions from his journey—making complex tech simple and accessible. Whether it's writing YAML, scripting in Python, or deploying on the cloud, he believes in doing it the right way. "Infrastructure is code, but reliability is art."

Comments

Join the discussion

No comments yet. Be the first to comment.

Terraform

Part 4 of 12

🚀 Terraform Series – Automate Your Infrastructure Starting a complete **Terraform series** where I’ll cover everything from **basic to advanced level** with real-world practicals. In this series, you will learn: • What is Infrastructure as Code (IaC) & why it matters • Terraform fundamentals (providers, resources, state) • Writing and managing Terraform configurations • Variables, outputs & modules • Remote state & state management • Provisioning infrastructure on AWS • Automation & real-world use cases • Advanced concepts like workspaces, modules, and best practices 🎯 Goal: Help you automate infrastructure and become job-ready in DevOps. Perfect for **beginners, students, and DevOps learners** who want hands-on experience. Stay tuned and let’s build infrastructure the smart way ⚡💻 #Terraform #DevOps #Cloud #AWS #InfrastructureAsCode #Automation

Up next

📘 Terraform Series – Day 5

Terraform Providers, Resource Types & Naming In today’s Terraform journey, I explored one of the most fundamental concepts that every DevOps engineer must understand Providers and Resource Naming Stru

More from this blog

Day 6 : Variables, Secrets, Artifacts & Complete CI/CD Workflow

Master GitLab CI/CD Variables, Secrets Management, Artifacts & Best Practices 📖 Introduction In the previous article, we learned how GitLab Runners execute CI/CD pipelines and how to configure Self-H

Jul 26, 20264 min read

Day 6 : Variables, Secrets, Artifacts & Complete CI/CD Workflow

Day 5 : GitLab Runners & Pipeline Execution

Learn GitLab Runners, Hosted vs Self-Hosted Runners, Runner Registration, Tags, Pipeline Editor & Parallel Jobs 📖 Introduction In the previous article, we created our first GitLab CI/CD pipeline and

Jul 26, 20267 min read5

Day 5 : GitLab Runners & Pipeline Execution

Day 4 GitLab CI/CD Pipelines

Learn Continuous Integration, Continuous Delivery, Pipelines, Stages, Jobs & .gitlab-ci.yml 📖 Introduction In the previous articles, we explored GitLab fundamentals, repository management, and collab

Jul 26, 20268 min read

Docker Scout, Hardened Images, AI & Supply Chain Security

Learn Docker Scout, Multi-Stage Builds, Docker Hardened Images (DHI), SBOM, Docker Model Runner, Ask Gordon AI, and production-ready container security through practical, real-world examples. Introduc

Jul 22, 202618 min read43

Docker Scout, Hardened Images, AI & Supply Chain Security

Day 3: Working with GitLab Repositories

Import Repositories, Mirroring & Repository Management Best Practices 📖 Introduction In the previous articles, we learned the fundamentals of GitLab, created projects, and configured secure authentic

Jul 19, 20268 min read9

Apurv Gujjar

33 posts

Sharing hands-on DevOps, AWS, and Cloud tutorials with real-world projects, tips, and automation guides for students and professionals.

Terraform Workflow: init, validate, plan, apply & destroy

🧠 Before Starting (AWS Setup)

Before using Terraform with AWS, we first need to configure AWS access on our local machine.

👉 Steps:

Install AWS CLI

Configure AWS using:

aws configure

👉 It will ask for:

AWS Access Key
Secret Key
Region
Output format

✅ After this setup, Terraform can interact with your AWS account.

🎯 Objective

Understand Terraform workflow
Learn core commands
Perform hands-on execution

🧱 Step 0: Create Terraform Configuration File

👉 Create a file:

main.tf

👉 This file contains your Terraform infrastructure code

⚙️ Step 1: Initialize Terraform

🔹 Command:

terraform init

🔹 Purpose:

Initializes working directory
Downloads required providers
Prepares environment

✅ Step 2: Validate Configuration

🔹 Command:

terraform validate

🔹 Purpose:

Checks syntax of .tf files
Ensures configuration is valid

👉 “Check if your code is correct”

📊 Step 3: Review Execution Plan

🔹 Command:

terraform plan

🔹 Purpose:

Shows what Terraform will do
Lists resources to create/change/destroy
Works as a dry run

👉 “Preview before execution”

🚀 Step 4: Apply Configuration

🔹 Command:

terraform apply

🔹 Purpose:

Executes the plan
Creates real infrastructure

👉 Type yes to confirm

🧨 Step 5: Destroy Infrastructure

🔹 Command:

terraform destroy

🔹 Purpose:

Deletes all resources
Avoids unnecessary cloud cost

⚡ Auto-Approve Option

terraform apply -auto-approve
terraform destroy -auto-approve

👉 Skips confirmation

👉 Useful in automation (CI/CD)

👨‍💻 About the Author

“A complete Terraform series covering everything from fundamentals to advanced real-world infrastructure automation in a DevOps environment.”

📬 Let's Stay Connected

📧 Email: gujjarapurv181@gmail.com
🐙 GitHub: github.com/ApurvGujjar07
💼 LinkedIn: linkedin.com/in/apurv-gujjar

Command Palette

Comments

Terraform

📘 Terraform Series – Day 5

More from this blog

Terraform Workflow: init, validate, plan, apply & destroy

🧠 Before Starting (AWS Setup)

🎯 Objective

🧱 Step 0: Create Terraform Configuration File

⚙️ Step 1: Initialize Terraform

✅ Step 2: Validate Configuration

📊 Step 3: Review Execution Plan

🚀 Step 4: Apply Configuration

🧨 Step 5: Destroy Infrastructure

⚡ Auto-Approve Option

👨‍💻 About the Author

📬 Let's Stay Connected