I’ve been learning cloud technologies for a while, but there’s always been one thing that slows you down when managing infrastructure manually. Mistakes, inconsistencies, and time wasted configuring servers. That’s where Infrastructure as Code (IaC) comes in. For the next 30 days, I’ll be diving into Terraform as part of the 30-day Terraform challenge, and I want to share what I learn along the way.

What is Infrastructure as Code?

Infrastructure as Code is simply managing and provisioning your infrastructure through code rather than manual configuration. Instead of clicking around in the AWS console to create servers, networks, or databases, you write code that defines what you want.

The big advantage is consistency. Every time you run your code, you get the same environment. No more missing security settings, misconfigured instances, or forgotten network rules. Everything is repeatable, version-controlled, and reviewable.

Declarative vs Imperative Approaches

Imperative: You give step-by-step instructions. For example, “create a server, install software, configure settings.”

Declarative: You declare the final state you want, and the system figures out how to get there. For example, “I want a server with NGINX installed and this network configuration.”

Write on Medium
Terraform is declarative, which means I focus on describing what I need, and it handles all the steps behind the scenes. This makes deployments faster, safer, and easier to scale.

Why Terraform is worth learning

Terraform is cloud-agnostic, widely used, and integrates well with AWS, Azure, GCP, and more. Learning Terraform means I can confidently build infrastructure across different cloud platforms. It also makes it easy to collaborate with other engineers, because the infrastructure is just code.

For someone like me who wants to grow in my devops/cloud engineering career, mastering Terraform is a clear advantage. It’s the skill that lets me move from experimenting to delivering real solutions for businesses.

My goals for this 30-day challenge is to build tangible skills I can showcase. I want to:

• Understand Terraform deeply, not just superficially
• Build practical projects I can showcase on GitHub and portfolio
• Learn how to manage infrastructure efficiently on AWS
• Share my journey so others can follow along and maybe learn a few things from my mistakes

Conclusion

Today was all about setting up my environment and understanding the foundations. The next days will be about writing actual Terraform code, experimenting with AWS resources, and turning ideas into real infrastructure.

I’m excited to continue, and I’m looking forward to sharing progress, lessons, and challenges along the way. If you’re curious about Terraform or IaC, stay tuned.