Create a BYOC Warehouse
A BYOC (Bring Your Own Cloud) warehouse provides you with VeloDB Cloud data warehouse installation and operational services within your own cloud resource pool.
Choose a cloud platform
Choose a cloud platform and deployment option before you start. The creation guide for each platform lists its required permissions and network prerequisites.
| Cloud platform | Deployment options | Create a warehouse |
|---|---|---|
| AWS | New VPC, Existing VPC, or Custom Infrastructure. Custom Infrastructure is the only option that supports customer-managed TDE or EBS encryption keys. | Create a BYOC warehouse on AWS |
| Google Cloud | New VPC or Existing VPC. | Create a BYOC warehouse on Google Cloud |
| Azure | New VNet or Existing VNet. | Create a BYOC warehouse on Azure |
For the AWS, Google Cloud, and Azure regions where you can deploy a BYOC warehouse, see Supported Regions.
Feature availability on cloud platforms
Feature availability differs by cloud platform. The following table summarizes feature availability on each platform for BYOC warehouses.
| Feature | AWS | Google Cloud | Azure |
|---|---|---|---|
| Multi-AZ high availability | ✅ | ✅ | ❌ |
| Encryption key (TDE and EBS) | ✅ (Custom Infrastructure only) | Coming soon | Coming soon |
| Resource tags | ✅ | ✅ | ✅ |
Manage resource tags
Add custom tags during warehouse creation to organize and identify the cloud resources that VeloDB Cloud creates in your cloud account. VeloDB Cloud applies the tags to the warehouse and its clusters.
After you create the warehouse, you can view, add, or update tags from Warehouse Settings.
BYOC warehouse fees
A BYOC warehouse has two types of charges: cloud resource fees and VeloDB Cloud compute service fees.
Cloud resource fees
Your cloud provider bills you directly for virtual machines, object storage, private endpoints, and other cloud resources. These charges are separate from VeloDB Cloud charges.
Compute service fees
VeloDB Cloud charges for managing the compute clusters in a BYOC warehouse. Usage is metered in vCPU-hours while a cluster is running. Review usage in the Billing Center. For current rates, see the Pricing page.
You can pay VeloDB Cloud directly or through a supported cloud marketplace. For example, AWS Marketplace consolidates the VeloDB Cloud compute service fee into your AWS bill, while AWS continues to bill cloud resource fees separately. The payment method does not change how you deploy a BYOC warehouse. For committed-use discounting, contact VeloDB sales for a private offer.
Avoid direct changes to managed cloud resources
VeloDB Cloud-created resources have the following tags. Use these tags to identify managed resources in your cloud provider console:
- resource-created-by:
velodb - cloud-resource-profile:
online - resource-used-by-app:
BYOC,MetaService, or a specific warehouse ID. - sdb-cluster-id: A specific cluster ID.
Warning:
Do not modify, stop, detach, or delete VeloDB Cloud-created resources directly in your cloud provider console. These resources are required for warehouse connectivity, storage, and operation. Changes can interrupt running workloads, leave the warehouse unavailable, or cause data loss that VeloDB Cloud cannot automatically recover. Before making any change, determine whether the resource is managed by VeloDB Cloud.
The following actions are particularly risky:
- Modifying or deleting the permissions of an IAM user created by VeloDB Cloud.
- Modifying or deleting virtual machines or storage buckets created by VeloDB Cloud.
- Modifying or deleting security groups or private endpoints created by VeloDB Cloud.
FAQ
Warehouse creation is stuck. What should I check?
The most common cause is a region mismatch. On every cloud platform (AWS, Google Cloud, and Azure), the Region you select in VeloDB Cloud must be the same region where your cloud resources exist, especially your network (VPC or VNet and subnets). If the warehouse region and your network region differ, the deployment cannot place the warehouse in your network and the creation flow stalls.
Before you start, confirm that:
- The Region selected in VeloDB Cloud matches the region of the VPC or VNet and subnets you plan to use.
- For Existing VPC, the VPC or VNet and subnets you select during deployment are in that same region.
If creation is already stuck because of a mismatch, cancel the creation and start again with matching regions. Any cloud resources that were partially created belong to your cloud account and can be identified by the VeloDB tags listed under Avoid direct changes to managed cloud resources.
If you are unsure which resources are safe to remove, contact VeloDB Cloud Support before deleting anything.