AWS Cost and Usage Report (CUR)
The most detailed AWS billing dataset — line-item cost and usage data delivered to an S3 bucket you own.
Verified against AWS documentation · 2026-08-28
Key facts
- 01Delivers granular line items (per service, per resource, per hour if enabled) as files into your S3 bucket — it's raw data, not a dashboard
- 02Time granularity: hourly, daily, or monthly; optionally includes resource IDs for per-resource cost attribution
- 03Refreshed at least once a day; initial delivery can take up to 24 hours after setup
- 04Integrates with Athena (query with SQL), QuickSight (visualize), and Redshift (warehouse) — Parquet format is built for the Athena path
- 05Tracks Reserved Instance and Savings Plans utilization at the line-item level — the data source for serious commitment analysis
Exam triggers
Phrases and scenarios that point here.
- "Most detailed" or "most granular" billing/cost data → CUR
- "Analyze costs with SQL / Athena" or "custom cost dashboards in QuickSight" → CUR in S3
- Cost data "delivered to S3" → CUR (Cost Explorer has no S3 delivery)
- Chargeback / showback per team, per resource, or per tag → CUR with resource IDs and cost allocation tags
Not this service
- Visual point-and-click cost exploration and forecasts → Cost Explorer
- Alerts when spend crosses a threshold → AWS Budgets
- Cost optimization recommendations → Trusted Advisor / Compute Optimizer
- Splitting bills across business units → AWS Billing Conductor
Use cases
- 01Feeding a FinOps pipeline: CUR lands in S3, Athena queries it, QuickSight dashboards it — the standard homegrown cost analytics stack
- 02Chargeback: tagging resources by team, then using CUR line items to bill each department for exactly what they consumed
- 03Auditing a surprise bill — CUR is where you find *which* resource, in *which* hour, generated the charge Cost Explorer only shows as a spike
- 04Verifying RI and Savings Plans coverage before renewing commitments, using actual utilization line items instead of estimates
How it's charged
- 01The report itself is free — no charge to enable or generate it
- 02You pay for what surrounds it: S3 storage for the report files, and Athena/QuickSight/Redshift costs if you query or visualize the data
- 03Enabling resource IDs or hourly granularity multiplies file size — meaning more S3 storage and more Athena data scanned per query