A city FinOps team must give each department a monthly showback of AWS spend with service-level detail across dozens of accounts. Which approach best provides that granular organizational cost visibility?
Select an answer to reveal the explanation.
Short Explanation
Showback needs a spreadsheet of truth, not a one-page invoice. CUR dumps every line item into a central analytics lane so parks, courts, and utilities each see their own meter. Averaging by headcount hides the real spenders.
Full Explanation
The AWS Cost and Usage Report provides the most granular cost and usage data for multi-account organizations and is commonly landed in a central analytics account for Athena or similar showback. Invoice PDFs lack line-item depth for department allocation. Blocking Cost Explorer reduces visibility rather than enabling governance. Untagged shared accounts without detailed reporting prevent accurate mapping of spend to business units.