> 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/engine-guide/redshift/recipes/deployment-recipes.md).

# Deployment Recipes

Deploy Vulcan projects to Redshift using DataOS resources.

Use these recipes as a starting `spec` instead of tuning from a blank slate. Pair them with the sizing guidance in [Limits and Performance](https://v2.dataos.info/references/engine-guide/redshift/limits-and-performance.md) if you need to adjust further.

## Daily incremental Kimball (retail shape)

A layered retail product with DQ, semantics, and a depot gateway:

```yaml
# config.yaml (excerpt)
name: retail-redshift
model_defaults:
  dialect: redshift
  start: "2025-01-01"
  cron: "0 */3 * * *"
gateways:
  default:
    connection:
      type: depot
      address: dataos://redshiftdepot?purpose=rw
variables:
  source_schema: public
  bronze_schema: bronzev1
  silver_schema: silverv1
  gold_schema: goldv1
enable_rollup: true
```

```yaml
# Vulcan resource (excerpt)
spec:
  engine: redshift
  depots:
    - dataos://<depot-name>?purpose=rw
  workflow:
    schedule:
      crons: ["0 3 * * *"]
      timezone: UTC
      endOn: "2027-01-01T00:00:00Z"
      concurrencyPolicy: Forbid
  api:
    replicas: 2
```

## Split build vs query (WLM)

Optional: separate DB users and WLM query groups: an ETL user for `plan`/`run`, and a read-only user for API/BI traffic through a second depot purpose, `query`.

## First-time backfill (multi-year history)

Temporarily raise `concurrent_tasks`, widen the incremental `start`, and scale the cluster or Serverless RPU. Revert all three once the backfill completes.

## Local full stack

```bash
set -a && source .env && set +a
docker run -d --name vulcan-state \
  -e POSTGRES_USER=vulcan -e POSTGRES_PASSWORD=vulcan \
  -e POSTGRES_DB=statestore -p 5432:5432 postgres:15
vulcan migrate
vulcan plan
```

## Next steps

Return to [Redshift](https://v2.dataos.info/references/engine-guide/redshift.md) to continue with serving, operations, and troubleshooting guidance.


---

# 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/engine-guide/redshift/recipes/deployment-recipes.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.
