From Manual Clicking to Infrastructure as Code: My Terraform & CloudFormation Journey — Like Leveling Up in Zelda
The Quest Begins (The "Why") Honestly, I used to feel like I was stuck in a never‑ending tutorial level. Every time we spun up a new environment — dev, staging, prod — I’d hop into the AWS console, click through a dozen screens, pray I didn’t miss a checkbox, and then spend the next hour documenting what I just did so the next person wouldn’t have to repeat my misery. It was tedious, error‑prone,…
The story begins with the author feeling trapped in a never-ending tutorial, manually spinning up environments in the AWS console, clicking through screens and praying nothing was missed. After yet another error triggering a late-night pager, the author realized there must be a better way. The revelation came when they understood Infrastructure as Code (IaC) isn't just about automating clicks, but describing the desired state of infrastructure and letting tools figure out the implementation.
Terraform and CloudFormation were highlighted as popular tools for this approach, each with its own strengths. Terraform is cloud-agnostic, using HCL, while CloudFormation is native to AWS, using JSON or YAML. The author demonstrates this with an example of creating an S3 bucket with versioning and public read access. The manual process involved numerous clicks and manual documentation, while the Terraform code snippet shows a clean, repeatable, and secure implementation.
The CloudFormation YAML template shows a similar outcome, but with a pitfall of using a deprecated AccessControl parameter instead of a policy. The final version corrects these issues, emphasizing the benefits of IaC, such as reproducible environments, automated security best practices, and safe state management.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
