Skip to main content

AWS Cost and Usage Reports

AWS Cost and Usage Reports FAQs

Dive deeper into your AWS cost and usage data

General AWS Cost and Usage Report

Open all

    The AWS Cost and Usage Reports (CUR) contains the most comprehensive set of cost and usage data available. You can use Cost and Usage Reports to export your cost and usage data to an Amazon S3 bucket that you own. You can receive exports that break down your costs by the hour, day, or month, by product or product resource, or by tags that you define yourself. AWS delivers the export to your bucket at least once a day as either a CSV or Parquet file. You can process the export using analytics tools, such as Amazon Athena or Amazon Redshift, or spreadsheet applications, such as Microsoft Excel. You can also create visualizations of your CUR using business intelligence tools, such as Amazon QuickSight, to share insights with your teams.

    You can create an export of the Cost and Usage Report table to be delivered to your Amazon S3 bucket from the Data Exports page in the AWS Billing and Cost Management console or using the AWS Data Exports CLI/SDKs.

    The AWS Cost and Usage Reports provide access to the most detailed information available about your AWS costs and usage. Cost and Usage Reports contain the data you need to perform the most detailed cost optimization, reporting, and allocation activities.

Split Cost Allocation Data

Open all

    Split Cost Allocation Data enables cost visibility for shared AWS resources in AWS Cost and Usage Reports (CUR). You can use this data to allocate shared costs to the workloads and teams that use those resources.

    Split Cost Allocation Data supports container-level cost and usage data for Amazon ECS tasks, AWS Batch jobs, and Amazon EKS pods, and Amazon S3 storage and API request costs by prefix. Networking flexible cost allocation supports NAT gateway data transfer and data processing charges, data transfer between an Amazon EC2 instance and a directly connected peer in the same Region, and data transfer over a VPC peering connection in the same Region. See the Split Cost Allocation Data documentation and networking flexible cost allocation documentation for service coverage and requirements.

    Opt into Split Cost Allocation Data for the relevant service in Cost Management preferences in the AWS Billing and Cost Management console, then include Split Cost Allocation Data in your legacy CUR report or your CUR 2.0 export in AWS Data Exports. This report setting includes data for all services enabled in Cost Management preferences. Complete any required service configuration, such as exporting S3 Storage Lens prefix metrics to AWS Billing and Cost Management or applying a networking flexible cost allocation policy in Amazon VPC. For container workloads, Split Cost Allocation Data automatically scans for ECS tasks and EKS pods once activated and prepares granular cost data for the current month.

    Only regular and payer accounts have access to Cost Management preferences and can opt into Split Cost Allocation Data. Once opted in, member accounts can view the data in the AWS Cost and Usage Reports (CUR). It can take up to 24 hours for the data to be visible in the CUR.

    With Split Cost Allocation Data for Amazon ECS and AWS Batch, you can allocate the cost of your EC2 instances to your containerized workloads running on these instances. Split Cost Allocation Data for Amazon ECS generates container-level costs by analyzing each container’s Amazon EC2 instance resource consumption based on the price of the instance and the percentage of CPU and memory resources consumed by the containers running on the instance. AWS Batch customers running workloads using Amazon ECS or AWS Fargate compute environments will also see their cost and usage in the CUR.

    Split Cost Allocation Data enables cost visibility for all Amazon ECS container objects across your entire consolidated billing family (payer and linked accounts). For Amazon EKS, allocation covers the same consolidated billing family and uses pod resource requests and, where configured, utilization metrics.

    Split Cost Allocation Data for Amazon S3 uses S3 Storage Lens prefix metrics to allocate a bucket’s storage costs for supported storage classes and its Tier 1 and Tier 2 API request costs to individual prefixes. You can select up to five adjacent prefix levels in S3 Storage Lens. Each cost is assigned to the deepest matching prefix within your configured range, so you can group costs across your prefix hierarchy without double counting. Usage that does not match a configured prefix is reported as unattributed. Data transfer, data retrieval, and other S3 charges remain at the bucket level.

    Networking flexible cost allocation attributes usage and cost to the resources that generated the traffic, using the reporting granularity specified in your policy. A network administrator applies allocation policies in the Amazon VPC console to resources in one account or across accounts in your organization in AWS Organizations. For example, a NAT gateway policy with EC2 reporting granularity allocates its data processing usage and cost to each EC2 instance that sent traffic through it. Additional split line items in your CUR identify the resource that generated the usage and the shared resource it used. The original billing line items remain in your report, and the allocation does not change which account AWS bills for the original usage.