How to create BYOC Warehouse on AWS
Preparations
Since resources in BYOC mode are deployed in your cloud account, you need to do some preparatory work before using to ensure smooth resource configuration and management:
- Prepare an IAM user and authorize it
- Prepare a VPC and subnet
- Learn about Resource Orchestration and Resource Stack
Create a BYOC Warehouse on AWS
Create warehouse configuration
On the warehouse creation guide page or the warehouse list in the upper left corner, click New Warehouse to enter the warehouse configuration page and fill in the form to create it.
| Parameter | Description |
|---|---|
| Warehouse Name | Required. Unique within the organization, no more than 32 characters in length, supports English letters, Chinese, numbers, -, _, and the combination of them. |
| Warehouse Mode | Select BYOC |
| Cloud Platform | Select AWS |
| Region | Select the region where you want to deploy your data warehouse. Because the remote communication network architecture is complex and the delay is large, it is recommended to choose the same region as your application system/client. Currently, VeloDB Cloud already supports multiple regions of the cloud platform, and will continue to support more regions based on customer needs. |
| Core Version | VeloDB Core 2.0 and the later versions support the separation of storage and computing. Storage is billed based on actual usage, and there is no need to pre-configure storage space. |
| VPC | When you create a new BYOC warehouse for the first time, the "New VPC" is selected by default. The subsequent steps will guide you to select the VPC in the cloud environment to complete the new warehouse creation. If you have created a BYOC warehouse in a VPC before, you can directly select this VPC and create a new warehouse. |
This table lists the AWS Regions and Availability Zones where VeloDB Cloud BYOC Warehouse can be deployed, along with the associated Availability Zone IDs. You will need this information to choose an available subnet when setting up AWS CloudFormation.
| Cloud Platform | Region Name | Region ID | Availability Zone ID |
|---|---|---|---|
| AWS | US East (N. Virginia) | us-east-1 | use1-az2 |
| AWS | US West (Oregon) | us-west-2 | usw2-az1 |
| AWS | Europe (Ireland) | eu-west-1 | euw1-az1 |
| AWS | Asia Pacific (Singapore) | ap-southeast-1 | apse1-az1 |
| AWS | Asia Pacific (Hong Kong) | ap-east-1 | ape1-az1 |
Click Next to proceed to the next step.
AWS preparation
Before officially creating, please refer to the document to complete the following preparation:
- Prepare an IAM user and authorize it
- Prepare a VPC and subnet
- Learn about Resource Orchestration and Resource Stack
Click Done to proceed to the next step.
Cloud resource configuration process
VeloDB Cloud will use Amazon Web Services' resource orchestration service to complete the deployment of private warehouses within the user's VPC. In the resource orchestration service, select the VPC and subnet where you want to deploy the BYOC warehouse, click Create, wait for the resource stack to run, and complete the deployment.
Fill in the Stack name, select the created VPC and Subnets.
Check "I acknowledge that AWS CloudFormation might create IAM resources with custom names."
Click Create stack.
Warehouse initialization
The system will initialize the warehouse, which takes about 5-10 minutes. If the warehouse initialization takes more than 30 minutes, or other situations that cannot be continued, please Get Help.
Create a new cluster
On the new cluster page or cluster overview page, click Create a new cluster to enter the cluster configuration page. For detailed operations, please refer to Create a new cluster.
Open public network connection and access
After the warehouse is created, if you need to connect to the warehouse on the public network, access the WebUI, etc., you need to bind the public IP address and set up a security group on AWS
Notice: Please use an AWS user with permissions to perform the operation or ask the administrator to help you complete the following operations.
Allocate Elastic IP
1. Create internet gateway
Enter VPC Console (opens in a new tab)
Click Virtual private cloud > Internet gateways > Create Internet gateway
Input Name tag, Click Create internet gateway.
Enter the Internet gateway, Click Actions > Attach to VPC
Select the VPC where your BYOC warehouse is in. Click Attach internet gateway.
2. Copy Master Private IP
Go to VeloDB Cloud (opens in a new tab), Click Connect and copy Master IP.
Enter EC2 Console (opens in a new tab), Search the IP above.
Enter the instance and confirm VPC.
3. Allocate Elastic IP
Enter AWS Instance Console (opens in a new tab), Click Network & Security > Elasitc IPs > Allocate Elastic IP address.
Select Amazon's pool of IPv4 addresses, Select us-east-1 for Netowrk border group, Click Allocate.
Click Associate this Elastic IP address.
Select Instance for Resource type, Select Instance and Private IP address above. Click Associate.
Set up security group
Enter AWS EC2 Console (opens in a new tab) , click Network & Security > Security Group on the left, and click Create security group.
Input Security group name, Description, Select VPC
Add inbound rules: Select Custome TCP fro type, Input 8080,8088,9030 for Port, Select Custom for Source, Input public IP that you want to connect to the VeloDB warehouse.
Click Create security group.
Enter AWS EC2 Console (opens in a new tab), Enter instance details of Master IP.
Search the security group. Click Add security group. Click Save.
Modify the routing table
Enter VPC details. Click Main route table.
Enter Route Table details. Click Edit routes.
Click Add route. Input 0.0.0.0/0. Select Internet Gateway and gateway id. Click Save Changes.
Return to the VeloDB Cloud connection page and click the Master IP public network refresh icon.
At this point, you can access the WebUI and connect to the warehouse through the public network.
Warehouse Usage
For warehouse usage operations and if you need to delete a warehouse, please refer to the document Warehouse Usage.