Create BYOC Warehouse
BYOC (Bring Your Own Cloud) warehouse provides you with VeloDB Cloud data warehouse installation and operational services within your own cloud resource pool.
Create BYOC Warehouse on Cloud Platform
There are slight differences in the preparation and creation steps for different cloud platforms. Please refer to the following document for detailed instructions:
- Amazon Web Services: How to create BYOC Warehouse on AWS
- Google Cloud Platform: How to create BYOC Warehouse on GCP
- Microsoft Azure: How to create BYOC Warehouse on Azure
BYOC Warehouse Fees
It's important to note that the billing for BYOC warehouse is divided into two parts:
- Cloud resource fee: The cost generated by the virtual machines, object storage, private network endpoint, etc. when starting a cluster, charged directly by the cloud platform (for example, AWS), separately from VeloDB.
- Compute service fee: The service fee VeloDB Cloud charges for managing the cluster. In BYOC, VeloDB meters only the compute cluster, by vCPU × running hours, and you can review this usage by the hour in the VeloDB Cloud Console. The first 30 days are free; after that, please refer to the Pricing Page.
How you pay the compute service fee. You can settle it directly with VeloDB, or through a cloud marketplace so it is consolidated into your cloud provider's bill. For example, if you subscribe via AWS Marketplace, the VeloDB compute service fee is consolidated into your monthly AWS bill, while the cloud resource fee is still billed separately by AWS. Subscribing through a marketplace is only a billing channel — it does not change how a BYOC warehouse is deployed. The public marketplace offer is Pay-As-You-Go; for committed-use discounting, contact VeloDB sales for a private offer.
Precautions
Most warehouse resources run within your cloud environment, so avoid operating cloud resources created by VeloDB Cloud directly on the cloud platform console.
The cloud resources created by VeloDB Cloud have the following tags (Tag):
- resource-created-by : velodb
- cloud-resource-profile : online
- resource-used-by-app : BYOC or MetaService or Specific Warehouse ID
- sdb-cluster-id : Specific Cluster ID
You can filter the resources created by VeloDB Cloud through the filter function on the cloud platform console.
Actions that may cause the warehouse to become abnormally unavailable include:
- Modify or delete the permissions of the IAM user created by VeloDB Cloud
- Modify or delete the virtual machines, storage bucket created by VeloDB Cloud
- Modify or delete the security groups, private endpoint created by VeloDB Cloud
Please note, the warehouse unavailability caused by your operations on the cloud platform console may be irrecoverable.
Supported Regions and Availability Zones
This table lists the regions where VeloDB Cloud BYOC Warehouse can be deployed.
| Cloud Platform | Region Name | Region ID |
|---|---|---|
| AWS | Asia Pacific (Mumbai) | ap-south-1 |
| AWS | US West (Oregon) | us-west-2 |
| AWS | US East (N. Virginia) | us-east-1 |
| AWS | Asia Pacific (Hong Kong) | ap-east-1 |
| AWS | Asia Pacific (Singapore) | ap-southeast-1 |
| AWS | Asia Pacific (Tokyo) | ap-northeast-1 |
| AWS | Europe (Ireland) | eu-west-1 |
| AWS | Europe (Frankfurt) | eu-central-1 |
| AWS | Asia Pacific (Thailand) | ap-southeast-7 |
| Google Cloud | US West | us-west1 |
| Google Cloud | US East | us-east4 |
| Google Cloud | US Central | us-central1 |
| Google Cloud | Europe West | europe-west3 |
| Google Cloud | Asia Southeast | asia-southeast1 |
| Azure | West US 3 | westus3 |
| Azure | (Asia Pacific) Central India | centralindia |