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

# DataOS Operator

- [DataOS Operator overview](https://v2.dataos.info/operate/dataos-operator/operator.md): End-to-end Operator workflow from infrastructure deployment to Tenant readiness.
- [Provision Data Plane](https://v2.dataos.info/operate/dataos-operator/provision-data-plane.md): Provision the Data Plane, the execution layer in the customer cloud: prerequisites, the sequence, and the per-cloud runbooks.
- [AWS](https://v2.dataos.info/operate/dataos-operator/provision-data-plane/aws.md): Provision AWS Data Plane
- [AWS (UI)](https://v2.dataos.info/operate/dataos-operator/provision-data-plane/aws-ui.md): Provision an AWS BYOC Data Plane from the DataOS UI
- [Azure](https://v2.dataos.info/operate/dataos-operator/provision-data-plane/azure.md): Provision Azure Data Plane
- [Azure (UI)](https://v2.dataos.info/operate/dataos-operator/provision-data-plane/azure-ui.md): Provision an Azure BYOC Data Plane from the DataOS UI
- [Design Tenants](https://v2.dataos.info/operate/dataos-operator/design-tenants.md): How to slice Tenants before you create them: the common blueprints and a framework for choosing.
- [Choosing between an Instance and a Tenant](https://v2.dataos.info/operate/dataos-operator/choosing-between-instance-and-tenant.md): Decide whether a new requirement needs a separate DataOS Instance or a Tenant in an existing one.
- [Create & set up Tenant](https://v2.dataos.info/operate/dataos-operator/create-tenants.md): Create a Tenant, attach the Data Plane and Compute, install Stacks, and make it ready for a team to deploy Data Products.
- [Deploy Stacks](https://v2.dataos.info/operate/dataos-operator/create-tenants/deploy-stacks.md): Deploy the Lakehouse MRuntime Stack, the Data Product MCP server, and its OAuth broker for a Tenant.
- [Hand off Tenant](https://v2.dataos.info/operate/dataos-operator/create-tenants/hand-off-tenant.md): Confirm the Tenant is ready, assign a Tenant Admin, and hand day-to-day operation over to them.
- [Manage access](https://v2.dataos.info/operate/dataos-operator/governance.md): What the Operator governs: assigning Tenant Admins, keeping Tenant roles consistent, and auditing high-privilege access.
- [Monitoring](https://v2.dataos.info/operate/dataos-operator/monitoring.md): Watch the Instance Status page and Data Plane health from the Operator's seat.


---

# 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.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.