A city wants monthly showback so each municipal department sees its own AWS spend by application tag rather than a single opaque IT bill. Which approach best investigates Cost and Usage Reports at a granular level for that showback?
Select an answer to reveal the explanation.
Short Explanation
Dump CUR to S3, let Athena slice by the department tag, and put QuickSight on top—that’s municipal showback you can defend in a council meeting. A payer homepage screenshot teaches nobody which app burned the budget.
Full Explanation
Granular FinOps showback typically lands Cost and Usage Reports in S3, queries tagged line items with Athena, and presents departmental views in QuickSight (or equivalent). That pattern maps spend to municipal departments by cost-allocation tags. Untagged payer screenshots and disabling tags reduce allocation fidelity; Capacity Reservation counts alone are not a complete departmental showback model.