An important reminder from our Director of Operations and Cloud Expert, effective AWS cost management is not simply a matter of discipline. Read his full reflection here ⬇️
Strong take on the cultural shift required for FinOps: Treating cost efficiency as a first-class engineering concern, rather than an afterthought for finance, is the only way to scale sustainably. Where I tend to see friction is at the execution layer. Turning compute on and off relentlessly sounds ideal in theory. In practice, if ephemeral environments begin slowing down CI/CD pipelines, developers will naturally resist. Discipline rarely survives a tight sprint deadline if it creates bottlenecks. There is also a hidden layer of architectural waste that stems from access friction. When teams struggle with complex IAM role assumptions or cross-account permissions, the instinct is often to duplicate resources or build inefficient network workarounds just to get code deployed. Over time, those shortcuts quietly inflate the bill. This is why enablement must go beyond visibility dashboards. Cost efficiency needs to be engineered into the default path. If developers are given standardized, pre-approved architectural patterns where cross-account strategy, optimal sizing, and tagging are built in from the start, the cognitive burden of cost savings disappears. You can’t just mandate cost efficiency; you have to engineer it seamlessly into the daily workflow. For the technical leaders out there: are your teams spending cycles manually optimizing and fighting infrastructure, or are you building the paved roads that prevent structural leaks from the start?