Earlier quoted context omitted.
I agree AWS should tag all resources with their names already for them to show up in the Cost Explorer. However, we already tag by cost center or teams to identify costs. It's required as a policy and baked in most of our automations. It's also a best practice recommended by even most basic tutorials. If you have a TAM, they would tell you to do this as well when your finance team or person is asking about why these…
Got it - so what I'm inferring is that for your use-cases you don't need to see per-resource cost granularity out of the box which is completely fair. We've heard from customers that some top issues they have with cost explorer include (1) lack of visibility into K8S workloads (2) more complex filtering around creating cost reports and (3) more effective tools for chargebacks/showbacks. All of these are on our roadma…
Chargebacks in AWS is very complex, i.e in cost explorer net amortized cost vs unblended cost is hard to understand for an average user. It'd be nice if you can have some clarifications on it, what does even amortized mean etc.
We use Cost Explorer API to identify anomalies. Even basic statistics works sometimes. But there is also new native feature that is good enough for us, so we removed that. But it was a very sensitive topic, i.e our S3 usage is steadily increasing %.x per month. Trend & seasonality analysis is a must.
Sorry for my quick and dirty English. This is a hot topic for me and I get excited.