Connect to Your SaaS Warehouse
To connect an application to a SaaS warehouse, select the warehouse in the VeloDB Cloud Console and open Connect. Choose the endpoint based on how the application reaches the warehouse.
Choose an endpoint
| Where the client connects from | Which option to use |
|---|---|
| Over the public internet | Select Public Endpoint. Use the Public IP Allowlist to restrict access to the client's outbound IP address or CIDR range. |
| From your AWS VPC or Azure virtual network | Select Private Endpoint > Access VeloDB from Your VPC. Create a private endpoint in the same cloud provider and region as the warehouse. Follow Private Connectivity for the provider-specific steps. |
For a public endpoint, choose your connection method on the Public Endpoint tab. For a private endpoint, wait for it to become available, then choose the method in its endpoint row. Copy the host, port, and connection settings for your client. See Connection Methods.
Cross-account AWS PrivateLink connectivity
When your VPC and the SaaS warehouse are in different AWS accounts, the side that initiates the connection owns the interface endpoint. If both the application and the warehouse need to initiate connections, configure each direction separately.
| Connection direction | What you do | What VeloDB Cloud does |
|---|---|---|
| Application to warehouse | Create an interface endpoint in the client VPC using the warehouse service name. Register its endpoint ID in the VeloDB Cloud Console. | Publishes the warehouse endpoint service and provides its name. |
| Warehouse to private data source | Publish an endpoint service backed by a Network Load Balancer and authorize the VeloDB Cloud account. | Creates an interface endpoint using the service name you provide. |
Cloud-provider network charges apply to private endpoints. Eligible traffic may also incur the VeloDB Cloud data transfer fee.