I love programming and after exploring cloud and devops, I was almost giving up but terraform is sparking my interest again.
I think I’m one of the few people who actually enjoy a formal introduction to things. Today was my official introduction to Terraform. I explored why Terraform exists, the problems it solves, the old-school way people used to interact with cloud platforms, and why Infrastructure as Code matters in modern engineering.

If Terraform or IaC still sound new to you, here’s the simplest update: Infrastructure as Code is a way to create cloud resources using code instead of clicking around dashboards. Terraform is the most popular tool for this, letting you describe the infrastructure you want and then letting Terraform talk to the cloud provider on your behalf. Get started with terraform here.
This session felt more like discovering the idea behind Terraform rather than building something. I spent time understanding the workflow, the concepts, and why engineers rely on automation instead of manual actions.
The main thing I learned today was Terraform’s basic workflow:
-
terraform init- Set up the working directory -
terraform validate- Check for syntax and configuration issues -
terraform plan- Preview what changes Terraform will make -
terraform apply- Execute the plan and create/update resourcesstate -
terraform destroy- Remove infrastructure when you no longer need it
terraform destroy is my favorite for now. It feels like giving orders to tiny minions that quickly tear down everything so you don’t accidentally keep resources running and racking up costs.
I clearly understand that IaC tools are basically talking to cloud APIs for us. And with that, you can create repeatable, scalable infrastructure without the stress of manual setup.
Piyush, my wonderful instructor whom I recently encounted on youtube, explained this in a way that clicks for me.
You can check out his video.
And if you like a supportive learning environment, the cloudops community is worth joining. It’s full of motivated engineers, learners, and enthusiasts.
It's a 30 day challenge to learn and use terraform and I’m doing this challenge to improve my Terraform and AWS skills, but also to sharpen my writing. I’m excited to look back at the end and see how far I’ve come.
Today I've just known about terraform. and talked about it and it's possibilites. Tomorrow we plan on provisioning some infrastructure with it. I'd love to see the magic. I'll command, apply! and watch how the infrastructure comes alive. Join the #30daysofawsterraform challenge and upskill too.
Top comments (1)
Thanks for Reading