Connect Redshift to Odie so your customer data can become part of the Odie Customer Knowledge Graph. This connection authorizes Odie to access Redshift. It does not begin importing data.
After you authenticate, our Activation team will contact you and guide the ingestion setup. Together, you will decide which data to bring in, how it maps to Odie, and how often it should refresh.
Before You Start
Have the following information ready:
- An Odie administrator who can add and manage integrations.
- An AWS administrator who can configure the IAM role used for the connection.
- Your Redshift deployment type and AWS region.
- Your cluster identifier for a provisioned cluster, or workgroup name for Redshift Serverless.
- The database and database user Odie should use.
- The Role ARN for the AWS IAM role Odie should use to access Redshift.
Odie uses the Role ARN to authenticate. Do not enter an AWS access key or secret access key in the connection.
Create the Redshift Connection
- In Odie, open Settings > Integrations.
- Select Add a Connection.
- Find Redshift, then select Connect.
- Enter a connection name your team will recognize.
- Complete the Redshift connection details described below.
- Select Create connector.
| Setting | What to enter |
|---|---|
| Deployment type | Select Provisioned cluster or Serverless workgroup based on where your data is stored. |
| Region | The AWS region that hosts your Redshift cluster or workgroup. |
| Cluster identifier | For a provisioned deployment, enter the cluster identifier. |
| Workgroup name | For a serverless deployment, enter the workgroup name. |
| Database | The Redshift database that contains the source data. |
| Database user | The database user Odie should use for the connection. |
| Role ARN | The ARN of the AWS IAM role Odie should use to access Redshift. |
Authenticate the Connection
- After the connector is created, select Authenticate.
- Follow the prompts to authorize the connection.
- Return to the Redshift connection and review the authentication status.
Completing authentication confirms the connection details Odie needs to access Redshift. It does not begin data ingestion.
What Happens Next
Our Activation team will contact you to complete the ingestion setup. They will work with you to:
- Choose the schemas, tables, and views Odie should use.
- Map your source data to Odie objects and properties.
- Confirm the keys and relationships that connect your customer data.
- Set the refresh schedule and decide how new and updated records should be handled.
- Validate the data before ongoing ingestion begins.
Manage the Connection
Open Settings > Integrations, select the Redshift connection, then open Connection Settings. From there, you can:
- Update the deployment type, region, cluster identifier, or workgroup name.
- Update the database, database user, or Role ARN.
- Save the updated settings.
- Authenticate again when the connection details or IAM role change.
If you switch between a provisioned cluster and a serverless workgroup, update the corresponding cluster or workgroup setting, save your changes, then authenticate again.
FAQs
Does authentication start importing data?
No. Authentication prepares the Redshift connection. Your Activation team will guide the ingestion and configuration work before data begins flowing into Odie.
Which deployment type should I select?
Select Provisioned cluster if your data is in a Redshift cluster. Select Serverless workgroup if your data is in Redshift Serverless.
What is a Role ARN?
A Role ARN identifies the AWS IAM role Odie should use to access Redshift. Your AWS administrator can provide it and make sure the role has access to the Redshift environment you plan to connect.
Do I need to provide AWS access keys?
No. Enter the Role ARN in Odie. Do not add an AWS access key or secret access key to the connection.
What should I check if authentication fails?
Confirm the region, deployment type, cluster identifier or workgroup name, database, database user, and Role ARN. Save any corrections, then select Authenticate again.