> ## Documentation Index > Fetch the complete documentation index at: https://private-7c7dfe99-vortex-format.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > Seamlessly connect your external data sources to ClickHouse Cloud. # Integrating with ClickHouse Cloud export const Image = ({img, alt, size = "lg"}) => { const normalizedSize = ["sm", "md", "lg"].includes(size) ? size : "lg"; return

; };

Introduction

[ClickPipes](/integrations/clickpipes/home) 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](/integrations/clickpipes/programmatic-access/openapi) and [Terraform](/integrations/clickpipes/programmatic-access/terraform). ClickPipes stack

Supported data sources

| Name | Type | Status | Description | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

Azure Event Hubs | Streaming | Stable | Configure ClickPipes and start ingesting streaming data from Azure Event Hubs into ClickHouse Cloud. See the [Azure Event Hubs FAQ](/integrations/clickpipes/kafka/faq#azure-eventhubs) for guidance. | |

[Amazon Kinesis](/integrations/clickpipes/kinesis/overview) | Streaming | Stable | Configure ClickPipes and start ingesting streaming data from Amazon Kinesis into ClickHouse Cloud. | |

[GCP Pub/Sub](/integrations/clickpipes/pubsub/overview) | Streaming | Private Preview | Configure ClickPipes and start ingesting streaming data from Google Cloud Pub/Sub into ClickHouse Cloud. | |

[Amazon S3](/integrations/clickpipes/object-storage/amazon-s3/overview) | Object Storage | Stable | Configure ClickPipes to ingest large volumes of data from object storage. | |

[Google Cloud Storage](/integrations/clickpipes/object-storage/google-cloud-storage/overview) | Object Storage | Stable | Configure ClickPipes to ingest large volumes of data from object storage. | |

[Azure Blob Storage](/integrations/clickpipes/object-storage/azure-blob-storage/overview) | Object Storage | Stable | Configure ClickPipes to ingest large volumes of data from object storage. | |

[MongoDB](/integrations/clickpipes/mongodb/index) | DBMS | Private Preview | Configure ClickPipes and start ingesting data from MongoDB into ClickHouse Cloud. | More connectors will get added to ClickPipes, you can find out more by [contacting us](https://clickhouse.com/company/contact?loc=clickpipes).

AWS IAM database authentication

ClickPipes supports AWS IAM database authentication for Amazon RDS and Aurora. The configuration differs by database engine and AWS service, so choose the source setup guide that matches your database: | Database engine | AWS service | Setup guide | | --------------- | ------------- | ---------------------------------------------------------------------------------------------------------- | | PostgreSQL | Amazon RDS | [RDS for PostgreSQL](/integrations/clickpipes/postgres/source/rds#iam-authentication) | | PostgreSQL | Amazon Aurora | [Aurora PostgreSQL-Compatible Edition](/integrations/clickpipes/postgres/source/aurora#iam-authentication) | | MySQL | Amazon RDS | [RDS for MySQL](/integrations/clickpipes/mysql/source/rds#iam-authentication) | | MySQL | Amazon Aurora | [Aurora MySQL-Compatible Edition](/integrations/clickpipes/mysql/source/aurora#iam-authentication) | | MariaDB | Amazon RDS | [RDS for MariaDB](/integrations/clickpipes/mysql/source/rds-maria#iam-authentication) |

List of Static IPs

The list of ClickPipes static NAT IPs has moved to the [ClickPipes networking documentation](/integrations/clickpipes/networking/static-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](/reference/statements/create/role) syntax for details. 2. add the custom role to ClickPipes user on step `Details and Settings` during the ClickPipes creation. Assign a custom role

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

| Setting | Default value | Description | | ------------------------------------ | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Max insert bytes` | 10 GB | Number of bytes to process in a single insert batch. | | `Max file count` | 100 | Maximum number of files to process in a single insert batch. | | `Max threads` | auto(3) | [Maximum number of concurrent threads](/reference/settings/session-settings/max-threads#max_threads) for file processing. | | `Max insert threads` | 1 | [Maximum number of concurrent insert threads](/reference/settings/session-settings/max-insert#max_insert_threads) for file processing. | | `Min insert block size bytes` | 1 GB | [Minimum size of bytes in the block](/reference/settings/session-settings/min-insert#min_insert_block_size_bytes) which can be inserted into a table. | | `Max download threads` | 4 | [Maximum number of concurrent download threads](/reference/settings/session-settings/max-download#max_download_threads). | | `Object storage polling interval` | 30 s | Configures the maximum wait period before inserting data into the ClickHouse cluster. | | `Parallel distributed insert select` | 2 | [Parallel distributed insert select setting](/reference/settings/session-settings/parallel#parallel_distributed_insert_select). | | `Parallel view processing` | false | Whether to enable pushing to attached views [concurrently instead of sequentially](/reference/settings/session-settings/parallel#parallel_view_processing). | | `Use cluster function` | true | Whether to process files in parallel across multiple nodes. | Advanced settings for ClickPipes

Streaming ClickPipes

| Setting | Default value | Description | | -------------------------------- | ------------- | ------------------------------------------------------------------------------------- | | `Streaming max insert wait time` | 5 s | Configures the maximum wait period before inserting data into the ClickHouse cluster. |

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 `_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](/reference/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-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](/reference/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-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](/products/cloud/features/monitoring/prometheus) 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](/products/cloud/features/monitoring/prometheus#integrating-with-grafana), [Datadog](/products/cloud/features/monitoring/prometheus#integrating-with-datadog)). See [Monitoring ClickPipes](/integrations/clickpipes/monitoring) 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](/concepts/features/materialized-views/cascading-materialized-views). * **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](/products/cloud/reference/billing/clickpipes/index). 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.