Day 25: AWS Cloud Resume Challenge
The Project Was Complete, Except It Couldn't Tell Me When It Broke Every AWS resource in Terraform. A CI/CD pipeline ran clean, tests gated every deploy, and zero credentials were stored. By most meas
Alfiya | Cloud & DevOps Developer Blog
Documenting my hands-on journey through AWS, DevOps, and Infrastructure as Code.
Latest articles
Day 24: AWS Cloud Resume Challenge
Getting the Pipeline From Designed to Actually Running Yesterday I designed the pipeline. Today was about actually getting it to run — which turned out to be its own separate challenge, full of small,
Day 23: AWS Cloud Resume Challenge
Started the CI/CD phase today — two GitHub Actions workflows, one for my frontend, one for backend. Here's how I actually thought through each decision. Keeping Terraform and Deployment Separate The f
Day 22: AWS Cloud Resume Challenge
The Whole Project Is Actually in Terraform Now This one closes out something that started back on Day 14 — turning every piece of infrastructure I'd clicked together by hand into real, working Terrafo
Day 21: AWS Cloud Resume Challenge
The Firewall I Didn't Know I Had Today was supposed to be the last resource in this whole Terraform project — the CloudFront distribution itself. It was, but not before one wrong command and one real
Day 20: AWS Cloud Resume Challenge
Route 53, a Second Provider, and My First Multi-Region Resource Two sessions' worth of work today — Route 53 from last night, which I was unable to post until too late, but better to have it, and the
Day 19: AWS Cloud Resume Challenge
Today I finished writing the last piece of my backend in Terraform — API Gateway. Four small resources, all coded, all imported cleanly. Then I ran terraform plan to double-check everything, and the o
Day 18: AWS Cloud Resume Challenge
My last post ended with a plan: lock down public access on my S3 bucket, then move on to CloudFront and ACM. That's not quite what happened. Eight days passed, and instead of a straight line to CloudF
Day 17: AWS Cloud Resume Challenge
The Two-Day Detour I Didn't Plan For This one took longer than I thought — two days, not the quick "import and move on" I expected after Day 16. I want to write about it honestly, even though it wasn'
