.png)
How It Works
AWS generates the CUR on an hourly, daily, or monthly basis and writes it as a CSV or Parquet file to an Amazon S3 bucket you specify. Each row in the report represents a single line item: a specific resource, in a specific region, during a specific time window, with its on-demand rate, any negotiated rate, and any discount applied through a Savings Plan or Reserved Instance. The report can include hundreds of columns covering resource tags, usage type, billing entity, and cost allocation metadata. Finance and engineering teams typically load CUR data into a query engine such as Amazon Athena, a data warehouse, or a third-party cost visibility tool to analyze spend by team, service, or environment.
Why It Matters for Cloud Cost
Without CUR data, cloud cost management operates on summaries. The AWS Cost Explorer console shows aggregated views, but it does not expose the full granularity needed to allocate costs accurately, identify waste at the resource level, or reconcile billing with internal budgets. CUR is the foundation for showback and chargeback programs, commitment utilization analysis, and any savings model that requires verifying whether Reserved Instances or Savings Plans are actually covering the right usage. Teams that skip CUR-based analysis often discover cost anomalies weeks after they occur, because summary dashboards smooth out the spikes that line-item data would catch immediately.
Usage AI: Usage AI’s ClearCost visibility layer ingests billing-layer data to surface showback reporting and savings attribution, giving finance teams the cost allocation clarity that CUR data enables without requiring them to build and maintain a custom data pipeline.