# 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**](/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**](/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**](/integrations/cloud-and-cost-sources/connecting-to-gcp.md) billing account. OneLens will ingest cost data from BigQuery cost exports.
* **OCI** - [**Connect your OCI**](/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**](/integrations/kubernetes.md) to get a unified view across cloud and containerized workloads.


---

# Agent Instructions: 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:

```
GET https://docs.onelens.cloud/getting-started/onboarding-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
