Skip to main content

Create a BYOC Warehouse on GCP

On Google Cloud, VeloDB Cloud deploys the warehouse with a VeloDB-provided command that you run in your own Google Cloud project through Google Cloud Shell. When you start creating the warehouse, you choose the network option:

  • BYOC (New VPC): the command creates a new VPC and subnet along with the other resources the warehouse needs. You do not need an existing VPC.
  • BYOC (Existing VPC): the command deploys into a VPC and subnet you already have, such as one from an earlier BYOC warehouse.

The Custom Infrastructure option is available only on AWS.

Prerequisites​

Because you run the command yourself in your own Google Cloud account, complete this preparation before you begin:

  • A Google Cloud account with sufficient IAM permissions to create the required resources. If you lack these permissions, you can copy the command and send it to your Google Cloud administrator.
  • For Existing VPC, a VPC and subnet in the target region. Note the VPC name and subnet name, because you pass them to the command.
  1. Log in to the VeloDB Cloud console.
  2. In the upper-left corner, click the organization name to open the Organization Overview page.
  3. Click Create New Warehouse. Alternatively, you can click All Warehouses in the upper-left corner and then click Create New Warehouse.
  4. Select BYOC, select Google Cloud, then complete the warehouse configuration.

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

Steps​

The steps are the same for both options. Your choice of New VPC or Existing VPC only changes two things: the prerequisites above, and the command parameters in step 7.

  1. Log in to the VeloDB Cloud console.

  2. In the upper-left corner, click All Warehouses, then click Create New Warehouse. Alternatively, open the Organization Overview page and click Create New Warehouse.

  3. Select BYOC (New VPC) or BYOC (Existing VPC), then click Continue.

  4. On the Warehouse Configuration and Initial Cluster cards, set the fields below.

    FieldDescription
    Warehouse NameRequired. Up to 32 characters: letters, numbers, underscores (_), and hyphens (-). The name must be unique within the organization.
    Warehouse ModeSelect BYOC.
    Cloud PlatformSelect GCP.
    RegionSelect the region where the warehouse runs. To reduce latency, choose the same region as your application or client. If your region is not listed, get help to request it.
    Core VersionSelect the VeloDB Core version. Version 2.0 and later separate storage and compute, and storage is billed by actual usage with nothing to pre-provision.
    Admin PasswordRequired. The password for the default admin user. Use at least 8 characters, including at least three of: uppercase letters, lowercase letters, numbers, and special characters. You can reset it later from the warehouse settings page.

    Advanced Settings

    FieldDescription
    Custom TagsOptional. Add custom tags to the cloud resources VeloDB Cloud creates for the warehouse.
    Table Name Case SensitivityChoose whether table names are case-sensitive. This setting cannot be changed after the warehouse is created.

    Initial Cluster

    FieldDescription
    ComputeThe compute size of the warehouse's first cluster. The default range is 4 to 1024 vCPU per cluster at a fixed 1:8 vCPU-to-memory ratio. To raise this quota, get help.
    CacheThe cache-space limit scales with the compute size.

  5. Click Create. In the Create BYOC Warehouse dialog, review the notes, then click Start.

  6. Google Cloud Shell opens in a new tab. If the tab does not open, click Open Google Cloud Console on the deployment page.

  7. On the VeloDB Cloud deployment page, copy the command. In Cloud Shell, set the active project to the Google Cloud project where the warehouse resources should be created, using the project selector in the Cloud Shell toolbar or by running gcloud config set project <PROJECT_ID>. Then paste and run the command.

    • For New VPC, run the command as-is. It already targets the warehouse region you selected in VeloDB Cloud and creates the VPC and subnet in that region, so do not change the region.
    • For Existing VPC, set the active project to the one that contains the VPC and subnet you prepared, and pass their names to the command:
    ParameterDescription
    VPC nameThe name of the VPC to deploy into.
    Subnet nameThe name of the subnet to deploy into. The subnet is a regional resource and must be in the same region as the warehouse region you selected in VeloDB Cloud, otherwise the deployment fails and the creation flow stalls.
    Zone IDThe availability zone where the warehouse runs (optional). It must be within the warehouse region.

    gcp cloudshell

  8. Wait for the command to finish. If your IAM permissions are insufficient, the command reports an error.

  9. Return to the VeloDB Cloud console. The deployment page shows progress through Cloud Resource Configuration, Agent Deployment, and Warehouse Initialization. This usually takes 5 to 10 minutes. If it takes more than 30 minutes, or you hit a situation you cannot resolve, get help.

  10. When the deployment finishes, the warehouse is ready to use, including its initial cluster.