> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Amazon Redshift

> Learn how to connect to Redshift

Connect Prophecy to your Amazon Redshift data warehouse to read from and write to tables from your pipelines. This page explains how to configure the connection, including required parameters, necessary permissions, and how connections are shared across teams.

## Prerequisites

Prophecy connects to Amazon Redshift using the database credentials you provide. These credentials are used to authenticate your session and authorize all data operations performed during pipeline execution. To use a Redshift connection effectively, your user must have the following permissions:

* `SELECT`, `INSERT`, `UPDATE`, and `DELETE` on the tables used in your Prophecy pipelines.
* `CREATE TABLE`, `DROP TABLE`, or `ALTER TABLE` if your pipelines create or replace tables.
* Access to specific schemas or databases where your tables reside.

To learn more about user permissions, visit [Default database user permissions](https://docs.aws.amazon.com/redshift/latest/dg/r_Privileges.html) in the Amazon Redshift documentation.

## Feature support

The table below outlines whether the connection supports certain Prophecy features.

| Feature                                                                                    | Supported |
| ------------------------------------------------------------------------------------------ | --------- |
| Read data with a [Source gem](/data-analysis/gems/source-target/external-table/redshift)   | Yes       |
| Write data with a [Target gem](/data-analysis/gems/source-target/external-table/redshift)  | Yes       |
| Browse data in the [Environment browser](/data-analysis/development/studio/studio#sidebar) | Yes       |
| Index tables in the [Knowledge Graph](/data-analysis/ai/knowledge-graph/knowledge-graph)   | No        |

## Data type mapping

When Prophecy processes data from Amazon Redshift using SQL warehouses, it converts Redshift-specific data types to formats compatible with your target warehouse. This table shows how [Amazon Redshift data types](https://docs.aws.amazon.com/redshift/latest/dg/c_Supported_data_types.html) are transformed for Databricks and BigQuery.

| Redshift         | Databricks                        | BigQuery                        |
| ---------------- | --------------------------------- | ------------------------------- |
| SMALLINT         | INT<br />Alias: Integer           | INT64<br />Alias: Integer       |
| INTEGER          | BIGINT<br />Alias: Bigint         | INT64<br />Alias: Integer       |
| BIGINT           | BIGINT<br />Alias: Bigint         | INT64<br />Alias: Integer       |
| REAL             | DOUBLE<br />Alias: Double         | FLOAT64<br />Alias: Float       |
| DOUBLE PRECISION | DOUBLE<br />Alias: Double         | FLOAT64<br />Alias: Float       |
| DECIMAL          | DECIMAL(38,5)<br />Alias: Decimal | NUMERIC<br />Alias: Numeric     |
| BOOLEAN          | BOOLEAN<br />Alias: Boolean       | BOOL<br />Alias: Boolean        |
| CHAR             | STRING<br />Alias: String         | STRING<br />Alias: String       |
| VARCHAR          | STRING<br />Alias: String         | STRING<br />Alias: String       |
| DATE             | DATE<br />Alias: Date             | DATE<br />Alias: Date           |
| TIME             | TIMESTAMP<br />Alias: Timestamp   | TIME<br />Alias: Time           |
| TIMETZ           | TIMESTAMP<br />Alias: Timestamp   | TIME<br />Alias: Time           |
| TIMESTAMP        | TIMESTAMP<br />Alias: Timestamp   | TIMESTAMP<br />Alias: Timestamp |
| TIMESTAMPTZ      | TIMESTAMP<br />Alias: Timestamp   | TIMESTAMP<br />Alias: Timestamp |
| VARBYTE          | BINARY<br />Alias: Binary         | BYTES<br />Alias: Bytes         |
| GEOMETRY         | STRING<br />Alias: String         | STRING<br />Alias: String       |
| GEOGRAPHY        | STRING<br />Alias: String         | STRING<br />Alias: String       |
| SUPER            | STRING<br />Alias: String         | STRING<br />Alias: String       |
| HLLSKETCH        | STRING<br />Alias: String         | STRING<br />Alias: String       |
| INTERVAL         | STRING<br />Alias: String         | STRING<br />Alias: String       |

<Info>Learn more in [Supported data types](/data-analysis/gems/data-types).</Info>

## Connection parameters

To create a connection with Redshift, enter the following parameters:

| Parameter                                                                | Description                                                                                              |
| ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| Connection Name                                                          | Name to identify your connection                                                                         |
| Server                                                                   | Redshift cluster server<br />Example: `redshift-cluster-1.abc123xyz789.us-west-2.redshift.amazonaws.com` |
| Port                                                                     | Port used by Redshift (default is `5439`)                                                                |
| Username                                                                 | Your Redshift username                                                                                   |
| Database                                                                 | Name of the Redshift database you want to connect to<br />Example: `analytics_db`                        |
| Password ([Secret required](/data-analysis/environment/secrets/secrets)) | Your Redshift password                                                                                   |

## Sharing connections within teams

Connections in Prophecy are stored within [fabrics](/data-analysis/environment/fabrics/prophecy-fabrics), which are assigned to specific teams. Once a Redshift connection is added to a fabric, all team members who have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the stored connection credentials.

<Warning>
  Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.

  To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
</Warning>