> 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/request-historical-data.md).

# Request historical data

When you create a Cost and Usage Report in an AWS-linked account, the S3 bucket is automatically populated with data from the beginning of the current month. 

However, if the AWS account has existed for longer than this period, you can request a backfill of historical cost and usage data.

### Request a backfill of your cost data

To request a backfill of your historical data, create a support case with AWS. 

For information on how to open a support case and the information to include in your request, see the following link in the AWS Data Exports User Guide:

<https://docs.aws.amazon.com/cur/latest/userguide/troubleshooting.html#backfill-data>

### Perform a billing reimport in FinOps <a href="#perform-a-billing-reimport" id="perform-a-billing-reimport"></a>

To perform a billing reimport in FinOps for Cloud:

1. Navigate to the **Data sources** page.
2. Select the AWS data source containing the updated S3 bucket, then select **Billing reimport**.
3. In **Import from**, choose the start date of your historical billing data.
4. Select **Schedule import**.&#x20;

<div data-with-frame="true"><figure><img src="https://756292039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6rFi99rib6iBPaHxldNx%2Fuploads%2FjKVCE0VXirsdYwb1do47%2Fimage.png?alt=media&amp;token=6698cac5-4677-4c34-a6df-d2aed9659cd0" alt=""><figcaption><p>The option to reimport billing data.</p></figcaption></figure></div>

Once the import process has been initiated, it might take several hours for the process to complete, depending on the amount of historical data.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.finops.softwareone.com/system/data-sources/amazon-web-services/request-historical-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.