Writing
Notes, collected
What I’m figuring out as I go. Cloud architecture, AWS security, and the tooling in between.
Dependency order is the real EKS deployment problem
Most failed Kubernetes platform rollouts aren't a tooling problem — they're a sequencing problem. A tool-agnostic way to think about what has to exist before what.
Read post →
The cloud comparison chart lied to you (a little).
Every 'AWS to Azure to GCP' cheat sheet does the same thing: it gives you a table. S3 equals Blob Storage. EC2 equals Compute Engine. Done, ship it. Except it's not done. The table tells you where to start, not where you'll get burned.
Read post →
Decoupling & Securing Web App Storage: Building a Zero-Trust S3 Perimeter with Terraform
When hosting a scalable, multi-AZ 3-tier web application (like WordPress), storing media files locally on the EC2 instances is an architectural dead end. The moment your auto-scaler destroys an instance, your user uploads vanish.
Read post → Least privilege is a design problem, not an audit finding
IAM policies get written last and reviewed never. Treating blast radius as an architecture constraint changes what you build, not just what you document.
Read post →Nothing matches that. Try a different word.