The Most Expensive Lie in Cloud Engineering
Teams keep telling themselves infrastructure is simple. “It’s just Terraform.” “A contractor can clean it up.” Here’s what those assumptions actually cost.
Read the essayEssays and practical guides from the engineers at Cloud Posse.
Teams keep telling themselves infrastructure is simple. “It’s just Terraform.” “A contractor can clean it up.” Here’s what those assumptions actually cost.
Read the essayLearn why building AWS infrastructure from scratch is more complex, slower, and riskier than teams expect — and how successful teams avoid common pitfalls to accelerate delivery.
Learn why SOC 2 compliance is an implementation problem, not a paperwork problem—and how the right AWS foundation turns controls into code and evidence into automation.
Why a battle-tested, opinionated reference architecture is a better starting point than building a custom AWS architecture from zero — and how successful teams avoid common traps.
Why developer experience in infrastructure is stuck — and why bringing frameworks to IaC is the key to moving faster, safer, and smarter in the cloud.
What makes Cloud Posse a uniquely credible, trustworthy partner for building AWS cloud platforms — and why engineering leaders at publicly traded companies, fintechs, and startups trust our model.
Twenty-one production infrastructure decisions, followed by concrete examples of addressing them with Atmos.
01 / The decisions
A guided checklist of every decision you'll make on the road from `terraform apply` to production. Not a recommendation — an education. Borrowed in spirit from Kelsey Hightower's 'Kubernetes the Hard Way.'
02 / The framework
The companion to 'Terraform the Hard Way.' Same twenty-one crossroads, framed against what each one looks like under a framework that's already made the decisions. With concrete Atmos snippets at every step.
Scanners are good at finding vulnerabilities. The hard part is managing what they find while engineering velocity keeps climbing. Here's why shift-left security has to mean guardrails, not gates.
An internal developer platform is the icing on the cake — the reward for getting the foundation underneath into shape. Here's what I've learned about when the icing actually delivers, and why a framework matters more than the portal.
There's an anxiety running through services businesses about AI. They have it backwards. When the busywork disappears, what's left is the part that actually matters.
AI is expanding the possibility space faster than we can build. Traditional metrics can't capture what's happening. Here's a new way to think about it.
Open source Terraform module libraries are infrastructure's equivalent of npm and PyPI—battle-tested foundations that become even more critical when AI enters the picture.
AI leveled the playing field. You don't need vendor platforms anymore. Here's what real infrastructure ownership looks like and why it's your strategic advantage.
Generative AI doesn't replace infrastructure as code—it supercharges it. Here's why IaC is the perfect foundation for agentic development.
Your lead engineer thinks 10 AWS accounts is overkill. Here's why starting clean is weeks of work, while untangling later is 6-12 months of migration pain.
Infrastructure as Code follows the same architectural principles software engineering established decades ago. Here's why service-oriented patterns fit infrastructure at enterprise scale.
Showing 9 of 20 articles
Erik Osterman
