Skip to main content

​
Introduction

ClickPipes is a managed integration platform that makes ingesting data from a diverse set of sources as simple as clicking a few buttons. Designed for the most demanding workloads, ClickPipes’s robust and scalable architecture ensures consistent performance and reliability. ClickPipes can be used for long-term streaming needs or one-time data loading job. ClickPipes can be deployed and managed manually using the ClickPipes UI, as well as programmatically using OpenAPI and Terraform.

​
Supported data sources

More connectors will get added to ClickPipes, you can find out more by contacting us.

​
List of Static IPs

The following tables list the static NAT IPs that ClickPipes uses to connect to your external services. Add the IPs for the ClickPipes region that serves your ClickHouse Cloud service to your IP allow list. In the case of object storage pipes you should also add the ClickHouse cluster IPs to your IP allow list. Services in the Google Cloud regions listed in the Google Cloud table below use those Google Cloud IPs only if the service did not contain pre-existing ClickPipes prior to June 15th, 2026. Services in those regions with pre-existing ClickPipes prior to June 15th, 2026 continue to use the default region IPs listed below. For other services, ClickPipes traffic will originate from a default region based on your service’s location:
  • eu-central-1: For all EU regions not explicitly listed, plus Azure EU regions and Google Cloud EU services with pre-existing ClickPipes prior to June 15th, 2026.
  • eu-west-1: For all services in AWS eu-west-1 created on or after 20 Jan 2026 (services created before this date use eu-central-1 IPs).
  • us-east-1: For all services in AWS us-east-1.
  • ap-south-1: For services in AWS ap-south-1 created on or after 25 Jun 2025 (services created before this date use us-east-2 IPs).
  • ap-northeast-2: For services in AWS ap-northeast-2 created on or after 14 Nov 2025 (services created before this date use us-east-2 IPs).
  • af-south-1: For services in AWS af-south-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • ap-east-1: For services in AWS ap-east-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • ap-northeast-1: For services in AWS ap-northeast-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • ap-southeast-1: For services in AWS ap-southeast-1 created on or after 18 Mar 2026 (services created before this date use us-east-2 IPs).
  • ap-southeast-2: For services in AWS ap-southeast-2 created on or after 25 Jun 2025 (services created before this date use us-east-2 IPs).
  • ap-southeast-3: For services in AWS ap-southeast-3 created on or after 6 Mar 2026 (services created before this date use us-east-2 IPs).
  • ca-central-1: For services in AWS ca-central-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • eu-north-1: For services in AWS eu-north-1 created on or after 15 Apr 2026 (services created before this date use eu-central-1 IPs).
  • eu-west-2: For services in AWS eu-west-2 created on or after 15 Apr 2026 (services created before this date use eu-central-1 IPs).
  • il-central-1: For services in AWS il-central-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • mx-central-1: For services in AWS mx-central-1 created on or after 19 May 2026 (services created before this date use us-east-2 IPs).
  • sa-east-1: For services in AWS sa-east-1 created on or after 15 Apr 2026 (services created before this date use us-east-2 IPs).
  • us-west-2: For services in AWS us-west-2 created on or after 24 Jun 2025 (services created before this date use us-east-2 IPs).
  • us-east-2: For all other regions that do not match a rule above, including Azure regions and Google Cloud services with pre-existing ClickPipes prior to June 15th, 2026.

​
AWS static NAT IPs

​
Google Cloud static NAT IPs

​
Adjusting ClickHouse settings

ClickHouse Cloud provides sensible defaults for most of the use cases. However, if you need to adjust some ClickHouse settings for the ClickPipes destination tables, a dedicated role for ClickPipes is the most flexible solution. Steps:
  1. create a custom role CREATE ROLE my_clickpipes_role SETTINGS .... See CREATE ROLE syntax for details.
  2. add the custom role to ClickPipes user on step Details and Settings during the ClickPipes creation.

​
Adjusting ClickPipes advanced settings

ClickPipes provides sensible defaults that cover the requirements of most use cases. If your use case requires additional fine-tuning, you can adjust the following settings:

​
Object storage ClickPipes

​
Streaming ClickPipes

​
Error reporting

ClickPipes will store errors in two separate tables depending on the type of error encountered during the ingestion process.
This does not currently apply to CDC pipes (Postgres, MySQL, and MongoDB), for which operational and error logging are available directly in the ClickHouse Cloud console.

​
Record errors

ClickPipes will create a table next to your destination table with the postfix <destination_table_name>_clickpipes_error. This table will contain any errors from malformed data or mismatched schema and will include the entirety of the invalid message. This table has a TTL of 7 days.

​
System errors

Errors related to the operation of the ClickPipe will be stored in the system.clickpipes_log table. This will store all other errors related to the operation of your ClickPipe (network, connectivity, etc.). This table has a TTL of 7 days. If ClickPipes can’t connect to a data source after 15 min or to a destination after 1 hr, the ClickPipes instance stops and stores an appropriate message in the system error table (provided the ClickHouse instance is available).

​
Monitoring

In addition to in-console monitoring, ClickPipes exposes metrics to a Prometheus-compatible endpoint for scraping. These metrics are published with other ClickHouse Cloud service metrics, and allow you to integrate ClickPipes monitoring with your existing observability stack (e.g., Grafana, Datadog). See Monitoring ClickPipes for the full list of available metrics.

​
FAQ

  • What is ClickPipes? ClickPipes is a ClickHouse Cloud feature that makes it easy for you to connect your ClickHouse services to external data sources, specifically Kafka. With ClickPipes for Kafka, you can easily continuously load data into ClickHouse, making it available for real-time analytics.
  • Does ClickPipes support data transformation? Yes, ClickPipes supports basic data transformation by exposing the DDL creation. You can then apply more advanced transformations to the data as it is loaded into its destination table in a ClickHouse Cloud service leveraging ClickHouse’s materialized views feature.
  • Does using ClickPipes incur an additional cost? ClickPipes is billed on two dimensions: Ingested Data and Compute. The full details of the pricing are available on this page. Running ClickPipes might also generate an indirect compute and storage cost on the destination ClickHouse Cloud service similar to any ingest workload.
  • Is there a way to handle errors or failures when using ClickPipes for Kafka? Yes, ClickPipes for Kafka will automatically retry in the event of failures when consuming data from Kafka for any operational issue including network issues, connectivity issues, etc. In the event of malformed data or invalid schema, ClickPipes will store the record in the record_error table and continue processing.
Last modified on July 3, 2026