Learn more
What is AWS Cost Usage Report (CUR)?

What is AWS Cost Usage Report (CUR)?

What is AWS Cost Usage Report (CUR)?

AWS Cost and Usage Report (CUR) is a single solution that enables users to access information on their cloud costs and resource usage. With AWS CUR, users can publish their billing reports to an Amazon S3 bucket. The CUR report breaks down cost by product or product resource and by the hour, day, or month. The report in the bucket is updated once daily in a CSV format or Parquet format, according to your settings.

If know already know AWS CUR and just want to learn how to use it - click here

From AWS CUR blog

Users can enable AWS CUR on the CUR page in the Billing Console. Best practice is to turn on versioning for the S3 bucket to avoid data loss. Users can view the report on Microsoft Excel, Apache OpenOffice, or any other spreadsheet software.

The CUR CSV file includes the following columns.

  • Identity: This is a unique identifier that recognizes every line item in a single given version of the AWS CUR. An ID isn't consistent between different CURs, and therefore, users cannot use it to identify the same line item across different reports.
  • Billing details: These are static fields that appear in all CURs. Users use the billing line items in the report to find additional details about the specific bill that is highlighted in the report. Examples of additional details include the beginning and end of the billing period and the charge type.
  • LineItem details: This is also a static field. Here users can find all the cost and usage information for their usage.
  • Reservation: This column provides specifics about reserved resources.
  • Pricing: This column contains the prices for a line item. It is based on the AWS Price List Service API. The Price List Service API doesn't include Spot Instances, Free Tier pricing, products in AWS Marketplace, monthly recurring fees (RIFee), and upfront annual subscription fees (Fee).
  • Product: This column provides metadata about the product that incurred the expense. This column is dynamic, and its visibility is dependent on the usage of the product during the billing period.

From AWS CUR BlogBenefits of setting up Cost Usage Reports

Users can experience the following benefits from using AWS Cost and Usage Reports:

  1. Delivery of report files to Amazon S3 bucket.
  2. Ability to update the report up to a maximum of three times daily.
  3. Ability to create, retrieve, and delete reports using AWS Cost and Usage Reports API reference.

A CUR can be set up by a standalone account if you use the consolidated billing. It is important to be aware that the designated Amazon S3 bucket that receives billing reports must be owned by the payer account in the organization. Users will not be able to receive billing reports in a bucket owned by a member account. Organizations using consolidated billing can also have the course broken down by member account.

AWS CUR generates a detailed spreadsheet that can help organizations to analyze better and understand their costs. This data is compatible with Athena, which allows users to turn the report into a queryable database, or they can use QuickSight to visualize the billing data as graphs. 

Are you interested in generating detailed cloud cost reports and forecasts? Click here to book a time with our team!

Learn More

7 Ways to Improve Your Cloud ROI

AWS Recommendations for EC2 Cost Reduction

How FinOps can help cyber security vendors rein in cloud costs

Cloud Economics: Cost of Cloud Services Explained

What is FinOps

How to Choose a Payment Option for EC2 Reserved Instances (RIs)

How FinOps takes cloud cost management to the next level

4 Cloud Cost Management Questions that FinOps Answers

Finout's guide to understanding multiple cloud bills complexity

How to Use AWS Cost and Usage (CUR) Report

How Unit Economics help SaaS companies optimize their cloud spend

How FinOps helps make sense of cloud spending complexity

Discovering Finout's brand identity

5 Best Practices for Cloud Cost Management on Google Kubernetes Engine

The complete guide for Google Cloud pricing

DynamoDB Pricing: How to Optimize Usage and Reduce Costs

Introduction to Cost Management in Google Cloud

How to Manage Cloud Costs on GCP and GKE

AWS tagging: Why tagging is not enough

AWS tagging: Top 5 Cost Management Challenges

AWS tagging: Why you need it and how to do it

How FinOps Has Changed the Way Businesses Approach Cloud Computing

How Kubernetes Works and Why It’s So Complicated

Why Use Data warehouses in general and Snowflake specifically

We are announcing our $18.5M funding!

A Guide for APM Data Warehouses Tools

How to manage Snowflake costs

Managing DynamoDB Costs with Capacity Modes

Finout's Complete Guide to Kubernetes Cost Spot-Readiness

Finout's Complete Guide to Kubernetes Autoscaling

Join the FinOps Revolution

"Whether you’re a part of a team with an established FinOps practice, or are building up the discipline, everyone can relate to the challenges of mapping cloud utilization cost to their drivers one-to-one." – FinOps Foundation