feat(clickpipes): document custom private DNS for AWS PrivateLink reverse private endpoints#6492
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
whites11
approved these changes
Jul 7, 2026
morsapaes
approved these changes
Jul 7, 2026
Co-authored-by: Marta Paes <marta.paes.moreira@gmail.com>
Blargian
approved these changes
Jul 7, 2026
|
Docs PR opened: ClickHouse/ClickHouse#109654 Documented ClickPipes support for custom private DNS names on AWS PrivateLink reverse private endpoints, currently in private preview. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
ClickPipes reverse private endpoints support attaching custom private DNS names (
customPrivateDnsMappings) with AWS PrivateLink, but the docs don't mention this capability. The feature is in private preview and requires a support opt-in per service.Custom private DNS does not replace AWS PrivateLink's managed private DNS provisioning — it is an addition for cases where the provider requires each consumer to manage DNS resolution in their own VPC (e.g. Confluent Cloud).
Changes
docs/integrations/data-ingestion/clickpipes/aws-privatelink.md:Custom private DNSsection (private preview badge + support opt-in note) covering: what it does, how it complements managed private DNS, supported endpoint types (VPC endpoint service, VPC resource; not MSK multi-VPC), name rules (exact + single-label wildcard, per-service uniqueness, reserved suffixes), and how to configure it via console, OpenAPI, and theclickhouse_clickpipes_reverse_private_endpoint_custom_private_dnsTerraform resource.docs/integrations/data-ingestion/clickpipes/kafka/02_schema-registries.md: linked the existing "custom private DNS mapping" phrase to the new section.Notes