The single most detailed source of truth for understanding exactly what you are paying for in AWS.

The AWS Cost and Usage Report, often shortened to CUR, is a detailed data export that breaks down your AWS costs and usage down to the individual line item, showing exactly which resource, service, and usage type contributed to every part of your bill. The current recommended version, Cost and Usage Report 2.0 (CUR 2.0), is delivered through a feature called AWS Data Exports, and provides a consistent, well-structured set of columns that can be queried directly using standard SQL tools.

This level of detail exists because AWS bills can include an enormous variety of charges — different services, different regions, different pricing models, and different individual resources — all contributing to a single overall total. Without a detailed breakdown, it would be nearly impossible to answer questions like “which specific application is driving up our storage costs” or “how much are we really paying for this one particular database.”

Summary numbers tell you how much, but detailed reports tell you why.

Higher-level tools like AWS Budgets or the AWS Cost Explorer dashboard are great for getting a quick, visual sense of overall spending trends, but they often summarize data in ways that hide the finer details. When a business needs to answer very specific questions — such as identifying exactly which team’s testing environment is responsible for an unexpected cost spike — a summarized dashboard view is often not detailed enough.

The Cost and Usage Report solves this by providing the raw, detailed data that finance teams, engineers, and automated analysis tools can use to build custom dashboards, run precise queries, and attribute costs accurately across an organization, down to the level of a single resource or usage type.

From raw AWS billing events to a queryable, structured dataset you can analyze directly.

flowchart TD
    A[AWS records billing events across all your usage] --> B[You configure a Cost and Usage Report export]
    B --> C[AWS compiles detailed line items into the CUR 2.0 schema]
    C --> D[Report data is delivered to your chosen Amazon S3 bucket]
    D --> E[Optional integration connects the data to Athena or Redshift]
    E --> F[You query the data using standard SQL]
        

The Configuration Step

You start by setting up a Cost and Usage Report export through AWS Data Exports, choosing settings such as time granularity (hourly, daily, or monthly), whether to include individual resource-level detail, and which output format you prefer.

The Compilation Step

AWS then compiles all relevant billing line items into the report’s fixed schema, ensuring the columns remain consistent from one report to the next, which is especially helpful for building reliable, long-term analysis tools on top of the data.

The Delivery Step

The finished report is automatically delivered to an Amazon S3 bucket you specify, on a regular, ongoing basis, without requiring you to manually request or download it each time.

The Analysis Step

Once delivered, the report can be queried directly using standard SQL through integrations with services like Amazon Athena or Amazon Redshift, or loaded into other analysis and visualization tools of your choice.

AWS has evolved the report format over time, and the newer version is now the recommended approach.

A typical path from a fresh AWS account to a fully automated, queryable cost dataset.

A closer look at the kinds of information each line item actually contains.

Unmatched detail comes with a learning curve and a need for proper tooling.

Designed to handle the billing detail of accounts ranging from small to massive in scale.

Because the report is delivered automatically and stored in Amazon S3, it naturally scales to handle the billing detail of accounts ranging from a small personal project to a massive enterprise with thousands of resources across many services. Choosing coarser time granularity, such as daily or monthly instead of hourly, can help manage the size of the dataset for organizations that do not need the finest possible detail, while still preserving accurate, itemized cost information.

The Cost and Usage Report quietly powers many of the cost dashboards and finance processes businesses rely on.

A few thoughtful choices make the difference between a useful report and an overwhelming pile of data.

How experienced finance and engineering teams structure their use of the Cost and Usage Report.

AWS recommends CUR 2.0 for new setups, since it offers a consistent, fixed schema and built-in integration with tools like Athena and Redshift.

The report is automatically delivered to an Amazon S3 bucket that you specify when setting up the export.

Basic SQL knowledge is very helpful for querying the data directly, though some tools and dashboards can present the data visually without requiring you to write queries yourself.

Yes. When resource-level detail is enabled, the report can include a specific resource identifier alongside each relevant line item.

Reports are refreshed regularly and automatically, and when integrated with Athena or Redshift, those connected tables reflect the updates without requiring additional manual steps.

While large organizations benefit significantly from its detail at scale, even smaller teams and individual developers can use it to better understand exactly where their AWS spending is going.

The AWS Cost and Usage Report exists to answer the question that summary dashboards often cannot: exactly what, specifically, is driving every part of your AWS bill. By providing detailed, line-item-level data, and evolving into the more consistent, integration-friendly CUR 2.0 format delivered through AWS Data Exports, this report gives finance teams, engineers, and analysis tools the precise information needed to attribute, understand, and ultimately optimize cloud spending. Paired with good tagging practices and the right analysis tools, it turns a vague monthly total into a clear, itemized story of where every dollar actually went.