“Just use aws” is starting to sound like bad advice in 2026

## The hidden cost: cognitive load and velocity loss The part nobody warns you about isn’t the bill. It’s the *brain tax*. AWS doesn’t just charge money it charges attention. Every new service you touch adds a little more surface area you have to remember, reason about, and explain to Future You when something breaks for reasons that feel personal. On paper, **Amazon Web Services** gives you infinite flexibility. In practice, that flexibility shows up as decisions you didn’t know you were signing up for. Networking models. Permission boundaries. Execution roles. Service limits. Quotas you only learn about by hitting them. None of these things are individually terrible. The problem is accumulation. I’ve lost more time than I want to admit debugging IAM policies that were technically correct but emotionally hostile. You start by wanting to give a service access to one thing, and an hour later you’re three tabs deep in docs, muttering “why is this denied” like it’s a personal betrayal. And that time adds up. Infra reviews start taking longer than feature planning. Pull requests get blocked not on logic, but on configuration. You hesitate to ship small changes because you’re not entirely sure which invisible meter they might spin. This is where velocity quietly leaks out. Not because AWS is slow but because *thinking about AWS* is slow. It pulls you out of product mode and into platform-operator mode, even when you never wanted that job.