Create an AWS BYOC Warehouse with Terraform
Use Terraform to create an advanced AWS BYOC warehouse when you want the deployment and its AWS dependencies to be reproducible and version controlled.
Terraform provider v1.1.10 or later supports advanced AWS BYOC setup. It does not support guided/template BYOC setup, Google Cloud BYOC, or Azure BYOC.
Choose a workflow
| Scenario | Documentation |
|---|---|
| Terraform should create the AWS infrastructure and VeloDB Cloud warehouse | Use the AWS BYOC module. Its documentation defines the required AWS permissions, inputs, outputs, and example configuration. |
| You have already prepared custom AWS infrastructure | Use the velodb_byoc_credential, velodb_byoc_network, and velodb_warehouse resources in the VeloDB provider documentation. |
Before you choose a workflow, review the AWS BYOC deployment options. Collect the required bucket name, role ARNs, security group ID, subnet IDs, and Availability Zones. Store the warehouse administrator password in an approved secrets manager or CI/CD secret store.
Review the Terraform plan before applying it. An AWS BYOC configuration can create billable networking, storage, compute, and security resources in your AWS account in addition to the VeloDB Cloud warehouse.
After the operation completes, verify that the warehouse and initial cluster have the Running status. Also verify the expected resources in your AWS account. Do not modify VeloDB Cloud-managed AWS resources directly. See Avoid direct changes to managed cloud resources.