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

Custom Infrastructure

With the Custom Infrastructure option, you provide and manage the infrastructure that the warehouse runs on, including the network, IAM roles, storage, and any encryption keys. Use this option when you manage your own networking and security, or when you need customer-managed encryption keys.

備考

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

Prerequisites​

Prepare the required AWS resources before you start. See Cloud resource preparation for details:

  • A VPC and subnets in the target region. For a Multi-AZ warehouse, prepare three subnets in different availability zones.
  • A security group, and optionally a VPC endpoint if you use private connectivity to VeloDB Cloud.
  • The IAM roles VeloDB Cloud uses to access your S3 bucket and to deploy resources (configured through a credential).
  • An S3 bucket for warehouse data.
  • Optionally, AWS KMS keys for Transparent Data Encryption (TDE) and for EBS encryption.

Steps​

  1. Sign in to the VeloDB Cloud console.

  2. At the top of the console, open the warehouse menu (All Warehouses, or the current warehouse name) and click Create New Warehouse. You can also click Create New Warehouse on the Organization Overview page. Select Custom Infrastructure, then click Continue.

  3. Cloud Resources. Provide the resources the warehouse deploys into:

    • Cloud Platform: AWS.
    • Region: the AWS region where your resources exist.
    • Credential: select an existing credential or add a new one. The credential holds the IAM roles VeloDB Cloud uses to access your S3 bucket and deploy resources.
    • Network: select an existing network configuration or add a new one. A network configuration is either Single-AZ or Multi-AZ and includes the Subnet ID (three subnet IDs from different availability zones for Multi-AZ), the Security Group ID, and an optional VPC Endpoint ID for private connectivity.

    You can also create credentials and networks in advance from the Cloud Resources page in the console. See Cloud resource preparation.

  4. Warehouse configuration. Set the warehouse name and the admin password. Under Advanced Settings, you can configure customer-managed encryption keys:

    • CMK for TDE: encrypts all warehouse data at rest using your own AWS KMS key. You can rotate this key at any time after adding it.
    • CMK for EBS: encrypts the EBS volumes on compute nodes using your AWS KMS key. This key can only be set at warehouse creation time and cannot be rotated afterward.

    To use a key, select it from the list or choose Add encryption key configuration. For more on managing these keys, see Warehouse Encryption.

    Advanced Settings also lets you add custom tags and set table-name case sensitivity.

  5. Cluster initialization. Review the initial cluster settings, then create the warehouse. VeloDB Cloud validates the credential, network, and any selected encryption keys, then deploys the warehouse. Initialization usually takes 5 to 10 minutes. If it takes more than 30 minutes, get help.

  6. When initialization completes, the warehouse is ready to use, including its initial cluster.