> 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/vulcan/configurations/engines.md).

# Engines

Use engine configuration to connect Vulcan to your warehouse or compute layer.

Each engine page lists connection fields, prerequisites, permissions, and engine-specific behavior.

## What you configure here

Use this section when you need to:

* choose the engine adapter for a gateway
* set engine-specific connection properties
* check permissions and authentication requirements
* understand engine-specific materialization behavior

## Basic pattern

Every gateway needs a `connection.type`.

Your project also needs `model_defaults.dialect`.

In most projects, both values match the target engine.

```yaml
gateways:
  default:
    connection:
      type: postgres
      host: warehouse
      port: 5432
      database: analytics
      user: vulcan
      password: "{{ env_var('POSTGRES_PASSWORD') }}"

model_defaults:
  dialect: postgres
```

{% hint style="info" %}
Use environment variables for secrets such as passwords, tokens, and key files.
{% endhint %}

## Choose an engine

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>BigQuery</strong><br>Configure BigQuery authentication, permissions, and connection settings.</td><td><a href="/pages/1m8lmkSpw4EFEykMZ6Hs">/pages/1m8lmkSpw4EFEykMZ6Hs</a></td></tr><tr><td><strong>Databricks</strong><br>Connect Vulcan to Databricks and review engine-specific options.</td><td><a href="/pages/S6ompQaVISK65AaHa4pR">/pages/S6ompQaVISK65AaHa4pR</a></td></tr><tr><td><strong>Microsoft Fabric</strong><br>Set up Microsoft Fabric connection details for Vulcan workloads.</td><td><a href="/pages/o55DLTb1LoDatBp8YlD0">/pages/o55DLTb1LoDatBp8YlD0</a></td></tr><tr><td><strong>Microsoft SQL Server</strong><br>Configure SQL Server connectivity and required connection fields.</td><td><a href="/pages/zDGPoGIudoOvq7TRD4QA">/pages/zDGPoGIudoOvq7TRD4QA</a></td></tr><tr><td><strong>MySQL</strong><br>Review MySQL connection requirements and engine behavior.</td><td><a href="/pages/a98hNzmJYdMLVnHqRXaY">/pages/a98hNzmJYdMLVnHqRXaY</a></td></tr><tr><td><strong>Postgres</strong><br>Configure PostgreSQL gateways for development or production workloads.</td><td><a href="/pages/S9VgIvr7phi4omubTHaJ">/pages/S9VgIvr7phi4omubTHaJ</a></td></tr><tr><td><strong>Amazon Redshift</strong><br>Set up Redshift-specific connection properties and permissions.</td><td><a href="/pages/EESGkr7wLpXy3FQwzC6P">/pages/EESGkr7wLpXy3FQwzC6P</a></td></tr><tr><td><strong>Snowflake</strong><br>Configure Snowflake authentication, warehouse settings, and connectivity.</td><td><a href="/pages/Zaz60Y6pVdpSFwO6BbdL">/pages/Zaz60Y6pVdpSFwO6BbdL</a></td></tr><tr><td><strong>Spark</strong><br>Review Spark engine support and supported connection patterns.</td><td><a href="/pages/9kSJTx5GVi0bs33cshRl">/pages/9kSJTx5GVi0bs33cshRl</a></td></tr><tr><td><strong>Trino</strong><br>Set up Trino connectivity and engine-specific configuration.</td><td><a href="/pages/64YwSJ4ItdQHO6iKjYTv">/pages/64YwSJ4ItdQHO6iKjYTv</a></td></tr></tbody></table>

## Engine availability

Some engines are fully available today.

Some are still marked as work in progress.

Check the engine page before you finalize production configuration.

## Best practices

Keep `connection.type` and `model_defaults.dialect` aligned unless you have a specific transpilation need.

Use separate gateways for dev, staging, and prod when connection details differ.

Store credentials outside `config.yaml` and inject them at runtime.


---

# 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/vulcan/configurations/engines.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.