> 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/references/resources/depot/supported-sources.md).

# Data sources

Choose the source-specific guide for creating a Depot.

Every Depot, regardless of source type, is created the same way: create a Secret, write a Depot manifest, apply it, then verify it. Each source page covers the same core flow:

* source-specific prerequisites
* source-specific Depot manifest template
* apply and verification steps

### Browse supported sources

Select a source to view its prerequisites, manifest template, and setup steps.

#### Databases and warehouses

* [Amazon Redshift](https://v2.dataos.info/references/resources/depot/supported-sources/redshift.md)
* [Databricks](https://v2.dataos.info/references/resources/depot/supported-sources/databricks.md)
* [Google BigQuery](https://v2.dataos.info/references/resources/depot/supported-sources/bigquery.md)
* [Java Database Connectivity (JDBC)](https://v2.dataos.info/references/resources/depot/supported-sources/jdbc.md)
* [MongoDB](https://v2.dataos.info/references/resources/depot/supported-sources/mongo.md)
* [Microsoft SQL Server (MSSQL) or Azure SQL](https://v2.dataos.info/references/resources/depot/supported-sources/mssql.md)
* [MySQL](https://v2.dataos.info/references/resources/depot/supported-sources/mysql.md)
* [Oracle](https://v2.dataos.info/references/resources/depot/supported-sources/oracle.md)
* [PostgreSQL](https://v2.dataos.info/references/resources/depot/supported-sources/postgresql.md)
* [Snowflake](https://v2.dataos.info/references/resources/depot/supported-sources/snowflake.md)

#### Object storage and filesystems

* [Azure Blob File System Secure (ABFSS)](https://v2.dataos.info/references/resources/depot/supported-sources/abfss.md)
* [Google Cloud Storage (GCS)](https://v2.dataos.info/references/resources/depot/supported-sources/gcs.md)
* [Lakehouse (ABFSS / GCS / S3: Iceberg)](https://v2.dataos.info/references/resources/depot/supported-sources/lakehouse.md)
* [Simple Storage Service (Amazon S3)](https://v2.dataos.info/references/resources/depot/supported-sources/s3.md)

#### Streaming, search, and event systems

* [Eventhub](https://v2.dataos.info/references/resources/depot/supported-sources/eventhub.md)
* [Elasticsearch](https://v2.dataos.info/references/resources/depot/supported-sources/elasticsearch.md)
* [Kafka](https://v2.dataos.info/references/resources/depot/supported-sources/kafka.md)
* [Opensearch](https://v2.dataos.info/references/resources/depot/supported-sources/opensearch.md)

### Related references

* For supported table formats, see the [Supported Table Format Section](https://v2.dataos.info/references/resources/depot/supported-table-format.md).
* For the broader connector matrix across DataOS components, see [Supported Connectors](https://v2.dataos.info/references/supported-connectors.md).


---

# 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/references/resources/depot/supported-sources.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.
