Skip to main content
If your database is in a private network within Amazon Web Services (AWS), Omni can connect to your database via PrivateLink. In this configuration, Omni establishes an encrypted connection from our network to your network via a VPC endpoint.

​
Limitations

Only regular VPC endpoint services are supported. Redshift-managed VPC endpoints are not supported.

​
Requirements

To follow the steps in this guide, you’ll need permissions in AWS that allow you to create VPC endpoint services.

​
Setup

1

Set up a VPC endpoint in your AWS account

In your AWS account, set up a VPC endpoint service that connects to your database:
  • Allow access to our account principal: arn:aws:iam::767117061426:root
  • Enable cross-region access and allow access to the regions of your Omni environment:
    RegionPrimaryDisaster recovery
    EastUsaus-east-1us-west-2
    Irelandeu-west-1eu-central-1
    Australiaap-southeast-2ap-southeast-4
    Canadaca-central-1ca-west-1
2

Contact Omni support

Contact Omni support with the following information:
  • The name of your VPC endpoint service, for example com.amazonaws.vpce.REGION.vpce-svc-XXXXXXXXXX
  • The port your database will be listening on
  • Technical contact details, in case of connection difficulties

​
What’s next?

After you contact Omni support with the information in step 2, we’ll create a VPC endpoint that connects to your service to support the connection to the database. If your service requires manual approval of new endpoint connections, we will contact you to request approval. 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.