> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/system/data-sources/amazon-web-services/create-cost-and-usage-reports.md).

# Create Cost and Usage Reports

You can create a new Cost and Usage Report (CUR) from the AWS console. For details, see [Creating reports](https://docs.aws.amazon.com/cur/latest/userguide/cur-create.html) in the AWS Data Exports User Guide.

When creating the report, use the following settings:

1. Under **Export details**, choose **Standard data export**.
2. For **Export name**, enter *billing-{your AWS account number}*. Replace *{your AWS account number}* with a valid AWS account ID.
3. Under **Data table content settings**, select **CUR 2.0**.
4. For **Additional export content**, select **Include resource IDs**. Leave the **Split cost allocation data** checkbox clear.
5. For **Time granularity**, choose **Hourly**.
6. Under **Data export delivery options**, do the following:
   1. For **Compression type and file format**, select **Parquet - Parquet**.
   2. For **File versioning**, select **Overwrite existing data export file**.
7. Under **Data export storage settings**, enter the **S3 bucket name** as *billing-export-{your AWS account number}*. Replace *{your AWS account number}* with a valid AWS account ID.
8. For the **S3 path prefix**, enter *reports* as your prefix.

The following image displays the recommended CUR settings:

<div data-with-frame="true"><figure><img src="/files/w0siHQ5NO1zWUKs5ZtsN" alt=""><figcaption><p>The recommended Cost and Usage Report settings.</p></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.finops.softwareone.com/system/data-sources/amazon-web-services/create-cost-and-usage-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.