> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/dataos-operator/operator.md).

# DataOS Operator overview

End-to-end Operator workflow from infrastructure deployment to Tenant readiness.

The Operator manages the DataOS Instance and prepares and sets up the Tenants for use in the Instance Admin application. This includes provisioning the Instance, setting up Tenants and their resources, and handing them over to Tenant Admins.

Before you create anything, DataOS must be connected to your identity provider so users can sign in with their enterprise identity. This is a one-time setup. See [Authentication and Authorization](/operate/authentication-and-authorization.md).

{% hint style="info" %}
Access to a Tenant and its resources is managed separately through Tenant roles.
{% endhint %}

Use the phases below as your checklist. Each phase links to the detailed runbook.

## Provision Data Plane

After the customer provisions the cloud infrastructure, install the Data Plane: the execution layer that runs in the customer cloud.

* [AWS](/operate/dataos-operator/provision-data-plane/aws.md)
* [Azure](/operate/dataos-operator/provision-data-plane/azure.md)

{% hint style="success" %}
**Phase 1 complete:** the Data Plane is provisioned.
{% endhint %}

## Design Tenants

Plan the Tenant structure before you create anything. See [Design Tenants](/operate/dataos-operator/design-tenants.md): choose the slicing model, and Tenant vs. separate Instance.

## Create & setup Tenant

Set up and configure Tenants to organize workloads, connect resources, and manage access:

* [Create the Tenant](/operate/dataos-operator/create-tenants.md) in **Instance Admin**.
* [Invite users and assign roles](/operate/dataos-operator/create-tenants.md#invite-users-and-assign-roles), starting with the Tenant Admin.
* [Connect the Data Plane](/operate/dataos-operator/create-tenants.md#connect-dataplane) and [attach Compute](/operate/dataos-operator/create-tenants.md#attach-compute) to the Tenant.

See [Roles & Permissions](/operate/access-control/roles-and-permissions.md) for role definitions and the capability matrix.

{% hint style="success" %}
**Phase 2 complete:** the Tenant is created, the Data Plane and Compute are attached, and users have roles assigned.
{% endhint %}

## Configure Tenant resources

Install the required Stacks and connect the data sources that Data Product workloads depend on:

* [Deploy Stacks](/operate/dataos-operator/create-tenants/deploy-stacks.md): install the Data Product MCP server and its OAuth broker.
* [Data source access](/operate/tenant-admin/add-data-sources-and-secrets.md): create Secrets and the corresponding Depots for the Tenant.
* [Lakehouse (optional)](/operate/data-admin/manage-lakehouse.md): provision managed Iceberg storage.

{% hint style="success" %}
**Phase 3 complete:** the required Stacks are healthy, at least one data source connection is active, and the Lakehouse is provisioned if needed.
{% endhint %}

## Hand off Tenant

Hand the configured Tenant to the person who will run it day to day. See [Hand off Tenant](/operate/dataos-operator/create-tenants/hand-off-tenant.md) for the readiness checklist and how to assign the Tenant Admin.

A Tenant is ready to hand off when:

* The Data Plane and at least one Compute are attached and active.
* The required Stacks are deployed and healthy.
* At least one data source Secret and Depot are active.
* A sanity Data Product deploys and runs without errors.

{% hint style="success" %}
**Phase 4 complete:** the Tenant Admin owns a deployment-ready Tenant.
{% endhint %}

## Manage access

Once Tenants are handed over, your ongoing scope is the Instance and the planes everything depends on:

[Manage access](/operate/dataos-operator/governance.md): assign Tenant Admins, keep Tenant role design consistent, and audit access.

## Monitor Instance

[Monitoring](/operate/dataos-operator/monitoring.md): Instance and Data Plane health.

## Where to start? <a href="#where-to-start" id="where-to-start"></a>

* [Set up Access control](/operate/access-control.md): Configure authentication and access control for DataOS.
* [Provision Data Plane:](#provision-data-plane) Set up the Data Plane required to run workloads.
* [Plan Tenant model](/operate/dataos-operator/design-tenants.md): If the Dataplane is already provisioned, skip to this step to create and configure Tenants.


---

# 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://v2.dataos.info/operate/dataos-operator/operator.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.