clickhouse_clickpipe resource in the ClickHouse Terraform provider. This page covers provider setup and configuration examples for each supported ClickPipe type.
Provider setup
ClickPipes support is generally available from provider version v3.14.0.
If you are using an earlier version, you will need an alpha release — check the
provider changelog
for details.
Resource overview
Theclickhouse_clickpipe resource has the following top-level arguments:
| Argument | Required | Description |
|---|---|---|
name | Yes | Name for the ClickPipe. |
service_id | Yes | ID of the ClickHouse Cloud service. |
source | Yes | Source configuration (one source block per ClickPipe). |
destination | Yes | Destination configuration. |
scaling | No | Replica count and size. Defaults to 1 replica. |
field_mappings | No | Custom field mappings between source and destination columns. |
settings | No | Advanced ClickPipe settings. |
stopped | No | Set to true to create the ClickPipe in a stopped state. Defaults to false. |
id and state attributes are read-only and populated by ClickHouse Cloud after creation.
Destination
Thedestination block is shared across all source types:
database is typically needed.
Examples by ClickPipe type
Kafka
Supportedtype values: kafka, confluent, msk, azureeventhub, redpanda, warpstream.
Kafka with schema registry
Amazon Kinesis
Kinesis with IAM role
IAM role authentication requires a ClickHouse service running on AWS.Amazon S3
S3 continuous ingestion with SQS
For continuous ingestion using an SQS queue (unordered mode). See Configuring unordered mode for setup instructions.Google Cloud Storage
service_account_key must be the base64-encoded content of a GCP service account JSON key file.
Azure Blob Storage
Postgres CDC
Postgres with IAM role
IAM role authentication requires a ClickHouse service running on AWS.MySQL CDC
MongoDB CDC
BigQuery
service_account_file must be the base64-encoded content of a GCP service account JSON key file.
Scaling
All ClickPipe types support thescaling block to configure the number of replicas and their resource allocation: