Adding Routing Policy

Last updated: 2021-05-31 17:01:27


    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, please see Configuring ACL Policy.


    Up to 5 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 access, the SASL_PLAINTEXT access mode cannot be selected when other routes are created.


    1. Log in to the CKafka console.
    2. Click Instance List on the left sidebar and click the ID/Name of the target instance to enter the basic information page.
    3. On the instance basic information page, click Add a routing policy in the Access Mode module.
    4. Select the route type and access mode in the pop-up window (click the tabs below to view corresponding descriptions):

      Operation scenario: when purchasing an instance, if you select VPC and choose 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 VPC by configuring the access mode.
      Suggestion: to ensure security, this access mode provides user management and ACL policy configuration to manage user access permission. Please configure as appropriate.


      The VPC access address provided in the console (such as represents the communication address used to obtain the backend service. There may be multiple ports in a real access address. Please open all ports after 9092 to the internet on your server, so that the service can be accessed normally.

    5. Click Submit to add the routing policy.