メインコンテンツまでスキップ

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 AWS CloudFormation template in your own AWS account, and it creates the remaining AWS resources in your network. Choose this option when you want to reuse an existing VPC without managing all of the supporting resources yourself.

Note:

To use Transparent Data Encryption (TDE) or customer-managed keys for EBS encryption, create the warehouse with the Custom Infrastructure option instead. The New VPC and Existing VPC template flows do not support customer-managed encryption keys.

Before you start​

Before you begin, complete the following:

  • Use an AWS account with IAM permissions to create a CloudFormation stack and the AWS resources defined in the template. If you lack these permissions, copy the CloudFormation URL and ask your AWS administrator to create the stack.
  • Select the AWS region where you want to deploy the warehouse. The VPC and selected subnets must be in this region. See Supported Regions.
  • Prepare a VPC and subnets with outbound internet access. Private subnets typically use a NAT gateway. If you use public subnets, configure a route to an internet gateway and public IP addresses as required. For a Multi-AZ warehouse, prepare three subnets in different availability zones, all in the same VPC. See Network configuration for the network requirements.

1. Start warehouse creation​

  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 (Existing VPC), then click Continue.
  5. On the Warehouse Configuration and Initial Cluster cards, set the following fields.
FieldDescription
Warehouse NameRequired. Up to 32 characters: letters, numbers, underscores (_), and hyphens (-). The name must be unique within the organization.
Cloud PlatformAWS.
RegionThe AWS region where the warehouse will run.
Core VersionThe VeloDB Core version to run. A default is preselected.
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.
  1. Click Create. In the Create BYOC Warehouse dialog, click Start.

2. Create the CloudFormation stack​

  1. The AWS CloudFormation console opens in a new tab with the settings pre-filled. If the tab does not open, click Open AWS CloudFormation on the VeloDB Cloud deployment page.
  2. Select the existing VPC and its subnets. For a Multi-AZ warehouse, select three subnets in different availability zones, all in the same VPC.
  3. Do not change the remaining parameters. Select the acknowledgment checkbox, then click Create stack.
  4. Wait until the stack status is CREATE_COMPLETE. If the IAM permissions are insufficient, CloudFormation reports an error. The template creates the security group, VPC endpoint, and agent instance in your VPC. It also creates IAM roles and an S3 bucket in your AWS account.

3. Verify deployment​

  1. Return to the VeloDB Cloud console. The deployment page progresses through Cloud Resource Configuration, Agent Deployment, and Warehouse Initialization.
  2. When initialization completes, the warehouse and its initial cluster are ready to use. Initialization typically takes 5 to 10 minutes. If it takes more than 30 minutes, contact support.

See also​