Behind the Builds

This is where I document the things AWS taught me, the things I broke, the things I fixed, and the things I still don’t fully understand but pretend I do. It’s part study notes, part troubleshooting diary, part therapy session for anyone who’s ever stared at an IAM policy and questioned their life choices.

CloudFront: The service that caches everything except my sanity

April 2026 • Troubleshooting, DevOps

Nothing humbles you quite like deploying your website, refreshing the page, and seeing… absolutely nothing change. For a solid hour I thought I’d broken the entire pipeline. Turns out CloudFront was just proudly serving the cached version like a stubborn librarian refusing to update the records.

The fix? Invalidation. The lesson? Always invalidate. The emotional damage? Ongoing.

IAM: The service that reminds me I know nothing

April 2026 • Security, Study Notes

IAM policies are like riddles written by someone who doesn’t want you to solve them. One minute everything works, the next minute AWS decides you’re not allowed to touch your own resources. I swear IAM has a personal vendetta against me.

But after enough trial, error, and questioning my life choices, I finally got my least‑privilege roles working. Progress.

GitHub Actions: It deployed… but did it really

April 2026 • CI/CD, DevOps

GitHub Actions told me everything was green. Success. Deployed. Beautiful. Except the website looked exactly the same. Turns out CloudFront doesn’t care what GitHub says — it will serve old content until you explicitly tell it otherwise.

Lesson learned: automate your invalidations or prepare for confusion.

The Great SVG Mystery: Why my icons refused to show

April 2026 • Frontend, Troubleshooting

I spent longer than I’d like to admit wondering why my icons weren’t appearing. Wrong filenames? Check. Wrong paths? Check. Browser caching? Oh yes. Turns out the browser was clinging to the old versions like a dragon guarding treasure.

Hard refresh saved the day. And now the icons look great.

Git and the CRLF Panic Attacks

April 2026 • Dev Tools, Study Notes

Git decided to warn me — loudly — about line endings. CRLF, LF, conversions, warnings everywhere. For a moment I thought I’d corrupted the entire repo. Spoiler: everything was fine. Git was just being dramatic.

The fix? Set core.autocrlf. The lesson? Don’t panic when Git shouts.