> 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/getting-started/onboarding-guide.md).

# Onboarding Guide

Get started in just a few steps.

### **Connect Your Cloud Account**

Connect at least one cloud account to enable OneLens to begin analyzing your costs and resources.

Choose your cloud provider and follow the relevant connection guide:

* **AWS** - [**Connect your AWS**](https://docs.onelens.cloud/integrations/cloud-and-cost-sources/connect-to-aws.md) account. This enables OneLens to begin analyzing your selected resources along with cost and usage data via CUR.
* **Azure** - [**Connect your Azure**](https://docs.onelens.cloud/integrations/cloud-and-cost-sources/connecting-to-azure.md) subscription or management group. OneLens will pull cost data via actual & amortized cost exports.
* **GCP** - [**Connect your GCP**](https://docs.onelens.cloud/integrations/cloud-and-cost-sources/connecting-to-gcp.md) billing account. OneLens will ingest cost data from BigQuery cost exports.
* **OCI** - [**Connect your OCI**](https://docs.onelens.cloud/integrations/cloud-and-cost-sources/connecting-to-oci.md) tenancy. OneLens will pull cost data via Oracle's cost exports.

### **Wait for Data Processing**

Once connected, OneLens will begin ingesting your AWS data. Initial processing may take a few hours depending on data size.

### **Explore Insights**

After data is processed, access dashboards for cost optimization, anomaly detection and optimization opportunities.

### **Integrate Kubernetes (AKS/EKS)**

Enhance your insights by [**integrating your Kubernetes clusters**](https://docs.onelens.cloud/integrations/kubernetes.md) to get a unified view across cloud and containerized workloads.


---

# 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.onelens.cloud/getting-started/onboarding-guide.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.
