I was at AWS when this was unfolding and cost was never an afterthought. I also felt that the best way to control costs is to make it a section in design docs. This would force the developers to consider costs when proposing design alternatives for a new service or enhancing an existing service.
In particular, there was a strong understanding that engineers would overfocus on optimizing for what was asked, and so the deliberate overfocus was on "thinking big" on products that could grow rapidly while having pricing and engineering models that may be neutral margin in the short term; only in the long term paying off as positive margin (without needing to "surprise" customers with a price change).
Did you see a similar pattern in EC2?