# Viewing and managing reports
To view information about your Cost and Usage Report, use the Billing and Cost Management console. To view your report’s files, you can use the Amazon S3 console.
Use the following procedures to find your report and report files.
**To view your report details and files**
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. From your list of reports, choose the name of the report that you want to view.
1. On the **Report Details** page, you can view the report’s settings.
1. To view the report’s files, note the **Report path prefix** on the **Report Details** page.
1. Choose the bucket name listed under **Amazon S3 bucket**. The link opens this bucket in the Amazon S3 console.
1. From the list of objects in the bucket, choose the folder named with the first part of the **Report path prefix** that you noted in step 5. For example, if your **Report path prefix** is **example-report-prefix/example-report-name**, then choose the folder named **example-report-prefix**.
1. From the list of objects in the folder, choose the folder named with the second part of the **Report path prefix** that you noted in step 5. For example, if your **Report path prefix** is **example-report-prefix/example-report-name**, then choose the folder named **example-report-name**. This folder contains your report files.
# Viewing the latest report version
AWS updates your Cost and Usage Report at least once a day until your charges are finalized. When you create a report, you can choose to create new report versions or overwrite the existing report version with every update.
If you configured your report to create new report versions with every update, then use the **assemblyId** in the manifest file to find the latest report files.
**To view your latest report files when you have multiple report versions**
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. From your list of reports, choose the name of the report that you want to view.
1. On the **Report Details** page, note the **Report path prefix**.
1. Choose the bucket name listed under Amazon S3 bucket. The link opens this bucket in the Amazon S3 console.
1. From the list of objects in the bucket, choose the folder named with the first part of the **Report path prefix** that you noted in step 4. For example, if your **Report path prefix** is **example-report-prefix/example-report-name**, then choose the folder named **example-report-prefix**.
1. From the list of objects in the folder, choose the folder named with the second part of the **Report path prefix** that you noted in step 4. For example, if your **Report path prefix** is **example-report-prefix/example-report-name**, then choose the folder named **example-report-name**.
1. Open the folder named with the latest billing period (in the YYYYMMDD-YYYYMMDD format).
1. Open the ****example-report-name**-Manifest.json** file.
1. At the top of the manifest file, note the **assemblyId**. The **assemblyId** value corresponds to the name of the folder with the latest report files.
1. Return to the Amazon S3 console page where you’re viewing the folder named with the latest billing period.
1. Open the folder named with the **assemblyId** value that you noted in step 10. For example, if the **assemblyId** value is **20210129T123456Z**, then open the folder named **20210129T123456Z/**. This folder contains your latest report files.
# Viewing your finalized report
After issuing your invoice at the end of the month, AWS finalizes your report’s usage charges. To determine if a line item on your report is final, review the **bill/InvoiceId** column. If the line item is final, then the **bill/InvoiceId** column is populated with an AWS invoice ID. If the line item is not yet final, then the **bill/InvoiceId** column is blank.
To determine if your entire report is finalized, review the **bill/InvoiceId** column. If the report is final, then the **bill/InvoiceId** column is populated with invoice ID values. If the report is not yet final, then the **bill/InvoiceId** column is blank.
**Note**
After your report is finalized, AWS might update the report if AWS applies refunds, credits, or support fees to your usage for the month. Because Developer, Business, and Enterprise Support are calculated based on final usage charges, those are reflected on the sixth or seventh of the month for the prior month’s report. AWS applies credits or refunds based on the terms of your agreement or contract with AWS.
# Understanding your report versions
AWS updates your Cost and Usage Report at least once a day until your charges are finalized. When you create a report, you can choose to create new report versions or overwrite the existing report version with every update.
Your report files include a .csv file or a collection of .csv files and the manifest file. Your report can also include any additional files that support your data’s integration with Amazon Athena, Amazon Redshift, or Quick.
The following sections describe the file organization and naming conventions based on the report versioning that you choose.
## Cost and Usage Reports delivery timeline
During the report period, AWS delivers a new report and a new manifest file each time AWS updates the report. AWS builds on previous reports until the end of the billing period. After the end of the report billing period, AWS generates a new report with none of the information from the previous report.
## Creating new Cost and Usage Report versions
When you choose to keep your previous Cost and Usage Reports, your AWS CUR uses the following Amazon S3 organization and naming conventions.
```
//yyyymmdd-yyyymmdd//-.csv.
```
+ `report-prefix` = The prefix that you assign to the report.
+ `report-name` = The name that you assign to the report.
+ `yyyymmdd-yyyymmdd` = The range of dates that the report covers. Reports are finalized at the end of the date range.
+ `assemblyId` = An ID that AWS creates each time that the report is updated.
+ `file-number` = If the update includes a large file, AWS might split it into multiple files. The `file-number` tracks the different files in an update.
+ `csv` = The format of the report files.
+ `zip` or `gz` = The type of compression applied to the report files.
For example, your report could be delivered as a collection of the following files.
```
//20160101-20160131/<123456789>/-<1>.csv.
//20160101-20160131/<123456789>/-<2>.csv.
//20160101-20160131/<123456789>/-<3>.csv.
//20160101-20160131/<123456789>/-Manifest.json
//20160101-20160131/-Manifest.json
```
AWS delivers all reports in a report date range to the same `report-prefix/report-name/yyyymmdd-yyyymmdd` folder. AWS gives each report a unique ID and delivers it to the `assemblyId` subfolder in the date range folder. If the report is too large for a single file, the report is split into multiple files and delivered to the same `assemblyId` folder.
For more information on manifesting files when you keep a previous report, see [Cost and Usage Reports manifest files](#manifest-cur-files)
## Overwriting previous Cost and Usage Reports
When you choose to overwrite your previous Cost and Usage Reports, your AWS CUR uses the following Amazon S3 organization and naming conventions.
```
//yyyymmdd-yyyymmdd/-.csv.
```
+ `report-prefix` = The prefix that you assign to the report.
+ `report-name` = The name that you assign to the report.
+ `yyyymmdd-yyyymmdd` = The range of dates that the report covers. AWS finalizes reports at the end of the date range.
+
+ `file-number` = If the update includes a large file, AWS might split it into multiple files. The `file-number` tracks the different files in an update.
+ `csv` = The format of the report files.
+ `zip` or `gz` = The type of compression applied to the report files.
For example, your report could be delivered as a collection of the following files.
```
//yyyymmdd-yyyymmdd/-<1>.csv.
//yyyymmdd-yyyymmdd/-<2>.csv.//yyyymmdd-yyyymmdd/-<3>.csv.
//yyyymmdd-yyyymmdd/-Manifest.json
```
### Athena specifications
If you chose Athena support when you created your AWS CUR, the file naming conventions are the same as when you choose to overwrite your AWS CUR except for the format and compression. Athena AWS CUR files use `.parquet` instead. For example, your report could be delivered as a collection of the following files.
```
//yyyymmdd-yyyymmdd/.parquet
//yyyymmdd-yyyymmdd/
//yyyymmdd-yyyymmdd/-Manifest.json
//yyyymmdd-yyyymmdd/-create-table.sql
//yyyymmdd-yyyymmdd/crawler-cfn.yml
```
### CloudFormation specifications
In addition to the AWS CUR files, AWS also delivers an CloudFormation template that you can use to set up an CloudFormation stack that enables you to query Amazon S3 data using Athena. If you don't want to use the CloudFormation template, you can use the provided SQL to create your own Athena tables. For more information, see [Querying Cost and Usage Reports using Amazon Athena](cur-query-athena.md).
## Cost and Usage Reports manifest files
When AWS updates AWS CUR, AWS also creates and delivers manifest files that you can use for Amazon Athena, Amazon Redshift, or Quick.
Manifest files use the naming conventions, and lists the following:
+ All of the detail columns that are included in the report to date
+ A list of report files if the report was split into multiple files
+ The time period covered by the report, and other information.
```
//yyyymmdd-yyyymmdd/-Manifest.json
//yyyymmdd-yyyymmdd//-Manifest.json
///year=2018/month=12/-Manifest.json
```
### Creating new Cost and Usage Report versions
When you keep the previous Cost and Usage Reports, the manifest file is delivered to both the date range folder and the `assemblyId` folder. Each time AWS creates a new AWS CUR for a date range, it overwrites the manifest file stored in the date range folder with an updated manifest file. AWS delivers the same updated manifest file to the `assemblyId` folder along with the files for that update. Manifest files in the `assemblyId` folder aren't overwritten.
### Overwriting the previous Cost and Usage Reports
When you overwrite the previous AWS CUR, the manifest file is delivered to the `month=mm` folder. The manifest file is overwritten along with the report files.
### Amazon Redshift specifications
If you chose the option for Amazon Redshift support in your AWS CUR, AWS also creates and delivers a file with the SQL commands that you need to upload your report into Amazon Redshift. You can open the SQL file with a regular text editor. The SQL file uses the following naming convention.
```
//yyyymmdd-yyyymmdd//-RedshiftCommands.sql
```
If you use the commands in the `RedshiftCommands` file, you don't need to open the `RedshiftManifest` file.
**Important**
The `manifest` file determines which report files the `copy` command in the `RedshiftCommands` file uploads. Deleting or removing the `manifest` file breaks the copy command in the `RedshiftCommands` file.
### Amazon Athena specifications
If you chose the option for Amazon Athena support in your AWS CUR, AWS also creates and delivers multiple files to help set up all of the resources that you need. AWS delivers a CloudFormation template, a SQL file with the SQL to create your Athena table manually, and a file with the SQL to check your AWS CUR refresh status. These files use the following naming conventions.
```
///yyyymmdd-yyyymmdd/crawler-cfn.yml
///yyyymmdd-yyyymmdd/-create-table.sql
///yyyymmdd-yyyymmdd/
```
# Editing your Cost and Usage Reports configuration
You can use the **Cost and Usage Reports** page in the Billing and Cost Management console to edit Cost and Usage Reports.
**Note**
Report names can't be edited. If you chose **Overwrite** for **Report versioning**, you're unable to edit the report name, whether the report includes resource IDs, time granularity, or the report versioning. If you delete a report set to **Overwrite** and create a new report with the same name, Amazon S3 bucket, and path prefix, your data could corrupt and become inaccurate.
**To edit Cost and Usage Reports**
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. Select the report that you want to edit and choose **Edit report**.
1. (Versioned reports only) For **Report additional content**, select **Include resource IDs** to include the IDs of each individual resource in the report.
**Note**
Including resource IDs creates individual line items for each of your resources. This might increase the size of your Cost and Usage Reports files significantly, based on your AWS usage.
1. Select **Split cost allocation data** to include detailed cost and usage for shared resources (Amazon ECS and Amazon EKS).
**Note**
Including split cost allocation data creates individual line items for each of your resources (that is, ECS tasks and Kubernetes pods). This might increase the size of your Cost and Usage Reports files significantly, based on your AWS usage.
1. For **Data refresh settings**, select whether you want the AWS Cost and Usage Reports to refresh if AWS applies refunds, credits, or support fees to your account after finalizing your bill. When a report refreshes, a new report is uploaded to Amazon S3.
1. Choose **Next**.
1. For **S3 bucket**, enter the name of the Amazon S3 bucket where you want the reports delivered.
1. Choose **Verify**.
**Note**
The bucket must have appropriate permissions to be valid. For more information on adding permissions to the bucket, see [ Setting Bucket and Object Access Permissions](https://docs.aws.amazon.com/AmazonS3/latest/userguide/set-permissions.html) in the *[Amazon Simple Storage Service User Guide](https://docs.aws.amazon.com/AmazonS3/latest/userguide/)*.
1. For **Report path prefix**, enter the report path prefix that you want prepended to the name of your report.
1. (Versioned reports only) For **Time granularity**, choose one of the following:
+ **Hourly**: If you want the line items in the report to be aggregated by the hour.
+ **Daily**: If you want the line items in the report to be aggregated by the day.
+ **Monthly** if you want the line items in the report to be aggregated by month.
1. (Versioned reports only) For **Report versioning**, choose whether you want each version of the report to overwrite the previous version of the report, or to be delivered in addition to the previous versions.
1. For **Report data integration**, select whether you want to enable your AWS CUR to integrate with Amazon Athena, Amazon Redshift, or Quick. The report is compressed in the following formats:
+ **Athena**: Parquet format
+ **Amazon Redshift or Quick**: .gz compression
1. Choose **Save**.
# Using Cost and Usage Reports for AWS Organizations
In AWS Organizations, both management accounts and member accounts can create Cost and Usage Reports. The IAM policies that allow or restrict the ability to create a report are the same for both types of accounts.
**Note**
The account that creates the Cost and Usage Report must also own the Amazon S3 bucket that AWS sends the reports to. You cannot configure a Cost and Usage Report to deliver to an Amazon S3 bucket owned by another account. For more information about Amazon S3 bucket setup requirements, see [Setting up an Amazon S3 bucket for Cost and Usage Reports](cur-s3.md).
## Managing Cost and Usage Reports as a member account
If you have permissions to create a Cost and Usage Report for a member account within an organization, you can create a report for only the member account’s cost and usage data. The member account receives reports for its cost and usage during the time that the account has been a member of its current organization.
For example, say a member account leaves organization A and joins organization B on the 15th of the month. Then, the member account creates a report. Because the member account created a report after joining organization B, the member account’s report for the month includes billing data for only the time that the account has been a member of organization B.
After a member account joins a new organization, the member account's cost and usage are recorded in the new organization’s reports. This is the same outcome for a management account that converts to a member account and joins a new organization.
When a member account leaves an organization or converts into a standalone account, the member account can still access the previous reports as long as they have permissions to the Amazon S3 bucket where the previous reports are stored.
## Managing Cost and Usage Reports as a management account
If you’re an administrator of an AWS Organizations management account and you don’t want member accounts to create a report, you can apply a service control policy (SCP) that prevents member accounts from creating reports. The SCP can prevent member accounts from creating new reports, but it doesn’t delete reports created previously.
**Note**
SCPs apply only to member accounts. To prevent a management account from creating a report, modify the IAM policies attached to the user roles in the management account.
For more information on consolidated billing, see [Consolidated billing for AWS Organizations](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html) in the *AWS Billing User Guide*.