VeloDB Services
VeloDB Services are VeloDB-managed HTTPS services used by platform features that need to communicate with a warehouse but do not connect directly to the warehouse backend service. VeloDB Cloud publishes these services separately in each supported cloud region so that clients can connect to a service endpoint in their own region.
The following access paths currently use VeloDB Services:
| Access path | Purpose | Hostname format |
|---|---|---|
| Warehouse-specific Console endpoint | Carries data-plane requests from the frontend Console UI to a specific warehouse. | <warehouse-id>-studio.<region>.<provider>.velodb.cloud |
| Metrics API | Exposes regional warehouse metrics for monitoring systems. | apps-api.<region>.<provider>.velodb.cloud |
This service model applies to supported SaaS and BYOC use cases. It is separate from direct warehouse connectivity. A SaaS warehouse has its own backend Endpoint Service, while applications connect to a BYOC warehouse through the network in the customer's cloud environment.
Private Connectivity
For each supported region, VeloDB Cloud publishes a service target through the cloud provider's private connectivity technology. You create a private endpoint in the same region and connect it to that target.
| Cloud provider | Private connectivity technology | VeloDB publication identifier |
|---|---|---|
| AWS | AWS PrivateLink | Endpoint Service name |
| Google Cloud | Private Service Connect | Service attachment URI |
| Azure | Azure Private Link | Private Link Service resource ID |
A private endpoint can serve multiple supported VeloDB hostnames in its region. The endpoint does not replace those hostnames. Configure private DNS to resolve each required hostname to the endpoint, and continue to use the original hostname so that TLS validation and request routing work correctly.
The endpoint and the VeloDB service target must be in the same cloud region. Create an endpoint in each region from which clients need private access to VeloDB Services.
A private DNS zone is authoritative for its entire suffix in the networks associated with it. DNS does not fall back to the public zone when a hostname has no matching private record. Add records for every VeloDB hostname under the zone that clients must reach. Otherwise, those hostnames can return NXDOMAIN. If you do not need to cover the entire provider suffix, use a narrower regional zone where your cloud provider supports one.
Service Endpoint References
Choose your cloud provider to find the supported regions, the service identifier published in each region, and instructions for creating the private endpoint and configuring DNS.
| Cloud provider | Service endpoint reference |
|---|---|
| AWS | AWS PrivateLink for VeloDB Services |
| Google Cloud | Google Cloud Private Service Connect for VeloDB Services |
| Azure | Azure Private Link for VeloDB Services |