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

Deploy on Custom Infrastructure

With the Custom Infrastructure option, you provide and manage the AWS infrastructure that the warehouse runs on, including the network, IAM roles, storage, and any encryption keys. Choose this option when you must manage the underlying networking and security resources yourself, or need customer-managed encryption keys.

Note:

Custom Infrastructure is available only on AWS. It is the only deployment option that supports customer-managed encryption keys for TDE or EBS encryption.

Before you start​

Prepare the required AWS resources and register them as Cloud Resources configurations. You can register configurations before starting warehouse creation or add them inline during creation.

ConfigurationRequiredAWS resources to prepare
Credential configurationYesAn S3 bucket, a data-access IAM role, and a cross-account IAM role.
Network configurationYesA VPC, subnets, and a security group. For Multi-AZ, use three subnets in different availability zones. Add a VPC endpoint when you use private connectivity to VeloDB Cloud.
Encryption key configurationOptionalAn AWS KMS key for TDE, EBS encryption, or both.

All regional resources must be in the AWS region where you create the warehouse: the S3 bucket, VPC, subnets, security group, VPC endpoint, and any KMS key. A resource in another region can cause deployment to stall.

For the configuration procedures and required AWS policies, see Prepare Cloud Resources for an AWS BYOC Warehouse.

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, to start from warehouse navigation, click All Warehouses in the upper-left corner, then click Create New Warehouse.
  4. Select Custom Infrastructure, then click Continue.

2. Select or create cloud resources​

  1. Under Cloud Resources, set Cloud Platform to AWS and select the Region where you prepared the AWS resources. Select the region before choosing a credential or network configuration, because it limits the configurations you can use.
  2. In Credential, select an existing credential configuration, or create a new one. The credential contains the IAM roles that VeloDB Cloud uses to access your S3 bucket and deploy resources. For more information about how to create a credential configuration, see Credential configuration.
  3. In Network, select an existing network configuration, or create a new one. The configuration defines a Single-AZ or Multi-AZ layout and includes the subnet IDs, security group ID, and optional VPC endpoint ID. For more information about how to create a network configuration, see Network configuration.

Configurations that you add inline inherit the selected region. If you select an existing configuration, confirm that its resources are in the selected region.

3. Configure and create the warehouse​

  1. 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. To use an encryption key, select it from the list or choose Add encryption key configuration. For more information, see Warehouse Encryption.
  2. Review the initial cluster settings, then click Create. VeloDB Cloud validates the credential, network, and any selected encryption keys before deploying the warehouse.
  3. 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​