Create BYOC Infrastructure
Create a new BYOC Infrastructure in the organization. Returns the configuration of the newly created infrastructure
Permission
control-plane:organization:manage permission.Autorizações
Use key ID and key secret obtained in ClickHouse Cloud console: https://clickhouse.com/docs/cloud/manage/openapi
Parâmetros de caminho
ID of the requested organization.
Corpo
Region in which the BYOC infrastructure will be located
ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, ca-central-1, eu-central-1, eu-west-1, eu-west-2, il-central-1, us-east-1, us-east-2, us-west-2, us-east1, us-central1, europe-west2, europe-west4, asia-southeast1, asia-northeast1, eastus, eastus2, westus3, germanywestcentral, centralus Cloud account ID the BYOC infrastructure is configured for: AWS account ID, GCP project ID, or Azure subscription ID
"123456789012"
List of availability zone suffixes
a, b, c, d, e, f CIDR range for the ClickHouse-managed VPC. Mutually exclusive with the BYO-VPC fields (vpcId, privateSubnetIds, publicSubnetIds)
"10.0.0.0/16"
AWS only: ExternalID baked into the ClickHouse management role trust policy in your account
"ch-0a1b2c3d4e5f6789"
Azure only (required for Azure regions): Entra tenant ID of the subscription
Azure only (required for Azure regions): client ID of the service principal ClickHouse uses to manage the infrastructure
BYO-VPC only (AWS and GCP): ID or network name of the customer-provided VPC to deploy into. Requires privateSubnetIds
"vpc-0abc1234def567890"
BYO-VPC only: private subnet IDs or names (1-6 entries on AWS, exactly one on GCP)
AWS BYO-VPC only: public subnet IDs (at most 6 entries)
GCP BYO-VPC only: secondary IP range names on the subnet to use for pod IPs. Omitted: all secondary ranges are used
GCP BYO-VPC only: Shared VPC host project owning the VPC and subnet, when different from accountId
Human readable name for infrastructure