> 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.md).

# Data sources

The **Add** option on the **Data sources** page allows you to connect your data source to FinOps for Cloud. The supported data sources include Amazon Web Services, Google Cloud Platform, and Microsoft Azure. 

Before adding a data source, you must complete certain prerequisites, depending on the type of data source you are adding. In addition, you might also need to complete certain tasks on the cloud provider's side and some in FinOps for Cloud. 

To learn about all the prerequisites and onboarding steps for each of the supported data sources, see the following links:

* [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)

To manage the settings of your connected data sources, see [Manage Data Sources](/system/data-sources/manage-data-sources.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.finops.softwareone.com/system/data-sources.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.