> 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/add-your-aws-account-to-finops-for-cloud.md).

# Add your AWS account to FinOps for Cloud

The final step in configuring your AWS account for FinOps for Cloud is to add the AWS data source.

### Adding a management or standalone AWS account

The steps to add a management account or a standalone account are similar.

* If you are adding a management account, choose the **Management** account type.
* If you are adding a standalone account or a member account without a management account, choose the **Standalone** account type.

When you add a management or standalone account, you must enter the details of the role to assume (or IAM user and access key) and the details of the billing export.

{% hint style="info" %}
When setting up AWS data sources using an **Assumed Role**, providing an **External ID** is optional. If you decide to use this field, you must include the generated value in the  `Condition` block of your AWS IAM role trust policy using `sts:ExternalId`. For information on how to create a new IAM role, see [Create a new IAM role](/system/data-sources/amazon-web-services/configure-aws-access.md#create-a-new-iam-role).
{% endhint %}

<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%2FTghqeA2O1R0RkuNKeu8o%2Fimage.png?alt=media&amp;token=f0f71389-679d-4e7e-b2c0-d92d545d5908" alt="" width="563"><figcaption><p>Adding a management account to FinOps for Cloud using an assumed role</p></figcaption></figure></div>

### Adding a member AWS account

The steps to add a member account that already has its management account added to FinOps for Cloud are simpler.

<figure><img src="https://756292039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6rFi99rib6iBPaHxldNx%2Fuploads%2FsGnrWDp3puuBwQ7krPiF%2Fimage.png?alt=media&amp;token=4adb4b1f-0710-4475-8604-2ba1e65a6564" alt=""><figcaption><p>Adding a member account to FinOps for Cloud using an assumed role</p></figcaption></figure>


---

# 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/add-your-aws-account-to-finops-for-cloud.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.