I'm Co-Founder and CEO of www.vantage.sh - we recently launched "Advanced Analytics" which gives you the ability to see the accrued cost of each individual AWS resource in your AWS account(s) day by day broken down by cost category (computer, storage, transit, etc)
This gives you the ability to see costs for "hard" resources to see costs for...so imagine seeing the cost of each Lambda Function, Cloudfront Distribution, SNS Topic or SQS Queue.
The way this works is that Vantage will automatically profile for all active resources in your account using List/Describe service API calls then join that up with Cost and Usage Report (CUR) data.
Happy to answer any questions and hopefully this helps people demystify their AWS bills a bit. We also have a healthy free tier for the first $2,500 of AWS costs per month if you want to give it a shot on a personal account.
That's not the original premise of clouds, that's the original premise of renting out servers, which is much older. The original premise of clouds is “enable dynamic provisioning of resources”.
As developers are becoming more financially savvy as it relates to cloud infrastructure our goal is to simply give them the suite of analytics tools to dive deeper themselves. This feature launch supports that aim.
So my guess is that this would weed out cost consultants that are just glorified report writers, in exchange for ones that can actually give you actionable customized advice, rather than the canned type.
It's similar to a Github repo in some respects. Developers will connect their AWS account, invite their teams and temporarily add folks like cloud consultants to their Vantage team to provision some reports or do some initial investigation. We're thinking through some more collaboration features in the future to support this more.
We are a small team and have a hard time monitoring costs. The AWS billing alerts (which I setup after realizing too late that our ES cluster was costing us more than the rest of our infra) are rudimentary but need a bit more intelligence about exactly where our stuff is underutilized.
AWS has tools for _all_ these things (and can even show you underutilized or oversized resources) but they are quite half baked. I think this is intentional because they don't want to make it brain dead simple for you to cut costs.