From 6087ef2ff0e8a7a09839b110efb99e7b3d5dd27f Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Tue, 2 Jun 2026 03:34:39 +0000
Subject: [PATCH] docs: document schema registry connectivity over private
 endpoints

---
 integrations/clickpipes/aws-privatelink.mdx         |  4 ++++
 integrations/clickpipes/kafka/schema-registries.mdx | 11 +++++++++++
 2 files changed, 15 insertions(+)

diff --git a/integrations/clickpipes/aws-privatelink.mdx b/integrations/clickpipes/aws-privatelink.mdx
index c988b6f7..69af79d4 100644
--- a/integrations/clickpipes/aws-privatelink.mdx
+++ b/integrations/clickpipes/aws-privatelink.mdx
@@ -27,6 +27,10 @@ data source types:
 - MySQL
 - MongoDB
 
+<Note>
+For Kafka, the [schema registry](/integrations/clickpipes/kafka/schema-registries) can be reached over the same reverse private endpoint as the brokers — it does not need to be publicly accessible — provided its hostname resolves to the endpoint's private IP addresses.
+</Note>
+
 ## Supported AWS PrivateLink endpoint types {#aws-privatelink-endpoint-types}
 
 ClickPipes reverse private endpoint can be configured with one of the following AWS PrivateLink approaches:
diff --git a/integrations/clickpipes/kafka/schema-registries.mdx b/integrations/clickpipes/kafka/schema-registries.mdx
index 211fd7ab..0345b917 100644
--- a/integrations/clickpipes/kafka/schema-registries.mdx
+++ b/integrations/clickpipes/kafka/schema-registries.mdx
@@ -30,6 +30,17 @@ To integrate with a schema registry during ClickPipes configuration, you must us
 2. Provide a complete path to the schema ID (e.g. `https://registry.example.com/schemas/ids/1000`)
 3. Provide the root schema registry URL (e.g. `https://registry.example.com`)
 
+## Network connectivity {#network-connectivity}
+
+ClickPipes connects to the schema registry over HTTPS at the URL you provide. The schema registry does not need to be publicly accessible.
+
+If your Kafka brokers are reached through a [reverse private endpoint](/integrations/clickpipes/aws-privatelink) (AWS PrivateLink or GCP Private Service Connect), the schema registry can use the same private connectivity. ClickPipes resolves the registry hostname through the reverse private endpoint's private DNS, so a registry hosted privately alongside your brokers is reachable as long as its hostname resolves to the reverse private endpoint's private IP addresses (via the endpoint's private DNS support or a custom private DNS mapping).
+
+Keep the following in mind:
+
+- The schema registry URL must use `https://`.
+- If the registry hostname resolves to a private address, it must be reachable through a reverse private endpoint selected for the ClickPipe; otherwise the connectivity check during setup will fail.
+
 ## How it works {#how-schema-registries-work}
 
 ClickPipes dynamically retrieves and applies the schema from the configured schema registry.