> 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/finops-for-cloud/getting-started/data-sources.md).

# Add data sources

To start monitoring your cloud resources, you must connect your billing source to FinOps for Cloud. The supported data sources include Amazon Web Services, Google Cloud Platform, and Microsoft Azure.&#x20;

The onboarding process in FinOps requires you to meet certain prerequisites based on the data source you want to add. These prerequisites can differ depending on the source.

Additionally, you might need to complete certain tasks on the cloud provider's side and some in FinOps for Cloud. For instance, if you are connecting an AWS source, you must create Cost and Usage Reports, configure policies in the AWS console, and then add your AWS account to FinOps.&#x20;

## Add a data source

{% hint style="info" %}
Before adding a data source, make sure to go through the following links to understand the prerequisites and onboarding steps for supported data sources:&#x20;

* [Amazon Web Services](/system/data-sources/amazon-web-services.md)
* [Microsoft Azure](/system/data-sources/microsoft-azure.md)
* [Google Cloud Platform](/system/data-sources/google-cloud-platform.md)

Then, follow the steps in this section to add your data source to FinOps for Cloud.
{% endhint %}

To add a new data source:

1. From the left sidebar, select **Data sources**.
2. On the **Data sources** page, select **Add**.

<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%2F2oLUcmMk4trfFJ5tBxp1%2Fimage.png?alt=media&amp;token=b884c369-fa6e-4d93-a2d7-f924fbd7c6f7" alt=""><figcaption><p>Use the Data sources page to add and manage connected sources.</p></figcaption></figure></div>

3. On the **Connect data source** page, do the following:
   1. Select the source you want to add, for example, **AWS**, **Azure**, or **GCP**.&#x20;
   2. Select the connection type:
      1. **AWS** – Choose whether to connect a root account or a linked account.
      2. **Azure** – Choose whether to connect a tenant or a subscription.&#x20;
      3. **GCP** – Choose whether to connect a tenant or a project. &#x20;
4. Enter the account credentials. The fields and options vary depending on the source you are connecting.
5. Select **Connect**.

The **Data sources** page displays connected cloud accounts and subscriptions, including current costs, forecasted costs, billing information, and entitlement status.&#x20;

**Entitled** indicates whether a connected AWS account or Azure subscription is covered by a SoftwareOne service entitlement. When available, the associated entitlement ID is displayed.

To view the details of a connected data source, select its name. You can then view its properties and manage the data source, including renaming it, updating credentials, and disconnecting it.


---

# 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/finops-for-cloud/getting-started/data-sources.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.
