> 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/consume/nilus.md).

# Data ingestion

Use [Nilus](/concepts/resources/nilus.md) when you want managed ingestion patterns that read from source systems connected via Depot.

## How to consume a Depot in Nilus?

1. Ensure the Depot is created, and you have access permissions.
2. Identify the source path you want to ingest from the Depot.
3. Use the Depot UDL as the input/source reference in your Nilus pipeline configuration.
4. Select the ingestion mode based on your use case:
   * Batch mode for periodic loads
   * CDC mode for near real-time replication
5. Configure the target sink and schedule, then run and monitor the pipeline.

## Nilus Workflow example (batch)

The following Nilus Workflow reads from a PostgreSQL Depot and writes to an MSSQL Depot:

```yaml
name: mssql-to-pg2
version: v2alpha
type: workflow
tags:
  - dataos:resource:workflow
  - dataos:tenant:ct-onboarding
description: Nilus Batch Service Sample
owner: iamgroottmdcio
tenant: ct-onboarding
spec:
  type: instance
  dag:
    - name: pvc-test
      spec:
        runAsUser: iamgroottmdcio
        runAsApikey: '**********'
        compute: ct-compute
        stack: nilus:1.0
        stackSpec:
          sink:
            address: dataos://niluspgdepot1?purpose=rw
            options:
              dest-table: nilus_testing.ds2_dec_finaltesting_mssql_to_pg_11
              incremental-strategy: append
          source:
            address: dataos://nilusmssqldepot?purpose=rw
            options:
              source-table: nilus.cdc_test
```

## Typical use cases

* CDC and batch data movement into target zones.
* Scheduled ingestion pipelines from operational systems.
* Standardized ingestion for repeatable data product workflows.

## Next step

Choose the Nilus mode (batch or CDC), configure source and sink, and execute the pipeline.


---

# 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/consume/nilus.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.