📘 Terraform Series – Day 3

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 3 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 4

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

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 Blocks, Labels, and Arguments

In Day 2, we installed Terraform.
Now, before writing real infrastructure code, we must understand how Terraform actually reads and executes configurations.

👉 Every Terraform file is built using 3 core concepts:

Blocks
Labels
Arguments

🔹 1. What is a Block?

👉 A block is the main building unit in Terraform used to define infrastructure or configuration.

📌 Example:

resource "aws_instance" "my_vm" {
}

👉 Meaning:

Block tells Terraform what you want to create

📌 Common blocks:

resource
provider
variable
output

🔹 2. What are Labels?

👉 Labels are identifiers of a block that define resource type and name.

📌 Example:

resource "aws_instance" "my_vm" {
}

👉 Meaning:

aws_instance → resource type
my_vm → resource name

👉 Used to uniquely identify resources

🔹 3. What are Arguments?

👉 Arguments are key-value pairs inside a block used to configure the resource.

📌 Example:

instance_type = "t2.micro"

👉 Meaning:

Defines how the resource should be created
Controls behavior and properties

🔗 Combined Example

resource "aws_instance" "my_vm" {
  instance_type = "t2.micro"
}

👉 Breakdown:

Block → resource
Labels → aws_instance, my_vm
Argument → instance_type

👨‍💻 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 4

More from this blog

Terraform Blocks, Labels, and Arguments

🔹 1. What is a Block?

🔹 2. What are Labels?

🔹 3. What are Arguments?

👨‍💻 About the Author

📬 Let's Stay Connected