Skip to main content

Deploy in an Existing VPC

With the Existing VPC option, you deploy the warehouse into a VPC and subnets you already have. You run a VeloDB-provided CloudFormation template in your own AWS account, and it creates the remaining required resources within your network. Use this option to reuse existing networking for production workloads.

note

To use Transparent Data Encryption (TDE) or a customer-managed key for EBS encryption, create the warehouse with the Custom Infrastructure option instead. This template flow does not support customer-managed encryption keys.

Prerequisites​

  • An AWS account with sufficient IAM permissions to create a CloudFormation stack. If you lack these permissions, you can copy the CloudFormation URL and send it to your AWS administrator.
  • An existing VPC and subnets in the target region. The selected VPC and subnet must have internet access (through a NAT gateway or internet gateway) to reach AWS services. See Cloud resource preparation for the network requirements.

Steps​

  1. Sign in to the VeloDB Cloud console.

  2. At the top of the console, open the warehouse menu (All Warehouses, or the current warehouse name) and click Create New Warehouse. You can also click Create New Warehouse on the Organization Overview page. Select BYOC (Existing VPC), then click Continue.

  3. On the Warehouse Configuration card, set:

    • Warehouse Name: 1 to 32 characters, using letters (case-insensitive), numbers, underscores (_), and hyphens (-).
    • Cloud Platform: AWS.
    • Region: the AWS region where the warehouse will run.
    • Core version: the VeloDB core version to run (a default is preselected).
    • Admin Password: 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.
    • Optionally open Advanced Settings to add custom tags or set table-name case sensitivity.

    On the Initial Cluster card, set the initial compute and cache for the warehouse's first cluster.

  4. Click Create. A dialog titled Create BYOC Warehouse explains that after you click Start, the AWS CloudFormation console opens in a new tab with the required settings pre-filled. Click Start.

  5. In the AWS CloudFormation console, select your existing VPC and subnet in the stack parameters, review the remaining pre-filled parameters, and create the stack. The template creates the security group, IAM roles, S3 bucket, VPC endpoint, and agent instance within your VPC. If the AWS tab does not open, use Open AWS CloudFormation on the deployment page to reopen it.

  6. Return to the VeloDB Cloud console. The deployment page tracks progress through Cloud Resource Configuration, Agent Deployment, and Warehouse Initialization. Deploying the warehouse usually takes 5 to 10 minutes. If it takes more than 30 minutes, get help.

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