Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changefeed: add tips for Private Connect to Kafka SaaS services #19945

Merged
merged 5 commits into from
Jan 9, 2025
Merged

changefeed: add tips for Private Connect to Kafka SaaS services #19945

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
bbb024a
changefeed: add tips for Private Connect to special Kafka services
grovecai Jan 9, 2025
48c3914
Update tidb-cloud/changefeed-sink-to-apache-kafka.md
hfxsd Jan 9, 2025
9e955f6
Update tidb-cloud/changefeed-sink-to-apache-kafka.md
hfxsd Jan 9, 2025
ca46d39
Update tidb-cloud/changefeed-sink-to-apache-kafka.md
grovecai Jan 9, 2025
c8192a1
Update tidb-cloud/changefeed-sink-to-apache-kafka.md
hfxsd Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tidb-cloud/changefeed-sink-to-apache-kafka.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Ensure that your TiDB cluster can connect to the Apache Kafka service. You can c

Private Connect leverages **Private Link** or **Private Service Connect** technologies from cloud providers to enable resources in your VPC to connect to services in other VPCs using private IP addresses, as if those services were hosted directly within your VPC.

Currently, TiDB Cloud supports Private Connect for generic Kafka only. It does not include special integration with MSK, Confluent Kafka, or other services.
TiDB Cloud currently supports Private Connect only for self-hosted Kafka. It does not support direct integration with MSK, Confluent Kafka, or other Kafka SaaS services. To connect to these Kafka SaaS services via Private Connect, deploy a [kafka-proxy](https://github.com/grepplabs/kafka-proxy) as an intermediary, effectively treating the service as self-hosted Kafka. For an example, refer to [Set up self-hosted Kafka Private Service Connect by Kafka-proxy in Google Cloud](/tidb-cloud/setup-self-hosted-kafka-private-service-connect.md#set-up-self-hosted-kafka-private-service-connect-by-kafka-proxy). This setup is similar across all Kafka SaaS services.
hfxsd marked this conversation as resolved.
Show resolved Hide resolved

- If your Apache Kafka service is hosted in AWS, follow [Set Up Self-Hosted Kafka Private Link Service in AWS](/tidb-cloud/setup-self-hosted-kafka-private-link-service.md) to ensure that the network connection is properly configured. After setup, provide the following information in the TiDB Cloud console to create the changefeed:

Expand Down
Loading