Connection
The Connection page provides the network endpoints and client connection details that you need to access a VeloDB Cloud warehouse. Use it to choose a public or private network path, configure private connectivity, and retrieve the connection information for your client.
The available options depend on the warehouse deployment type:
- A software as a service (SaaS) warehouse is managed by VeloDB Cloud.
- A bring your own cloud (BYOC) warehouse runs in your cloud account and virtual private cloud (VPC) or virtual network (VNet).
For a SaaS warehouse, use a public endpoint when clients can connect over the public network, or use a private endpoint when clients must connect through your VPC or VNet. You can also configure a private path for console data-plane operations, such as SQL Editor and Import Data.
For a BYOC warehouse, configure your cloud network so that clients can reach the warehouse, then use the connection details provided by the page.
To open the page, select a warehouse in the VeloDB Cloud console, and then click Connection in the left navigation pane. Choose the section that matches your deployment type:
| Deployment type | Connection page | Network ownership |
|---|---|---|
| SaaS | Provides Public Endpoint and Private Endpoint tabs. | VeloDB Cloud provides the warehouse endpoints. You control who can reach them. |
| BYOC | Opens Connect to your warehouse without Public Endpoint or Private Endpoint tabs. | You control routing, security groups, network ACLs, and public exposure in your cloud account. |
Connect to a SaaS warehouse
VeloDB Cloud provides two ways to connect to a SaaS warehouse: use a Public Endpoint for connections over the public network, or use a Private Endpoint to connect through a private network. Choose the option that matches your network and security requirements.
Public endpoint
Use Public Endpoint to connect to a SaaS warehouse over the public network. Configure the Internet Protocol (IP) allowlist to restrict which source IP addresses can reach the warehouse. From the connection method dropdown list, choose MySQL CLI, JDBC, Stream Load, or MCP, and then copy the generated connection details.
See Public Endpoint and Connection Methods.
Private endpoint
The Private Endpoint tab separates two connection directions:
- Access VeloDB from Your VPC: Create an endpoint in your VPC so applications can connect privately to the warehouse. See Access VeloDB from Your VPC.
- Grant VeloDB Cloud Access to Your VPC: Publish an endpoint service so the warehouse can connect privately to a data source in your VPC. See Grant VeloDB Cloud Access to Your VPC.
These connections are region-specific. Configure the cloud endpoint or endpoint service in the same region as the warehouse.
Standard cloud-provider network charges apply to private endpoints and endpoint services. Eligible data transfer may also incur the VeloDB Cloud Data Transfer Fee.
Connect to BYOC warehouse
A BYOC warehouse runs in your cloud account and VPC. The Connection page provides MySQL CLI, JDBC, Stream Load, and MCP connection methods, but it does not provide SaaS Public Endpoint or Private Endpoint setup.
Before connecting, make the displayed host and ports reachable from the client through your cloud network. See Connect to a BYOC Warehouse.
Connect the console privately
The SaaS Private Endpoint tab configures warehouse service traffic. It does not make data-plane requests from the VeloDB Cloud console private.
To route console features such as SQL Editor, Import Data, and Query Audit through a private path, configure a warehouse-specific console endpoint. This option applies to both SaaS and BYOC warehouses. Console control-plane operations, including sign-in, warehouse management, members, and billing, continue to use the shared public endpoint.
See Private connectivity to the warehouse-specific console endpoint.
Connection methods
The following methods are available for both SaaS and BYOC warehouses:
- MySQL CLI
- JDBC
- Stream Load
- MCP
BYOC warehouses also provide Arrow Flight SQL. For connection details and client examples, see Arrow Flight SQL.
For the fields, generated commands, and client configuration examples, see Connection Methods.