ClickHouse · Blargian · Dec 1, 2025 · Nov 25, 2025 · Nov 28, 2025
@@ -8,7 +8,7 @@ doc_type: 'guide'
 ---
 
 import Image from '@theme/IdealImage';
-import secure_s3 from '@site/static/images/cloud/security/secures3.jpg';
+import secure_s3 from '@site/static/images/cloud/security/secures3.png';
 import s3_info from '@site/static/images/cloud/security/secures3_arn.png';
 import s3_output from '@site/static/images/cloud/security/secures3_output.jpg';
 
@@ -18,7 +18,7 @@ This article demonstrates how ClickHouse Cloud customers can leverage role-based
 
 Before diving into the setup for secure S3 access, it is important to understand how this works. Below is an overview of how ClickHouse services can access private S3 buckets by assuming into a role within customers' AWS account.
 
-<Image img={secure_s3} size="md" alt="Overview of Secure S3 Access with ClickHouse"/>
+<Image img={secure_s3} size="lg" alt="Overview of Secure S3 Access with ClickHouse"/>
 
 This approach allows customers to manage all access to their S3 buckets in a single place (the IAM policy of the assumed-role) without having to go through all of their bucket policies to add or remove access.
 

@@ -18,13 +18,13 @@ import self_managed_06 from '@site/static/images/integrations/migration/self-man
 
 # Migrating between self-managed ClickHouse and ClickHouse Cloud
 
-<Image img={self_managed_01} size='md' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_01} size='lg' alt='Migrating Self-managed ClickHouse'/>
 
 This guide will show how to migrate from a self-managed ClickHouse server to ClickHouse Cloud, and also how to migrate between ClickHouse Cloud services. The [`remoteSecure`](/sql-reference/table-functions/remote) function is used in `SELECT` and `INSERT` queries to allow access to remote ClickHouse servers, which makes migrating tables as simple as writing an `INSERT INTO` query with an embedded `SELECT`.
 
 ## Migrating from Self-managed ClickHouse to ClickHouse Cloud {#migrating-from-self-managed-clickhouse-to-clickhouse-cloud}
 
-<Image img={self_managed_02} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_02} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 :::note
 Regardless of if your source table is sharded and/or replicated, on ClickHouse Cloud you just create a destination table (you can leave out the Engine parameter for this table, it will be automatically a ReplicatedMergeTree table),
@@ -85,7 +85,7 @@ CREATE TABLE db.table ...
 
 - Use the `remoteSecure` function to pull the data from the self-managed source
 
-<Image img={self_managed_03} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_03} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 ```sql
 INSERT INTO db.table SELECT * FROM
@@ -98,7 +98,7 @@ If the source system is not available from outside networks then you can push th
 
 - Use the `remoteSecure` function to push the data to the ClickHouse Cloud service
 
-<Image img={self_managed_04} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_04} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 :::tip Add the remote system to your ClickHouse Cloud service IP Access List
 In order for the `remoteSecure` function to connect to your ClickHouse Cloud service the IP Address of the remote system will need to be allowed by the IP Access List.  Expand **Manage your IP Access List** below this tip for more information.
@@ -114,15 +114,15 @@ remoteSecure('HOSTNAME.clickhouse.cloud:9440', 'db.table',
 
 ## Migrating between ClickHouse Cloud services {#migrating-between-clickhouse-cloud-services}
 
-<Image img={self_managed_05} size='lg' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_05} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 Some example uses for migrating data between ClickHouse Cloud services:
 - Migrating data from a restored backup
 - Copying data from a development service to a staging service (or staging to production)
 
 In this example there are two ClickHouse Cloud services, and they will be referred to as *source* and *destination*.  The data will be pulled from the source to the destination. Although you could push if you like, pulling is shown as it uses a read-only user.
 
-<Image img={self_managed_06} size='lg' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={self_managed_06} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 There are a few steps in the migration:
 1. Identify one ClickHouse Cloud service to be the *source*, and the other as the *destination*

@@ -19,7 +19,7 @@ import ch_local_04 from '@site/static/images/integrations/migration/ch-local-04.
 
 # Migrating to ClickHouse using clickhouse-local
 
-<Image img={ch_local_01} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={ch_local_01} size='lg' alt='Migrating Self-managed ClickHouse'/>
 
 You can use ClickHouse, or to be more specific,[`clickhouse-local`](/operations/utilities/clickhouse-local.md)
 as an ETL tool for migrating data from your current database system to ClickHouse Cloud, as long as for your current database system there is either a
@@ -33,7 +33,7 @@ For all other popular database systems, there is JDBC driver or ODBC driver avai
 
 ## What is clickhouse-local? {#what-is-clickhouse-local}
 
-<Image img={ch_local_02} size='lg' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={ch_local_02} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 Typically, ClickHouse is run in the form of a cluster, where several instances of the ClickHouse database engine are running in a distributed fashion on different servers.
 
@@ -92,7 +92,7 @@ In order for the `remoteSecure` function to connect to your ClickHouse Cloud ser
 We will use the [integration table engine](/engines/table-engines/integrations/mysql/) (created on-the-fly by the [mysql table function](/sql-reference/table-functions/mysql/)) for reading data from the source MySQL database and we will use the [remoteSecure table function](/sql-reference/table-functions/remote/)
 for writing the data into a destination table on your ClickHouse cloud service.
 
-<Image img={ch_local_03} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={ch_local_03} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 ### On the destination ClickHouse Cloud service: {#on-the-destination-clickhouse-cloud-service}
 
@@ -133,7 +133,7 @@ No data is stored locally on the `clickhouse-local` host machine. Instead, the d
 We will use the [JDBC integration table engine](/engines/table-engines/integrations/jdbc.md) (created on-the-fly by the [jdbc table function](/sql-reference/table-functions/jdbc.md)) together with the [ClickHouse JDBC Bridge](https://github.com/ClickHouse/clickhouse-jdbc-bridge) and the MySQL JDBC driver for reading data from the source MySQL database and we will use the [remoteSecure table function](/sql-reference/table-functions/remote.md)
 for writing the data into a destination table on your ClickHouse cloud service.
 
-<Image img={ch_local_04} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={ch_local_04} size='lg' alt='Migrating Self-managed ClickHouse'  />
 
 ### On the destination ClickHouse Cloud service: {#on-the-destination-clickhouse-cloud-service-1}
 

@@ -3,21 +3,19 @@ sidebar_label: 'Using a third-party ETL tool'
 keywords: ['clickhouse', 'migrate', 'migration', 'migrating', 'data', 'etl', 'elt', 'clickhouse-local', 'clickhouse-client']
 slug: /cloud/migration/etl-tool-to-clickhouse
 title: 'Using a third-party ETL Tool'
-description: 'Page describing how to use a 3rd-party ETL tool with ClickHouse'
+description: 'Page describing how to use a third-party ETL tool with ClickHouse'
 doc_type: 'guide'
 ---
 
 import Image from '@theme/IdealImage';
 import third_party_01 from '@site/static/images/integrations/migration/third-party-01.png';
 
-# Using a 3rd-party ETL Tool
-
-<Image img={third_party_01} size='sm' alt='Migrating Self-managed ClickHouse' background='white' />
-
 A great option for moving data from an external data source into ClickHouse is to use one of the many popular ETL and ELT. We have docs that cover the following:
 
 - [Airbyte](/integrations/data-ingestion/etl-tools/airbyte-and-clickhouse.md)
 - [dbt](/integrations/data-ingestion/etl-tools/dbt/index.md)
 - [Vector](/integrations/data-ingestion/etl-tools/vector-to-clickhouse.md)
 
 But there are many other ETL/ELT tools that integrate with ClickHouse, so check your favorite tool's documentation for details.
+
+<Image img={third_party_01} size='lg' alt='Migrating Self-managed ClickHouse'/>
@@ -11,7 +11,7 @@ import object_storage_01 from '@site/static/images/integrations/migration/object
 
 # Move data from cloud object storage to ClickHouse Cloud
 
-<Image img={object_storage_01} size='md' alt='Migrating Self-managed ClickHouse' background='white' />
+<Image img={object_storage_01} size='md' alt='Migrating Self-managed ClickHouse'/>
 
 If you use a Cloud Object Storage as a data lake and wish to import this data into ClickHouse Cloud,
 or if your current database system is able to directly offload data into a Cloud Object Storage, then you can use one of the

@@ -10,7 +10,7 @@ import Image from '@theme/IdealImage';
 
 [Amazon Redshift](https://aws.amazon.com/redshift/) is a popular cloud data warehousing solution that is part of the Amazon Web Services offerings. This guide presents different approaches to migrating data from a Redshift instance to ClickHouse. We will cover three options:
 
-<Image img={redshiftToClickhouse} size="md" alt="Redshift to ClickHouse Migration Options" background="white"/>
+<Image img={redshiftToClickhouse} size="md" alt="Redshift to ClickHouse Migration Options"/>
 
 From the ClickHouse instance standpoint, you can either:
 
@@ -28,7 +28,7 @@ We used Redshift as a data source in this tutorial. However, the migration appro
 
 In the push scenario, the idea is to leverage a third-party tool or service (either custom code or an [ETL/ELT](https://en.wikipedia.org/wiki/Extract,_transform,_load#ETL_vs._ELT)) to send your data to your ClickHouse instance. For example, you can use a software like [Airbyte](https://www.airbyte.com/) to move data between your Redshift instance (as a source) and ClickHouse as a destination ([see our integration guide for Airbyte](/integrations/data-ingestion/etl-tools/airbyte-and-clickhouse.md))
 
-<Image img={push} size="md" alt="PUSH Redshift to ClickHouse" background="white"/>
+<Image img={push} size="md" alt="PUSH Redshift to ClickHouse"/>
 
 ### Pros {#pros}
 
@@ -45,7 +45,7 @@ In the push scenario, the idea is to leverage a third-party tool or service (eit
 
 In the pull scenario, the idea is to leverage the ClickHouse JDBC Bridge to connect to a Redshift cluster directly from a ClickHouse instance and perform `INSERT INTO ... SELECT` queries:
 
-<Image img={pull} size="md" alt="PULL from Redshift to ClickHouse" background="white"/>
+<Image img={pull} size="md" alt="PULL from Redshift to ClickHouse"/>
 
 ### Pros {#pros-1}
 
@@ -177,7 +177,7 @@ Ok.
 
 In this scenario, we export data to S3 in an intermediary pivot format and, in a second step, load the data from S3 into ClickHouse.
 
-<Image img={pivot} size="md" alt="PIVOT from Redshift using S3" background="white"/>
+<Image img={pivot} size="md" alt="PIVOT from Redshift using S3"/>
 
 ### Pros {#pros-2}