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
- Log in to the VeloDB Cloud console.
- In the upper-left corner, click the organization name to open the Organization Overview page.
- Click Create New Warehouse. Alternatively, you can click All Warehouses in the upper-left corner and then click Create New Warehouse.
- Select BYOC (New VPC), then click Continue.
- 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 |
|---|---|
| Memory per vCPU | Select R4 for 4 GB RAM per vCPU for general-purpose workloads, or R8 for 8 GB RAM per vCPU for memory-intensive workloads. |
| Cache Storage Type | Select EBS to set the cache capacity now and expand it later, or Local NVMe SSD for high-performance cache with fixed capacity. Local NVMe SSD is currently available only for BYOC warehouses on AWS. |
| Node Size | Select the vCPU and RAM capacity for each node. The RAM capacity depends on the selected Memory per vCPU option. |
| Cache per Node | For EBS, set the cache capacity for each node. Local NVMe SSD has fixed cache capacity. |
| Number of Nodes | Set the number of nodes in the initial cluster. |
Total cluster vCPU, RAM, and cache capacity depend on the per-node configuration and the number of nodes. Use the options and ranges available in the console. To request a higher compute quota, contact support.
Local NVMe cache is cleared when the cluster resumes from Auto-suspend or a node is replaced, but is preserved during routine upgrades.
- Click Create. In the Create BYOC Warehouse dialog, click Start.
2. Create the CloudFormation stack
- 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.
- Do not change the stack parameters. Select the acknowledgment checkbox, then click Create stack.
- 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
- Return to the VeloDB Cloud console. The deployment page progresses through Cloud Resource Configuration, Agent Deployment, and Warehouse Initialization.
- 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.