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 or a Redshift Serverless workgroup
- A Redshift cluster or workgroup in the same AWS region as your Omni instance
- Permissions that allow you to authorize endpoint access from Omni for your Redshift cluster or workgroup
Limitations
Redshift-managed VPC endpoints must be in the same region as the cluster or workgroup (your Omni instance):
For cross-region access, you’ll need to use a traditional AWS PrivateLink setup with a network load balancer instead. See AWS PrivateLink for more information.
Setup
Choose the tab that matches your Redshift deployment type.- Redshift Provisioned
- Redshift Serverless
Contact Omni support
Contact Omni support with the following information:
- Your AWS account ID (the 12-digit account ID that owns the Redshift cluster)
- The Redshift cluster identifier
- The AWS region where the cluster is deployed
- A unique database label for your connection in Omni (e.g. prod, stg, retail, etc.)
- Technical contact details, in case of connection difficulties

