# Understanding legacy billing reports
This section describes legacy billing reports offered outside of AWS Data Exports and AWS Cost and Usage Reports. These pages are available for reference. But, we recommend you use AWS Data Exports because these reporting methods will be unavailable at a later date.
**Topics**
+ [Using Detailed Billing Reports](detailed-billing.md)
+ [Migrating from Detailed Billing Reports to Cost and Usage Reports](detailed-billing-migrate.md)
+ [Understanding unused reservation costs](unused-reservation-costs.md)
+ [Downloading a monthly report](monthly-report.md)
+ [Downloading a monthly cost allocation report](monthly-cost-allocation.md)
+ [Downloading an AWS Usage Report](usage-report.md)
# Using Detailed Billing Reports
**Important**
The Detailed Billing Reports feature is unavailable for new customers as of July 8, 2019.
Detailed Billing Reports (DBR) contain similar information to AWS Cost and Usage Reports (AWS CUR) regarding your charges, but calculates the individual line items differently. If you've signed up for both the DBR and AWS CUR, the line items don't match. However, when the reports are finalized at the end of the month, the total cost will align.
AWS stores DBR in Amazon S3 as CSV files using the following naming convention:
```
AWS account number-aws-billing-detailed-line-items-yyyy-mm.csv.zip
```
AWS recreates Detailed Billing Reports (DBR) multiple times a day, overwriting the reports. When AWS overwrites reports, line items might be in a different order than they were in previous reports. A final report is created at the end of the month. For the next month, AWS creates a new report file instead of overwriting the final report from the previous month. Reports for previous months remain in your S3 bucket until you delete them.
For information on how to migrate your DBR to AWS CUR, see [Migrating from Detailed Billing Reports to Cost and Usage Reports](detailed-billing-migrate.md).
# Migrating from Detailed Billing Reports to Cost and Usage Reports
Detailed Billing Reports (DBR) and AWS Cost and Usage Reports (AWS CUR) both provide information about your charges. However, if you're using DBR, we recommend you transfer your report to Cost and Usage Reports.
**Topics**
+ [Comparing benefits of the Cost and Usage Reports (AWS CUR)](#migrate-benefit-cur)
+ [Key differences between Detailed Billing Reports and Cost and Usage Reports](#migrate-key)
+ [Reporting on advanced charge types](#reporting-advanced-chargetype)
## Comparing benefits of the Cost and Usage Reports (AWS CUR)
AWS CUR provides the most comprehensive source of information. You can use AWS CUR to understand individual costs in depth, and to analyze them in greater detail. This is especially useful at an enterprise scale. AWS CUR is helpful if you have complex cost management needs and require dedicated query or analytic-based systems. AWS CUR also provides detailed information about Reserved Instances (RI), including amortized costs.
### Comprehensive reservation information
Reserved Instances (RI), or reservations, offer a discounted hourly rate compared to On-Demand usage in exchange for committing to a one- or three-year term of service. This can result in significant savings. You can use AWS CUR to monitor and manage your reservation portfolio. AWS CUR provides you with detailed information, such as reservation Amazon Resource Numbers (ARNs), numbers of reservations, and total RIs. You can track your reservation-related discounts to specific resources to build a better understanding of your savings.
Detail Billing Reports (DBR) provide a subset of this metadata, but work is required to transform the required columns.
AWS CUR provides additional columns that are not available in DBR, such as information regarding your amortized reservation costs. For more information, see [Understanding your amortized reservation data](amortized-reservation.md).
### On-Demand pricing availability
AWS CUR provides information regarding the On-Demand rates for each individual line item of usage. You can use this information to quantify your savings by subtracting the amount you paid from the On-Demand rate. This also gives you the flexibility of choosing to allocate your costs using public On-Demand rates.
DBR doesn’t contain information for On-Demand rates, but only the billed amount. This makes it difficult to calculate your overall savings or to allocate costs using On-Demand rates.
### Granular breakdown of discounts
AWS CUR can access a granular view of the usage-based discounts. If discounts were applied, you can use AWS CUR to view the following:
+ Cost before being discounted
+ Discounted amount
+ Total cost after the discount was applied at the line item level
DBR does not contain a granular breakdown of your discounts.
### Automated data ingestion at scale
When you use AWS CUR, you can easily configure an event to trigger an automated data ingestion process, streamlining the process of refreshing the billing data in your in-house systems. AWS CUR data can automatically be refreshed when charges related to previous months are detected.
Additionally, AWS CUR is generated as multiple files, providing the added benefit of segmenting the data into smaller pieces. This way, you can ingest the data according to the processes used by multiple workers. Moreover, you can retry data downloads in smaller pieces.
AWS CUR is formatted in a way that enables you to locate and extract data quickly. This report is modeled from a manifest file that contains information for the overall structure of the data. This includes a list of every column that's contained in the report. Using this information, you can extend the report and include new information regarding your usage when it becomes available.
### Cross-product integration
AWS CUR is integrated with Amazon Redshift, Quick, and Amazon Athena. You can use AWS CUR to build an AWS-based cost management solution. AWS CUR also provides data in Parquet format. This provides you with more options for building out your own cost and usage reporting system. For more information, see [AWS Cost and Usage Reports Manifest Files](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-reports-costusage-files.html#manifests) in the *AWS Billing User Guide*.
## Key differences between Detailed Billing Reports and Cost and Usage Reports
There are a few differences between DBR and AWS CUR to consider after you migrate to AWS CUR. For example, you might need to adjust how you ingest the data into your systems.
### File structure
Detailed Billing Reports (DBR) are delivered as a single file. In contrast, AWS CUR are a consolidated set of files. In AWS CUR, you can view the following files in your Amazon S3 bucket:
+ A set of data files that contain all of your usage line items
+ A separate data file that contains all of your discounts (if applicable)
+ A manifest file that lists all of the data files that belong to a single report
### Column structure
DBR have a fixed list of columns, limiting its flexibility. AWS CUR don't have a fixed column structure, and instead allow you to freely add or remove columns as needed. When you begin using a new AWS service, AWS CUR can dynamically start to include new data in the report that might be useful in your case. The manifest file provides a map of all columns present in the report.
**Equivalent Column Names for DBR and AWS CUR**
| DBR column name | AWS CUR column name |
| --- | --- |
| InvoiceId | bill/InvoiceId |
| PayerAccountId | bill/PayerAccountId |
| LinkedAccountId | lineItem/UsageAccountId |
| ProductName | product/ProductName |
| SubscriptionId | reservation/subscriptionid |
| UsageType | lineItem/UsageType |
| Operation | lineItem/Operation |
| AvailabilityZone | lineItem/AvailabilityZone |
| ReservedInstance | Not Supported |
| ItemDescription | lineItem/LineItemDescription |
| UsageStartDate | lineItem/UsageStartDate |
| UsageEndDate | lineItem/UsageEndDate |
| UsageQuantity | lineItem/UsageAmount |
| BlendedRate | lineItem/BlendedRate |
| BlendedCost | lineItem/BlendedCost |
| UnBlendedRate | lineItem/UnblendedRate |
| UnBlendedCost | lineItem/UnblendedCost |
| ResourceId | lineItem/ResourceId |
| RecordType | Not Supported |
| PricingplanId | Not Supported |
| RateID | pricing/RateId |
**Note**
There's no equivalent for RecordId in AWS CUR. But, you can gather this information by combining identity/LineItemId, identity/TimeInterval, and bill/BillType.
**Retrieving DBR RecordType values through AWS CUR**
| RecordType values in DBR | Syntax to retrieve RecordType through AWS CUR | Use case |
| --- | --- | --- |
| LineItem | SELECT SUM(line\$1item\$1unblended\$1cost) FROM [CUR] WHERE line\$1item\$1line\$1item\$1type = 'Usage' | Usage line item partitions out usage costs from one-time charges (for example, upfront RI payment). |
| InvoiceTotal | SELECT (bill\$1invoice\$1id), sum(line\$1item\$1unblended\$1cost) FROM [CUR] GROUP BY bill\$1invoice\$1id | You can use invoice total to reconcile your costs between Invoices and Cost and Usage Reports. |
| AccountTotal | SELECT line\$1item\$1usage\$1account\$1id, sum(line\$1item\$1unblended\$1cost) FROM [CUR] GROUP BY line\$1item\$1usage\$1account\$1id | You can use account total to isolate costs related to your member accounts for charge back purposes. |
| StatementTotal | SELECT SUM(line\$1item\$1unblended\$1cost) FROM [CUR] | You can use statement total to understand your costs for the billing period. |
| Discount | SELECT SUM(line\$1item\$1unblended\$1cost) FROM [CUR] WHERE line\$1item\$1line\$1item\$1type = 'Discount' | You can use discount line items to identify all of your discount-related line items. |
| Rounding | Not yet supported | Not yet supported |
## Reporting on advanced charge types
### Refunds
AWS CUR: Refunds are identified by filtering for the `lineItem/LineItemDescription = ‘Refund’` string.
DBR: Refunds are identified by checking the ItemDescription column for the `‘Refund’` substring.
### Credits
AWS CUR: Credits are identified by filtering for the `lineItem/LineItemDescription = ‘Credit’` string.
DBR: Credits are identified by checking the ItemDescription column for the `‘Credit’` substring.
### Taxes
AWS CUR: Taxes are identified by filtering for the `lineItem/LineItemDescription = ‘Tax’` string.
DBR: Taxes are identified by checking the ItemDescription column for the `‘Tax’` substring.
### Identifying reservation-related upfront costs
AWS CUR: Reservation-related upfront costs are identified by filtering for the `"lineItem/LineItemType" = 'Fee'` string.
DBR: Reservation-related upfront costs are identified by checking the UsageType column for the `'HeavyUsage'` substring, and whether the `'SubscriptionId'` is null.
### Identifying reservation-related monthly fees
AWS CUR: Reservation-related monthly fees are identified by filtering for the `"lineItem/LineItemType" = 'RIfee'` string.
DBR: Reservation-related monthly fees are identified by checking the UsageType column for the `'HeavyUsage'` substring.
### Identifying instances that received reserved instance benefits
AWS CUR: Reservation-related upfront fees are identified by filtering for the `"lineItem/LineItemType" = 'DiscountedUsage'` string.
DBR: Reservation-related upfront fees are identified by checking the ReservedInstance column for the `'Y'` substring.
# Understanding unused reservation costs
You can use AWS Cost and Usage Reports (AWS CUR) to understand unused RI costs. The following four scenarios show how.
**Note**
In the following tables, the columns and rows from AWS CUR and DBR/DBR-RT are transposed for clarity. The values in the first column represent the headers of a report.
## Scenario 1: RI usage is 100%
RI Fee line item has \$10 unused cost and 0 usage hours.
Using the DBR/DBR-RT, you can understand your unused RI usage and costs by referring to the fields UsageQuantity and UnblendedCosts for RI Fee line items. RI Fee line items can be identified by the existence of ‘purchased hours’ information in the ItemDescription field. Table 1 illustrates the columns and information used to manage unused RI costs in the DBR and DBR-RT report.
**Table 1 – Unused RI costs for a 100% RI usage in DBR and DBR-RT before June 17, 2019**
| | | |
| --- |--- |--- |
| ProductName | Amazon Elastic Compute Cloud | Amazon Elastic Compute Cloud |
| UsageType | HeavyUsage:c3.8xlarge | HeavyUsage:c3.8xlarge |
| Operation | RunInstances | RunInstances |
| Availability Zone | us-east-1a | us-east-1a |
| Reserved Instance | Y | Y |
| ItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge (744 hours purchased, 744 hours used) | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| Usage Quantity | 0 | 744 |
| Unblended Rate | 0.1 | 0.1 |
| Unblended Cost | 0 | 74.4 |
Using AWS CUR, you can understand your unused RI usage and costs by referring to the fields ‘reservation/ UnusedQuantity’ and ‘reservation/ UnusedRecurringFee’ for RI Fee line items. Table 4 below illustrates the current columns and information utilized to manage unused RI costs in AWS CUR.
**Table 2 – Unused RI costs for a 100% RI usage in AWS CUR**
| | | |
| --- |--- |--- |
| lineitem/Productcode | Amazon EC2 | Amazon EC2 |
| UsageType | HeavyUsage:c3.8xlarge | USW2-BoxUsage:c3.8xlarge |
| lineitem/LineItemType | RI Fee | DiscountedUsage |
| lineitem/LineItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge | USD 0.00 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| lineitem/UsageAmount | 744 | 744 |
| lineitem/NormalizedUsageAmount | 47,616 | 47,616 |
| lineitem/UnblendedRate | 0.1 | 0 |
| lineitem/UnblendedCost | 74.4 | 0 |
| reservation/UnusedQuantity | 0 | |
| reservation/UnusedRecurringFee | 0 | |
| reservation/UnusedAmortizedUpfrontFeeForBillingPeriod | 0 | |
| reservation/RecurringFeeForUsage | | 74.4 |
| reservation/AmortizedUpfrontCostForUsage | | 5 |
| reservation/EffectiveCost | | 79.4 |
In addition to matching the current functionality supported by DBR/DBR-RT, AWS CUR has the following advantages:
+ Using AWS CUR, you are able to access information regarding the EffectiveCost for the DiscountedUsage line item, which includes both the recurring and upfront fees. The DBR only accounts for recurring fees.
+ In AWS CUR, the UsageType field is not transformed for the DiscountedUsage line items whereas DBR replaces the information with RI Fee line item information. This is because the user can group line items in AWS CUR by ReservationARN in order to understand what usage was discounted by which RI.
+ In AWS CUR, the LineItemDescription field is not transformed for the RI Fee line item. DBR appends the hours purchased and hours used.
## Scenario 2: Partial RI usage
RI Fee line item has unused cost and usage.
Using the DBR/DBR-RT, you can understand your unused RI usage and costs by referring to fields UsageQuantity and UnblendedCosts for RI Fee line items. Table 3 illustrates the columns and information used to manage unused RI costs in the DBR and DBR-RT report.
**Table 3 – Unused RI costs for a partial RI usage in DBR and DBR-RT before June 17, 2019**
| | | |
| --- |--- |--- |
| ProductName | Amazon Elastic Compute Cloud | Amazon Elastic Compute Cloud |
| UsageType | HeavyUsage:c3.8xlarge | HeavyUsage:c3.8xlarge |
| Operation | RunInstances | RunInstances |
| Availability Zone | us-east-1a | us-east-1a |
| Reserved Instance | Y | Y |
| ItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge (744 hours purchased, 644 hours used) | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| Usage Quantity | 100 | 644 |
| Unblended Rate | 0.1 | 0.1 |
| Unblended Cost | 10 | 64.4 |
Using AWS CUR, you can understand your unused RI usage and costs by referring to fields ‘reservation/ UnusedQuantity’ and ‘reservation/ UnusedRecurringFee’ for RI Fee line items. Table 4 illustrates the current columns and information utilized to manage unused RI costs in AWS CUR.
**Table 4 – Unused RI costs for a partial RI usage in AWS CUR**
| | | |
| --- |--- |--- |
| lineitem/Productcode | Amazon EC2 | Amazon EC2 |
| UsageType | HeavyUsage:c3.8xlarge | USW2-BoxUsage:c3.8xlarge |
| lineitem/LineItemType | RI Fee | DiscountedUsage |
| lineitem/LineItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge | USD 0.00 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| lineitem/UsageAmount | 744 | 644 |
| lineitem/NormalizedUsageAmount | 47,616 | 47,216 |
| lineitem/UnblendedRate | 0.1 | 0 |
| lineitem/UnblendedCost | 74.4 | 0 |
| reservation/UnusedQuantity | 100 | |
| reservation/UnusedRecurringFee | 0 | |
| reservation/UnusedAmortizedUpfrontFeeForBillingPeriod | 10 | |
| reservation/RecurringFeeForUsage | | 64.4 |
| reservation/AmortizedUpfrontCostForUsage | | 5 |
| reservation/EffectiveCost | | 69.4 |
In addition to matching the current functionality supported by DBR/DBR-RT, AWS CUR has the following advantages:
+ AWS CUR has a separate column representing UnusedQuantity for the RI Fee line item vs. DBR / DBR-RT which overloads the UsageQuantity column with the unused hours
## Scenario 3: Capacity reservation
DBR/DBR-RT filters out Capacity Reservations related UnusedBox and UnusedDed usage type line items when covered by an RI because the RI Fee line item already covers the unused amount in the UsageQuantity and UnblendedCost fields. Table 5 illustrates the columns and information utilized to manage unused RI costs in the DBR and DBR-RT report.
**Table 5 – Unused RI costs for Capacity Reservation scenario in DBR and DBR-RT prior to June 17 2019**
| | | |
| --- |--- |--- |
| ProductName | Amazon Elastic Compute Cloud | Amazon Elastic Compute Cloud |
| UsageType | HeavyUsage:c3.8xlarge | HeavyUsage:c3.8xlarge |
| Operation | RunInstances | RunInstances |
| Availability Zone | us-east-1a | us-east-1a |
| Reserved Instance | Y | Y |
| ItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge (744 hours purchased, 734 hours used) | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| Usage Quantity | 10 | 734 |
| Unblended Rate | 0.1 | 0.1 |
| Unblended Cost | 1 | 73.4 |
AWS CUR shows these line items as DiscountedUsage. Table 6 illustrates the current columns and information utilized to manage unused RI costs in AWS CUR.
**Table 6 – Unused RI costs for the Capacity Reservation scenario in AWS CUR**
| | | | |
| --- |--- |--- |--- |
| lineitem/Productcode | Amazon EC2 | Amazon EC2 | Amazon EC2 |
| UsageType | HeavyUsage: c3.8xlarge | USW2-Reservation: c3.8xlarge | USW2-BoxUsage: c3.8xlarge |
| lineitem/LineItemType | RI Fee | Usage | DiscountedUsage |
| lineitem/LineItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge | USD 0.00 per Reservation Linux/UNIX (Amazon VPC), c3:8xlarge Instance Hour | USD 0.00 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge |
| lineitem/UsageAmount | 744 | 744 | 744 |
| lineitem/NormalizedUsageAmount | 47,616 | | 47,216 |
| lineitem/UnblendedRate | 0.1 | 0 | 0 |
| lineitem/UnblendedCost | 74.4 | 0 | 0 |
| reservation/RecurringFeeForUsage | | | 64.4 |
| reservation/AmortizedUpfrontCostForUsage | | | 5 |
| reservation/EffectiveCost | | | 69.4 |
## Scenario 4: Size flexible reservations
Utilizing the DBR/DBR-RT, you can understand your unused RI usage and costs by referring to fields UsageQuantity and UnblendedCosts for RI Fee line items. RI Fee line items can be identified by the existence of ‘purchased hours’ information in the ItemDescription field. Table 9 illustrates the columns and information utilized to manage unused RI costs in the DBR and DBR-RT report.
**Table 7 – Unused RI costs for a size flex RI scenario in DBR and DBR-RT before June 17, 2019**
| | | |
| --- |--- |--- |
| ProductName | Amazon Elastic Compute Cloud | Amazon Elastic Compute Cloud |
| UsageType | HeavyUsage:c3.8xlarge | HeavyUsage:c3.8xlarge |
| Operation | RunInstances | RunInstances |
| Availability Zone | us-east-1a | us-east-1a |
| Reserved Instance | Y | Y |
| ItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge (744 hours purchased, 644 hours used) | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge; UsageType: BoxUsage:c3.large |
| Usage Quantity | 100 | 644 |
| Unblended Rate | 0.1 | 0.1 |
| Unblended Cost | 10 | 64.4 |
Using AWS CUR, you can understand your unused RI usage and costs by referring to fields ‘reservation/ UnusedQuantity’ and ‘reservation/ UnusedRecurringFee’ for RI Fee line items. Table 8 illustrates the current columns and information utilized to manage unused RI costs in the AWS CUR.
**Table 8 – Unused RI costs for a size flex RI scenario in AWS CUR**
| | | |
| --- |--- |--- |
| lineitem/Productcode | Amazon EC2 | Amazon EC2 |
| UsageType | HeavyUsage:c3.8xlarge | USW2-BoxUsage:c3.8xlarge |
| lineitem/LineItemType | RI Fee | DiscountedUsage |
| lineitem/LineItemDescription | USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge | USD 0.00 hourly fee per Linux/UNIX (Amazon VPC), c3:8large |
| lineitem/UsageAmount | 744 | 644 |
| lineitem/NormalizedUsageAmount | 47,616 | 2,576 |
| lineitem/UnblendedRate | 0.1 | 0 |
| lineitem/UnblendedCost | 74.4 | 0 |
| reservation/UnusedQuantity | 100 | |
| reservation/UnusedRecurringFee | 70.37 | |
| reservation/UnusedAmortizedUpfrontFeeForBillingPeriod | 5.5 | |
| reservation/RecurringFeeForUsage | | 4.03 |
| reservation/AmortizedUpfrontCostForUsage | | 0.5 |
| reservation/EffectiveCost | | 4.53 |
In addition to matching the current functionality supported by DBR/DBR-RT, AWS CUR has the following advantages:
+ AWS CUR has the NormalizedUsageAmount and quantity. The DBR / DBR-RT do not have columns representing this.
+ AWS CUR UsageType and Operation are not transformed for the DiscountedUsage lineitem. The DBR / DBR-RT replaces these values with the RI Fee line item.
+ AWS CUR LineItemDescription is not transformed for the DiscountedUsage line item. In DBR / DBR-RT, which replaces with the RI Fee line item description and appends the DiscountedUsage line item Usage Type to the end of the string i.e. “USD 0.10 hourly fee per Linux/UNIX (Amazon VPC), c3:8xlarge; UsageType: BoxUsage:c3.large”
# Downloading a monthly report
You can download a monthly report of your estimated AWS charges from the **Bills** page of the Billing and Cost Management console.
Suppose that you use the consolidated billing feature in AWS Organizations. Then, this report is available only for a management account and includes activity for all the member accounts. Member account owners can obtain the monthly report only from the management account. For more information, see [Consolidated Billing for Organizations](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html) in the *AWS Billing User Guide*.
The report contains line items for each unique combination of AWS product, usage type, and operation that the account uses. The estimated report is updated several times per day. You can get reports for previous months by selecting the statement period. Start with the report for the month when you signed up for monthly reports. Reports from before you signed up are not available.
# Downloading a monthly cost allocation report
**Important**
The monthly cost allocation report feature will be unavailable at a later date. We recommend that you use the AWS Cost and Usage Reports instead.
You can create custom cost allocation tag sets for your AWS resources that can describe the business dimensions of your AWS usage. You can use these tag sets to organize and track your AWS costs. Many AWS services expose tagging in their feature sets. You create the tags within those services by using the console, API, or the AWS command line interface (CLI). For more information, see [Using Cost Allocation Tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html) in the *AWS Billing User Guide*.
After you create your tags, you can obtain a monthly cost allocation report. This is essentially a monthly report that includes your cost allocation tag sets.
# Downloading an AWS Usage Report
**Important**
On September 15, 2023, the AWS Usage Report will no longer provide access to usage data older than March 1, 2019. To access such usage data, download historical usage and save it locally before September 15, 2023. The AWS Usage Report feature will be unavailable at a later date. We recommend that you use AWS Cost and Usage Reports instead.
You can download a usage report in XML or CSV format. Your report covers a single service, based on usage type, operation, and time period. You can also choose how the data is aggregated.
**To download a usage report**
1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/costmanagement/](https://console.aws.amazon.com/costmanagement/).
1. In the navigation pane, under **Legacy Pages**, choose **Cost and Usage Reports**.
1. Under the **AWS Usage Report** section, choose **Create a Usage Report**.
1. On the **Download usage report** page, under **Services**, choose the service that you want to view usage for.
1. Choose the **Usage type**.
1. Choose the **Operation**.
1. Choose the **Time period** for the report. If you choose **Custom date range**, you need to specify the **Date range** for the report manually.
1. Under **Report granularity**, choose **Hourly**, **Daily**, or **Monthly**.
1. Choose **Download**, and then choose **XML Report** or **CSV Report**.
**Note**
If you download a large report, the content of the report might be truncated. Check the last row of the downloaded file for warnings or error messages. If the report is truncated, download smaller reports by choosing a shorter time period. Another option is to decrease the report granularity from hourly to daily or monthly.