> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/aws-onboarding/connect-cur.md).

# How and Why Do I Connect My AWS CUR to Archera?

Archera leverages the AWS Cost and Usage Report to accurately report on cloud costs inclusive of all other discount programs. By integrating with your CUR, we can provide the most accurate cost information and forecasts.

## Setup Options

When connecting to the CUR, customers have two options depending on whether they have an existing CUR defined within AWS:

* **No existing CUR:** Archera will automatically create one as part of the onboarding process and use it.
* **Existing CUR:** It is preferable to connect to the already existing CUR to be able to report on historical costs.

## Connecting to an Existing CUR

1. Navigate to the Archera Settings → Integrations Page: <https://app.archera.ai/settings/integrations>
2. Review Integrations at the bottom of the screen and look for **"Warnings Detected"**
3. Click on the Integration with the Warning Detected
4. Look for a notification that says **"Please Connect CUR:"**
5. Click **"Connect"** and follow the in-app walkthrough to apply the IAM policy to the Archera IAM role for the appropriate CUR
6. Click **"Verify Access"** at the bottom to confirm

## Related Resources

* [Settings & Integrations - Section Overview](/help-center/user-guide/settings-integrations.md)
* [How Does Archera Access my AWS Environment?](/help-center/sign-in-and-security/aws-access.md)
* [What IAM permissions does the Archera AWS production deployment require?](/help-center/aws-onboarding/iam-permissions-production.md)


---

# 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.archera.ai/help-center/aws-onboarding/connect-cur.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.