> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/integrations/cloud-and-cost-sources.md).

# Cloud & Cost Sources

OneLens connects directly to your cloud accounts to provide real-time visibility into costs, usage, and optimization opportunities. OneLens supports the following cloud providers:

### Amazon Web Services (AWS)

Start by [**connecting your AWS account**](/integrations/cloud-and-cost-sources/connect-to-aws.md). This integration allows OneLens to securely ingest resource, usage metrics via AWS SDK calls and Cost and Usage Reports (CUR) from your AWS S3 bucket. Cost data is showcased through our unified Cost Atlas and other in-depth features.

### Azure (AZ)

Start by [**connecting your Azure**](/integrations/cloud-and-cost-sources/connecting-to-azure.md) Subscriptions, Management Groups or Resource Groups to OneLens. We use an App Registration with access to Microsoft's Cost Data Exports to provide insights into your spend. Cost data is showcased through our unified Cost Atlas.

### Google Cloud Platform (GCP)

**Start by** [**connecting your GCP**](/integrations/cloud-and-cost-sources/connecting-to-gcp.md) Projects, Folders or Organizations to OneLens. We use a Service Account with access to Google's BigQuery Detailed Usage exports to provide insights into your spend. Cost data is showcased through our unified Cost Atlas.

### Oracle Cloud Infrastructure (OCI)

**Start by** [**connecting your OCI**](/integrations/cloud-and-cost-sources/connecting-to-oci.md) Tenancies, Compartments or Resources to OneLens. We use an external user with access to the Cost Exports provided by Oracle to provide insights into your spend. Cost data is showcased through our unified Cost Atlas.

#### Databricks

Start by connecting your Databricks account to OneLens. This integration enables OneLens to securely ingest billing and usage data from Databricks system tables for cost analysis, anomaly detection, and optimization insights.

We use a **Service Principal with access to Unity Catalog system tables and a SQL Warehouse** to query usage and billing metadata. Data is retrieved from system tables such as `system.billing`, `system.compute`, and `system.access`.

Cost and usage data is showcased through our unified Cost Atlas and other in-depth optimization features.

{% hint style="info" %}
Once connected:

* Data is processed daily
* Insights are generated automatically
* No manual actions are required after setup
  {% endhint %}


---

# 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.onelens.cloud/integrations/cloud-and-cost-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.