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 in the Amazon Redshift documentation.
Feature support
The table below outlines whether the connection supports certain Prophecy features.
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 are transformed for Databricks and BigQuery.
Connection parameters
To create a connection with Redshift, enter the following parameters:
Sharing connections within teams
Connections in Prophecy are stored within 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.
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.
