Deploy in a New VPC

With the New VPC option, you run a VeloDB Cloud-provided AWS CloudFormation template in your own AWS account. The template creates a new VPC and the other AWS resources the warehouse needs. Choose this option when you do not need to reuse an existing VPC.

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 sufficient IAM permissions to create a CloudFormation stack. If you do not have 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 during warehouse configuration. See Supported Regions.

When creating a BYOC warehouse in a new VPC, you do not need to prepare a VPC or subnet. The template creates the VPC, subnets, security groups, IAM roles, S3 bucket, and VPC endpoint to VeloDB Cloud.

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 (New VPC), then click Continue.
5. On the Warehouse Configuration and Initial Cluster cards, set the fields below.

Field	Description
Warehouse Name	Required. Up to 32 characters: letters, numbers, underscores (_), and hyphens (-). The name must be unique within the organization.
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	Required. 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

Field	Description
Custom Tags	Optional. Add custom tags to the cloud resources VeloDB Cloud creates for the warehouse.
Table Name Case Sensitivity	Choose whether table names are case-sensitive. This setting cannot be changed after the warehouse is created.

Initial Cluster

Field	Description
Compute	The 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.
Cache	The cache-space limit scales with the compute size.

6. 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. Do not change the stack parameters. Select the acknowledgment checkbox, then click Create stack.
3. Wait until the stack status is CREATE_COMPLETE. If the IAM permissions are insufficient, CloudFormation reports an error.

The template creates the VPC, subnets, a NAT gateway, security groups, IAM roles, an S3 bucket, a VPC endpoint to VeloDB Cloud, and the agent instance.

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

• Deploy in an Existing VPC: run the same template into a VPC you already have.
• Custom Infrastructure: provide and manage the infrastructure yourself, and use customer-managed encryption keys.
• Warehouse Settings: manage the warehouse, including tags, after creation.