> 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/v1/resources/lakehouse/create-a-lakehouse-depot.md).

# Create a Lakehouse Depot

A Depot of type `lakehouse` connects to an existing Lakehouse instance, exposing its REST Catalog and object storage through the DataOS catalog layer. Create the Depot after the Lakehouse is running.

### Before you begin

Ensure that the Lakehouse is active. You also need its REST Catalog service address and ingress path.

Use the Lakehouse storage settings when you configure the Depot. The `metastoreUrl` field uses the internal Kubernetes service address. The `metastoreRelativePath` field uses the REST Catalog ingress path.

### Create the Depot

1. Set `depot.type` to `lakehouse`.
2. Set `storageType` to `s3`, `abfss`, or `gcs`.
3. Set `catalogType` to `REST`.
4. Configure the matching storage block and a Secret with `rw` access.

{% hint style="info" %}
The `metastoreUrl` and `metastoreRelativePath` fields identify the REST Catalog service. Use the internal Kubernetes service address for `metastoreUrl`.
{% endhint %}

{% tabs %}
{% tab title="S3" %}

```yaml
name: depotname
version: v2alpha
type: depot
description: "Lakehouse depot: Iceberg REST catalog + S3 storage"
tags:
  - lakehouse
  - s3
depot:
  type: lakehouse
  description: "Iceberg data depot backed by ${lakehouse-name}"
  spec:
    storageType: s3
    catalogType: REST
    metastoreUrl: <kong-proxy-service-name>.<environment-namespace>.svc.cluster.local:80
    metastoreRelativePath: /<ingress-path>
    s3:
      bucket: ${s3-bucket-name}
      relativePath: ${relative-path}
      format: ICEBERG
      region: ${aws-region}
  secrets:
    - id: ${tenant}:${secret-name}
      purpose: rw
```

{% endtab %}

{% tab title="ABFSS" %}

```yaml
name: depotname
version: v2alpha
type: depot
description: "Lakehouse depot: Iceberg REST catalog + ABFSS storage"
tags:
  - lakehouse
  - abfss
depot:
  type: lakehouse
  description: "Iceberg data depot backed by ${lakehouse-name}"
  spec:
    storageType: abfss
    catalogType: REST
    metastoreUrl: <kong-proxy-service-name>.<environment-namespace>.svc.cluster.local:80
    metastoreRelativePath: /<ingress-path>
    abfss:
      account: ${abfss-account}
      container: ${container-name}
      endpointSuffix: ${endpoint-suffix}
      relativePath: ${relative-path}
      format: ICEBERG
  secrets:
    - id: ${tenant}:${secret-name}
      purpose: rw
```

{% endtab %}

{% tab title="GCS" %}

```yaml
name: depotname
version: v2alpha
type: depot
description: "Lakehouse depot: Iceberg REST catalog + GCS storage"
tags:
  - lakehouse
  - gcs
depot:
  type: lakehouse
  description: "Iceberg data depot backed by ${lakehouse-name}"
  spec:
    storageType: gcs
    catalogType: REST
    metastoreUrl: <kong-proxy-service-name>.<environment-namespace>.svc.cluster.local:80
    metastoreRelativePath: /<ingress-path>
    gcs:
      bucket: ${gcs-bucket-name}
      relativePath: ${relative-path}
      format: ICEBERG
  secrets:
    - id: ${tenant}:${secret-name}
      purpose: rw
```

{% endtab %}
{% endtabs %}

### Apply and verify

Apply the Depot manifest:

```bash
dataos-ctl resource apply -f ${depot-manifest-file-path}
```

Verify the Depot:

```bash
dataos-ctl resource get -t depot
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/references/v1/resources/lakehouse/create-a-lakehouse-depot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.