diff --git a/images/integrations/data-ingestion/clickpipes/postgres/pipe-connection-settings.png b/images/integrations/data-ingestion/clickpipes/postgres/pipe-connection-settings.png
new file mode 100644
index 000000000..0b596f18a
Binary files /dev/null and b/images/integrations/data-ingestion/clickpipes/postgres/pipe-connection-settings.png differ
diff --git a/images/integrations/data-ingestion/clickpipes/postgres/pipe-edit-connection.png b/images/integrations/data-ingestion/clickpipes/postgres/pipe-edit-connection.png
new file mode 100644
index 000000000..b50a6f760
Binary files /dev/null and b/images/integrations/data-ingestion/clickpipes/postgres/pipe-edit-connection.png differ
diff --git a/images/integrations/data-ingestion/clickpipes/postgres/tls-settings.png b/images/integrations/data-ingestion/clickpipes/postgres/tls-settings.png
new file mode 100644
index 000000000..7fb0f8605
Binary files /dev/null and b/images/integrations/data-ingestion/clickpipes/postgres/tls-settings.png differ
diff --git a/integrations/clickpipes/mongodb/index.mdx b/integrations/clickpipes/mongodb/index.mdx
index 4c580e014..71f482a2b 100644
--- a/integrations/clickpipes/mongodb/index.mdx
+++ b/integrations/clickpipes/mongodb/index.mdx
@@ -13,6 +13,7 @@ integration:
 import BetaBadge from "/snippets/components/BetaBadge/BetaBadge.jsx";
 
 import { Image } from "/snippets/components/Image.jsx";
+import ChangingTLSSettings from '/snippets/clickpipes/_changing_tls_settings.mdx';
 
 <BetaBadge/>
 
@@ -67,6 +68,10 @@ Make sure you're logged in to your ClickHouse Cloud account. If you don't have a
 
    <Image img="/images/integrations/data-ingestion/clickpipes/mongodb/mongodb-connection-details.png" alt="Fill in connection details" size="lg" border/>
 
+#### (Optional) Changing TLS settings {#optional-changing-tls-settings}
+
+<ChangingTLSSettings/>
+
 #### (Optional) Set up SSH Tunneling {#optional-set-up-ssh-tunneling}
 
 You can specify SSH tunneling details if your source MongoDB database isn't publicly accessible.
diff --git a/integrations/clickpipes/mysql/index.mdx b/integrations/clickpipes/mysql/index.mdx
index cce1999f3..e183fca81 100644
--- a/integrations/clickpipes/mysql/index.mdx
+++ b/integrations/clickpipes/mysql/index.mdx
@@ -13,6 +13,7 @@ integration:
 import BetaBadge from "/snippets/components/BetaBadge/BetaBadge.jsx";
 
 import { Image } from "/snippets/components/Image.jsx";
+import ChangingTLSSettings from '/snippets/clickpipes/_changing_tls_settings.mdx';
 
 <BetaBadge/>
 
@@ -72,6 +73,10 @@ Make sure you're logged in to your ClickHouse Cloud account. If you don't have a
 
    <Image img="/images/integrations/data-ingestion/clickpipes/mysql/mysql-connection-details.png" alt="Fill in connection details" size="lg" border/>
 
+#### (Optional) Changing TLS settings {#optional-changing-tls-settings}
+
+<ChangingTLSSettings/>
+
 #### (Optional) Set up SSH Tunneling {#optional-set-up-ssh-tunneling}
 
 You can specify SSH tunneling details if your source MySQL database isn't publicly accessible.
diff --git a/integrations/clickpipes/postgres/index.mdx b/integrations/clickpipes/postgres/index.mdx
index f6eafe37d..3f445e600 100644
--- a/integrations/clickpipes/postgres/index.mdx
+++ b/integrations/clickpipes/postgres/index.mdx
@@ -13,6 +13,7 @@ integration:
 import BetaBadge from "/snippets/components/BetaBadge/BetaBadge.jsx";
 
 import { Image } from "/snippets/components/Image.jsx";
+import ChangingTLSSettings from '/snippets/clickpipes/_changing_tls_settings.mdx';
 
 You can use ClickPipes to ingest data from your source Postgres database into ClickHouse Cloud. The source Postgres database can be hosted on-premises or in the cloud including Amazon RDS, Google Cloud SQL, Azure Database for Postgres, Supabase and others.
 
@@ -82,6 +83,10 @@ You can use AWS Private Link to connect to your source Postgres database if it i
 want to keep your data transfer private.
 You can follow the [setup guide to set up the connection](/integrations/clickpipes/aws-privatelink).
 
+#### (Optional) Changing TLS settings {#optional-changing-tls-settings}
+
+<ChangingTLSSettings/>
+
 #### (Optional) Setting up SSH tunneling {#optional-setting-up-ssh-tunneling}
 
 You can specify SSH tunneling details if your source Postgres database isn't publicly accessible.
diff --git a/snippets/clickpipes/_changing_tls_settings.mdx b/snippets/clickpipes/_changing_tls_settings.mdx
new file mode 100644
index 000000000..50910aee4
--- /dev/null
+++ b/snippets/clickpipes/_changing_tls_settings.mdx
@@ -0,0 +1,18 @@
+import { Image } from "/snippets/components/Image.jsx";
+
+By default, your ClickPipe will be created with TLS enabled and certificate verification. These defaults can be modified upon ClickPipe creation:
+
+<Image img="/images/integrations/data-ingestion/clickpipes/postgres/tls-settings.png" alt="TLS settings" size="lg" border/>
+
+Or edited at the _Connection settings_ section of your paused ClickPipe _Settings_ tab:
+
+<Image img="/images/integrations/data-ingestion/clickpipes/postgres/pipe-connection-settings.png" alt="Connection settings -> Edit Connection" size="lg" border/>
+
+<Image img="/images/integrations/data-ingestion/clickpipes/postgres/pipe-edit-connection.png" alt="Edit Connection" size="lg" border/>
+
+Where:
+
+- `Disable TLS` toggles TLS for the connection on or off. Turning TLS off means data is sent as plaintext over the network, potentially including secrets and sensitive data.
+- `Skip certificate verification` toggles on or off the verification of the certificate presented by the source database. Take into consideration the security implications of skipping certificate verification.
+- `TLS Host` (optional, defaults to the source _Host_) is the hostname the certificate's CN must match when certificate verification is enabled.
+- `Upload CA` can be used to provide a CA used when certificate verification is enabled.