Once muda had worked through the waste in my deploy pipelines, I wanted the same thing for the AWS accounts those pipelines deploy to, built up against my own accounts first and checked on the real bill. Over a few weeks in October that cut the monthly bill roughly in half, and very little of the cut came from resizing instances — most of it came from changing code and deployments: a demo that ran around the clock when it only needed to run on request, dev schedules nobody used, stacks for projects I'd stopped working on, and programs that did more work than their job needed.

The first two muda posts covered delivery pipelines, where a deploy's minutes go and the waste behind each slow step. muda now covers AWS cost as well: it starts from the bill, traces each cost to the code and the coding agent session that own it, hands the fix to that session, and checks the result on the bill once the change is deployed.