Integrating with Redshift

Drivetrain supports connecting to Amazon Redshift as a data source for financial planning and analysis (FP&A). This guide explains how to configure and establish the connection.

Prerequisites

1. An active Amazon Redshift cluster with access to the database you want to connect.

2. A user account with the appropriate read permissions on the required database and schema.

Required Information

When setting up the Redshift connector in Drivetrain, you’ll need to provide the following details:

Host The endpoint of your Redshift cluster. Example: redshift-cluster-1.abc123xyz.us-east-1.redshift.amazonaws.com

Port The port number on which your Redshift cluster is running. Default: 5439

Database Name (dbname) The name of the database within your Redshift cluster to connect to. Example: fpna_db

User The Redshift user with read-only or required privileges. Example: drivetrain

Password The password for the above user.

Schema (Optional) The schema within the specified database to query by default. If not provided, Redshift will use the user’s default schema (often public). Example: finance_schema

Please share the above information with your Drivetrain Customer Success Manager to get started.

Connecting via VPC Peering

If your Redshift cluster is hosted in a private subnet, you can connect it to Drivetrain using AWS VPC Peering instead of a public endpoint.

To set up VPC Peering, please share the following details with your Drivetrain Customer Success Manager:

• Account ID

• Region

• VPC ID (Accepter)

Drivetrain will initiate the peering request from its VPC. Once you accept the request in your AWS console and configure routing, the connection will be established.

For detailed instructions on creating and accepting VPC peering connections, refer to the AWS VPC Peering documentation.