This feature is in beta and is subject to change.
Requirements
To follow the steps in this guide, you’ll need:
- Organization Admin permissions in Omni
- In AWS:
- A Redshift provisioned cluster (not Serverless)
- A Redshift cluster in the same AWS region as your Omni instance
- Permissions that allow you to authorize endpoint access from Omni for your Redshift cluster
Limitations
Redshift-managed VPC endpoints must be in the same region as the cluster (your Omni instance):
| Region | Primary |
|---|
| EastUsa | us-east-1 |
| Ireland | eu-west-1 |
| Australia | ap-southeast-2 |
| Canada | ca-central-1 |
| India | ap-south-1 |
Setup
Authorize Omni's AWS account
Before Omni can create a private connection to your Redshift cluster, you need to authorize Omni’s AWS account to create a managed VPC endpoint to your cluster.Run the following command in your AWS environment:aws redshift authorize-endpoint-access \
--cluster-identifier <your-cluster-identifier> \
--account 767117061426
What’s next?
After you contact Omni support with the above information, we’ll create a Redshift-managed VPC endpoint that connects to your cluster to support the connection.
Once this is complete, Omni support will add the new database connection to your Omni instance. The connection can then be used like any other database connection. You’ll need to provide your Redshift authentication credentials (username and password) when setting up the connection in Omni.
