Skip to main content

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:

Deployment options​

The deployment option determines how much of the network and infrastructure VeloDB Cloud creates and how much you prepare and manage.

  • On AWS, you choose New VPC, Existing VPC, or Custom Infrastructure. For what each option does and when to use it, see the AWS guide. Custom Infrastructure is AWS-only and is required for customer-managed keys used with warehouse-level TDE or EBS encryption.
  • On Google Cloud and Azure, you choose between New VPC and Existing VPC during creation.

Cloud platform feature support​

Feature availability differs by cloud platform. The table below summarizes what each platform supports for BYOC warehouses.

FeatureAWSGoogle CloudAzure
Multi-AZ high availability✓✓—
Encryption key (TDE and EBS)✓ (Custom Infrastructure only)Coming soonComing soon
Resource tags✓✓✓

Custom tags​

When you create a BYOC warehouse, you can add custom tags to help organize and identify the cloud resources that VeloDB Cloud creates in your cloud account. Tags specified during warehouse creation are applied to the warehouse and its clusters.

After the warehouse is created, you can view, add, or update tags from Warehouse Settings.

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.

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 Precautions. If you are unsure which resources are safe to remove, contact VeloDB Cloud Support before deleting anything.

Supported Regions and Availability Zones​

For the AWS, Google Cloud, and Azure regions where a BYOC warehouse can be deployed, see Supported Regions.