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

# MongoDB

Set up the MongoDB connection in two ways: `username` and `password`, or certificate authentication. Follow the sections below to create the Depot using either method.

## Pre-requisites specific to DataOS

To create a Depot, you need the Data Admin role. Contact the DataOS Operator or Tenant Admin to get it.

Run this command to see your assigned roles.

```bash
dataos-ctl user get
#Expected Output: 
time="2026-03-30T17:49:18+05:30" level=info msg="😃 user get..."
time="2026-03-30T17:49:19+05:30" level=info msg="😃 user get...complete"

     NAME     │        ID         │  TYPE  │        EMAIL         │                  TAGS
──────────────┼───────────────────┼────────┼──────────────────────┼────────────────────────────────────────
 I Am Groot   │ iamgroottmdcio    │ person │ iam.groot@tmdc.io    │ roles:id:ct-onboarding-data-developer,
              │                   │        │                      │ roles:id:data-dev,
              │                   │        │                      │ roles:id:system-dev,
              │                   │        │                      │ roles:id:user,
              │                   │        │                      │ users:id:iamgroottmdcio

```

## Pre-requisites specific to the source system

* **Username and password**: Obtain from your database administrator.
* **MongoDB node details**: Obtain from your database administrator.

## Steps

Create a MongoDB Depot that references a [MongoDB Secret](/concepts/resources/secret/data-sources/mongodb.md).

### **Step 1: Create a Secret for securing MongoDB credentials**

Create a Secret Resource using the [MongoDB](/concepts/resources/secret/data-sources/mongodb.md) guide.

### **Step 2: Create a MongoDB Depot manifest file**

Create a manifest file for the MongoDB Depot.

{% tabs %}
{% tab title="Manifest file" %}

```yaml
name: ${{mongodb-name}}
version: v2alpha
type: depot
tags:
  - MongoDB
  - depot
  - nosql
description: "MongoDB NoSQL document database depot"
spec:
  type: mongodb
  spec:
    subprotocol: "mongodb"
    nodes:
      - ${{mongodb-nodes}}
  secrets:
    - id: "${{tenant-id}}:${{mongodb-secret-name}}"
      purpose: scan
```

{% endtab %}

{% tab title="Example" %}

```yaml
name: ${{mongodb-name}}
version: v2alpha
type: depot
tags:
  - MongoDB
  - depot
  - nosql
description: "MongoDB NoSQL document database depot"
spec:
  type: mongodb
  spec:
    subprotocol: "mongodb"
    nodes:
      - ${{mongodb-nodes}}
  secrets:
    - id: "${{tenant-id}}:${{mongodb-secret-name}}"
      purpose: scan
```

{% endtab %}
{% endtabs %}

### **Step 3: Apply the Depot manifest file**

Apply the manifest with the DataOS CLI:

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

## Verify the Depot creation

Verify the Depot in two ways:

* List Depots where you are the owner:

  ```bash
  dataos-ctl resource get -t depot
  ```
* List all Depots in the current Tenant:

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

## Delete a Depot

{% hint style="warning" %}
Best practice: Delete Resources that are no longer in use to save time and reduce costs.
{% endhint %}

To delete a Depot, use the DataOS CLI:

{% tabs %}
{% tab title="Command 1" %}

```bash
dataos-ctl resource delete -t depot -n ${{name}}
```

{% endtab %}

{% tab title="Command 2 " %}

```bash
dataos-ctl resource delete -i "${{resource-name}}|v2alpha|depot"
```

{% endtab %}

{% tab title="Command 3" %}

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

{% endtab %}
{% endtabs %}

Specify the Resource type and Depot name in the `delete` command.

**Example:**

{% tabs %}
{% tab title="Command 1" %}

```bash
dataos-ctl resource delete -t depot -n testdepot
#output
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}

{% tab title="Command 2" %}

```bash
dataos-ctl resource delete -i "testdepot|v2alpha|depot"
#output
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}

{% tab title="Command 3" %}

```bash
dataos-ctl resource delete -f /path/to/depot.yaml
#output
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..."
time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..."
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted"
time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete"
```

{% endtab %}
{% endtabs %}

## MongoDB Depot configured with multiple nodes

MongoDB supports a Depot configured with multiple nodes. You can reuse the Depot created for the MongoDB CDC source as a destination, limited to the `replace` incremental strategy.

```yaml
name: ${{name}}
version: v1
type: depot
tags:
  - ${{tag-1}} # optional
  - ${{tag-2}} # optional
  - ${{tag-3}} # optional
owner: ${{owner-id}} # optional
layer: user
description: ${{description}}
spec:
  type: mongodb
  spec:
    subprotocol: ${{subprotocol}} # mandatory
    nodes: 
    - ${{node-1}} # mandatory
    - ${{node-2}} 
    - ${{node-3}} 
    params: # optional
      authSource: ${{auth-source}}
      replicaSet: ${{replica-set}}
  secrets:
    - id: "${{tenant-id}}:${{secret-name}}"
      purpose: scan
    - id: "${{tenant-id}}:${{secret-name}}"
      purpose: query
    - id: "${{tenant-id}}:${{secret-name}}"
      purpose: rw
```


---

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