# Viewing and managing data exports To view details about your exports, use the **Data Exports** page in the AWS Billing and Cost Management console. To view your export files, use the S3 console link for your Amazon S3 bucket on the **Data Exports** page. To view your export dashboards, use the QuickSight link on the **Data Exports** page, or go directly to the QuickSight console and find your dashboard. **To view your export details, files, and dashboards** 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, choose **Data Exports**. 1. In the **Exports and dashboards** list, find the name of the export that you want to view. 1. To view the export details, choose the link in the **Export name** column to view the summary page describing the export settings. 1. To view the export files, choose the link in the **S3 bucket** column to be brought to the S3 console for your bucket. 1. To view the QuickSight dashboard, choose the **Cost and usage dashboard** link in the **Export type** column. The following is an overview of the columns in the **Exports and Dashboards** list: + **Export name**: The name you chose when creating the export. + **Status**: The health of your export. It can have two values: + **Healthy**: This status indicates that the most recent export delivery was successful. **Note** Your Cost and Usage Dashboard could be missing the data for the current month because it can take up to 24 hours for all your data to be populated in your dashboard. If the export status says “Healthy”, allow 24 hours for your dashboard to update with the current month's data. When you use billing transfer as a bill transfer account, or AWS Billing Conductor as a management account, you can see all billing view-based exports with billing view mode disabled. When you enable billing view mode, you can see only exports associated with the selected billing view. + **Unhealthy**: This status indicates that the most recent export delivery failed. + **Export type**: The type of export created. Data Exports has three types of exports: + **Standard data export**: A customized export of a table that delivers to Amazon S3 on a recurring basis. + **Cost and usage dashboard**: An export and integration to Amazon QuickSight that deploys a pre-built cost and usage dashboard. This becomes a link to a dashboard. + **Legacy CUR export**: An export of the Legacy Cost and Usage Report (CUR). + **Data table**: The table that your export is querying. + **Date created**: The time and date when your export was created. + **Date last refreshed**: The time and date when your export was last refreshed. + **S3 bucket**: The S3 bucket to which your export is being delivered to. # Understanding export delivery In the following sections, you'll find information about your export delivery. + **Export S3 parent directory structure:** How export data is structured in the S3 directory to which your export is delivered to. + **Export refreshing:** How often your export updates in your S3 directory. + **Export overwriting and create new:** How your export delivery changes with overwriting and creates new delivery preferences. + **Export data file names and chunks:** How the export files (gzip/csv or Parquet) are named. ## Export S3 parent directory structure Each export delivers the data from the query to S3 (as one or more gzip/csv or Parquet files) and a `Manifest.json` metadata file containing information about the export definition at the time the export was executed. **Data** The data resulting from the export query is stored in the following S3 file path: `s3://///data//` The partition corresponds to the table that is being queried. For CUR 2.0, the partition corresponds to the “billing period” of a given CUR 2.0 export. `prefix`: The S3 file prefix that you assign to the export. `export-name`: The name that you assign to the export. `partition`: The partition describes how a single table is partitioned into separate tables for delivery. For CUR 2.0, the partition corresponds to the “billing period” in the format `BILLING_PERIOD=YYYY-MM`. For example, the partition for November 2023 is 2023-11. The following is an example of an S3 file path: `s3://my-data-export-s3-bucket/my-cur-files/business_group_a_cur/data/BILLING_PERIOD=2023-11` **Metadata** The `Manifest.json` metadata file for the query is stored in the following S3 file path: `s3://///metadata//-Manifest.json` The `Manifest.json` file is updated each time the export is refreshed. A new `Manifest.json` file is created for each new partition created by the export. For CUR 2.0, this means a new `Manifest.json` file is generated when a new billing period begins. Manifest files contain the following information: + All of the columns that are included in the export. + A list of the export files and their file path. We recommend identifying which files to ingest by programmatically reading this list. + The time period covered by the export. The `Manifest.json` is only delivered once all of the export data files have been delivered to S3. ## Export refreshing Data Exports refreshes your exports each time the source data is updated. For CUR 2.0, this occurs at least once a day. The current billing period (partition) is refreshed until the billing period ends, at which point deliveries of the next billing period begin. Deliveries of the next billing period only contain charges and billing data for that billing period. After the billing period ends, AWS may update the export delivery for the previous billing period within the first two weeks after it ended. ## Export overwriting and create new When you create an export, you can choose to either create new export files or overwrite the existing export files with each refresh. **Create new** Creating new export files uses more S3 storage because all export refreshes are kept. Overwriting the previous export files uses less S3 storage because only the latest version of each billing period refresh is kept. When in “create new” mode, the export files are delivered to the following S3 path: `s3://///data//-` The `timestamp` is the date and time when the export was executed. The `execution-id` is the unique ID assigned to the execution. For "create new", two `Manifest.json` files are delivered with each export execution. One is stored in the `metadata//-` directory, and the other is overwritten in the `metadata/` directory. The manifest in the `metadata/` directory always represents the most recent refresh and its data is used to identify the location of the most recently refreshed export files. **Overwrite** Overwriting only applies for refreshes of the same partition (that is, billing period). Once a new billing period begins, the export creates a new S3 directory with a name based on the latest partition or billing period, and begins delivering the new export partition there. The export of the previous partition is not overwritten unless the data for that specific partition is updated. When in “overwrite” mode, the export files are delivered to the following S3 path: `s3://///data//` The export files in this file directory are overwritten with each delivery of the same partition (that is, billing period). Export files are delivered as multiple “chunks” (separate gzip/csv or Parquet files) when the export becomes sufficiently big. If the export ever decreases in size during the month (due to a changed query or correction to data), fewer chunks may be needed to deliver the export refresh. In this case, Data Exports overwrites any extra chunks from the last refresh with empty data. For overwriting, one `Manifest.json` file is delivered with each export execution. It is stored in the `metadata/` directory and is overwritten with each refresh. ## Export data file names and chunks Exports either deliver the results of one execution as one file (gzip/csv or Parquet) or in multiple “chunks” (separate gzip/csv or Parquet files) when the export becomes sufficiently big. Exports are named as follows for the gzip/csv file format: `-.csv.gz` Exports are named as follows for the Parquet format: `-.snappy.parquet` Chunk numbers always have five digits. Chunk numbers are enumerated starting at `00001`. ## Summary **Export data file names with directory for create new** Parquet: `s3://///data//-/-.snappy.parquet` gzip/csv: `s3://///data//-/-.csv.gz` **Export data file names with directory for overwrite** Parquet: `s3://///data//-.snappy.parquet` gzip/csv: `s3://///data//-.csv.gz` **Manifest file names with directory for create new** The “create new” mode delivers `Manifest.json` to two locations. The first location is in a folder representing a specific execution of an export (named by `timestamp` and `execution-id`). This Manifest corresponds to that specific execution. The file path is as follows: `s3://///metadata//-` The second location is in a partition folder containing all executions. This Manifest is the same file from the most recent execution of the export. You can read this Manifest to identify the exact file paths of all recent export files. The file path is as follows: `s3://///metadata//Manifest.json` **Manifest file names with directory for overwrite** The “overwrite” mode delivers `Manifest.json` to one location. `s3://///metadata/` The Manifest in this directory is overwritten with each refresh of a given partition (that is, billing period). # Editing export details You can use the **Data Exports** page in the AWS Billing and Cost Management console to edit your export details. **To edit your export details** 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, choose **Data Exports**. 1. From your list of exports, choose the name of the export that you want to edit. 1. On the **Export details** page, choose **Edit**. 1. In **Edit** mode, you can update the column selection for your export and the export overwrite preference. You can't update the data table, the additional export content (table configurations), or the compression type and file format for an existing export. To change these details, you need to create a new export. # Editing export tags You can use the **Data Exports** page in the AWS Billing and Cost Management console to edit your export tags. **To edit your export tags** 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, choose **Data Exports**. 1. From your list of exports, choose the name of the export that you want to edit. 1. In the **Tags** section at the bottom of the page, choose **Manage tags**. 1. On the **Manage tags** page, do the following: + To add a new tag, choose **Add new tag**. You can add up to 50 tags to search and filter your resources or track your AWS costs. + To delete an existing tag, choose **Remove** beside the entry you want to remove. 1. Choose **Save**. # Deleting exports You can use the **Data Exports** page in the AWS Billing and Cost Management console to delete your exports. **To delete an export** 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, choose **Data Exports**. 1. From your list of exports, choose the name of the export that you want to delete. 1. On the **Export details** page, choose **Delete**. 1. Choose **Delete** once more to confirm that you want to delete the export. **Note** This procedure deletes your export from Data Exports. However, it doesn't delete the objects stored in your Amazon S3 bucket. For a Cost and Usage Dashboard, the above procedure deletes the Cost and Usage Dashboard from Data Exports. However, it doesn't delete the objects stored in your S3 bucket, QuickSight dashboard, and additional QuickSight resources. To delete your Cost and Usage Dashboard from QuickSight, see [Deleting an Amazon QuickSight dashboard](https://docs.aws.amazon.com/quicksight/latest/user/deleting-a-dashboard.html). When you delete an Amazon QuickSight dashboard, the dashboard is permanently removed from your account and all folders the dashboard was a part of. You'll no longer be able to access the deleted dashboard. You can only delete dashboards that you own or co-own. # Using Data Exports with AWS Organizations Data Exports can work with AWS Organizations so that management accounts can generate exports with data for all accounts in your organization. Member accounts can also create data exports, but these exports only contain the billing and cost management data for that specific member account. The settings that control whether the management account receives data for all member accounts varies across the Data Exports tables. Refer to the following sections for information about how it is determined whether to include member account data for each table. + [Cost and usage report 2.0 (CUR 2.0)](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2.html#cur2-table-organizations) + [Cost optimization recommendations (from Cost Optimization Hub)](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cor.html#cor-table-organizations) + [FOCUS 1.0 with AWS columns](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-focus-1-0-aws.html#focus-1-0-table-organizations) + [Cost and usage dashboard](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur-dashboard.html#cur-dashboard-table-organizations) + [Carbon emissions](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-carbon-emissions.html#carbon-emissions-table-organizations) The IAM policies that allow or restrict the ability to create an export are the same for both management and member accounts. If you are an administrator of an AWS Organizations management account and you don’t want member accounts to create an export, you can apply a service control policy (SCP) that prevents member accounts from creating exports. While the SCP prevents member accounts from creating new exports, it doesn’t delete previously created exports. **Note** SCPs apply only to member accounts. To prevent a management account from creating an export, modify the IAM policies attached to the user roles in the management account.