Search for a command to run...
Series
This series contains my journey where I learn Terraform from scratch and share my progress every single day. My goal is to stay consistent, learn at a steady and honest pace, and hopefully complete all 30 days.
#30daysofawsterraform By the time I reached Day 10, Terraform had already stopped feeling like a tool for “just creating resources.” Days 8 and 9 changed that mindset completely. Meta-arguments taught
#30daysofawsterraform By the time I reached Day 9, Terraform had already started changing the way I think about infrastructure. Day 8 was a big moment — meta-arguments like count and for_each showed me how Terraform can generate infrastructure dynami...
#30daysofawsterraform Day 8 was one of those days where you suddenly see Terraform not just as a way to describe infrastructure, but as a tool that can generate it — based on patterns and inputs instead of copy-paste blocks. Up until now, each AWS re...
#30daysofawsterraform By Day 7, Terraform usage starts to resemble real production workflows. You now have structured code, reusable modules, variables, and clean repositories. The next problem becomes obvious: how do you manage multiple environments...
#30daysofawsterraform By Day 6, Terraform starts to demand a different mindset.Up until now, writing everything in a single directory worked fine. Variables improved flexibility, remote state improved reliability, but the structure was still flat. Th...
#30daysofawsterraform By Day 5 of this journey, you’ve already stood up infrastructure, handled remote state, and built a foundation of reusable Terraform configurations. But real Infrastructure-as-Code isn’t just about what you build — it’s about ho...
