Perhaps as a freelance consultant right now I take a sharper look at the costs involved - if a client has, say, $50k to budget on a project, I really don't want $10k of that to go to hosting if it doesn't need to - I'd rather it be available for my services directly (obviously) or to give us more play for marketing, testing, whatever.
I've known a couple of small to medium sized companies where they were using AWS rather strategically as part of their services - dynamically spinning up test environments for running parallel testing, off-peak data crunching, etc - but even in those cases, there weren't gigantic savings vs other options.
What bugs me most is the false dichotomy I get when I talk about this with friends; their choice is presented as either use AWS or "hire a full-time sysadmin, buy multiple server-grade boxes and manage all this in a rented data center". I've been told Amazon is saving people "easily" $100k/year by not having to hire staff and buy expensive hardware. Hrmm... not all hardware is expensive, and instead of hiring a sysadmin, you've now got multiple developers spending time learning the AWS API, and building critical business processes around AWS, tying you to Amazon for the long haul, all while they could be focusing more on line-of-business stuff that you hired them for in the first place.
I don't doubt that in some cases there's robust cost savings, but it's never struck me as a terribly cost-efficient way of doing any web stuff. In some cases it may be the only way to deal with certain problems, but in those cases cost probably isn't a consideration anyway.