Cost and Usage Report (CUR)
Explore how to use the AWS Cost and Usage Report (CUR) to analyze detailed cost drivers within services. Understand how CUR complements Cost Explorer by providing granular data tied to specific usage dimensions, regions, and tags, enabling accurate troubleshooting and actionable cost management.
We'll cover the following...
Cost Explorer can tell you which service got expensive. It can't tell you, on its own, exactly which usage line inside that service caused it, or hand you a resource ID a team can actually act on. That gap is where the Cost and Usage Report (CUR) comes in. CUR is a detailed dataset of cost and usage line items that gets queried when there's a need to explain which resource behavior created a spend change. It is not an invoicing system, and it is not a real-time monitoring feed watched minute by minute.
The operational boundary is simple. Once an alert, a dashboard, or a human report signals that a cost spike probably happened, CUR is where the explanation gets justified with concrete dimensions like region, operation type, and tags, and then turned into an actionable change such as throttling, caching, scaling limits, or rollback. ...