Help Center>
Distributed Message Service for Kafka>
FAQs>
Connections>
Do Kafka Instances Support Cross-VPC Access?
Updated on 2022-08-11 GMT+08:00
Do Kafka Instances Support Cross-VPC Access?
Yes. You can use one of the following methods to access a Kafka instance across VPCs:
- Establish a VPC peering connection to allow two VPCs to communicate with each other. For details, see VPC Peering Connection.
- Create a cloud connection and load the VPCs that need to communicate with each other to the cloud connection. For details, see Communications Among VPCs of the Same Account.
- Use VPC Endpoint (VPCEP) to establish a cross-VPC connection. For details, see Cross-VPC Access to a Kafka Instance.
Parent topic: Connections
Connections FAQs
- How Do I Select and Configure a Security Group?
- Can I Access a Kafka Instance Over a Public Network?
- How Many Connection Addresses Does a Kafka Instance Have by Default?
- Do Kafka Instances Support Cross-Region Access?
- Do Kafka Instances Support Cross-VPC Access?
- Do Kafka Instances Support Cross-Subnet Access?
- Does DMS for Kafka Support Authentication with Kerberos?
- Does DMS for Kafka Support Password-Free Access?
- How Do I Obtain the Public Access Address After Public Access Is Enabled?
- Does DMS for Kafka Support Authentication on Clients by the Server?
- Can I Use PEM SSL Truststore When Connecting to a Kafka Instance with SASL_SSL Enabled?
- What Are the Differences Between JKS and CRT Certificates?
- Which TLS Version Does DMS for Kafka Support?
- Is There a Limit on the Number of Client Connections to a Kafka Instance?
- How Many Connections Are Allowed from Each IP Address?
- Can I Change the Private Network Addresses of a Kafka Instance?
- Is the Same SSL Certificate Used for Different Instances?
- Why Is It Not Recommended to Use a Sarama Client for Messaging?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore