This document describes how to configure a routing rule in the CKafka console to enhance network access control in public/private network transfers. For more information on public network access, see Configuring ACL Policy.
Route Type | VPC | Public Domain Name Access |
---|---|---|
Access mode |
Note:Up to five routes can be created per instance. There is only one route if the SASL_PLAINTEXT access mode is selected. For example, if the SASL_PLAINTEXT access mode is selected for the route type of public domain name access, the SASL_PLAINTEXT access mode cannot be selected when other routes are created.
Operation scenario: When purchasing an instance, if you select VPC and select a corresponding VPC environment (such as VPC A), then CKafka services (such as data production and consumption) can be accessed only from VPC A. If you subsequently find that you need to access the CKafka services in VPC A from other VPCs (such as VPC B), you can select an appropriate routing policy for VPCs by configuring the access mode.
Suggestion: To ensure security, this access mode provides user management and ACL policy configuration to manage user access permission. We recommend you configure as appropriate.
Directions:
NoteIf you select VPC access, you can specify the IP. In this way, when changing the access method, you can specify the IP to keep the IP unchanged.
NoteThe VPC access address provided in the console (such as
172.16.0.12:9092
) represents the communication address used to obtain the backend service. There may be multiple ports in a real access address. You should open all ports after 9092 to the internet on your server, so that the service can be accessed normally.
Was this page helpful?