Adding Routing Policy

Last updated: 2022-01-10 17:55:25

    Overview

    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.

    Note:

    • CKafka supports SASL_SSL and SASL_PLAINTEXT authentication modes. The former is supported only for Pro Edition instances.
    • 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 name access, the SASL_PLAINTEXT access mode cannot be selected when other routes are created.

    Directions

    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. Configure as appropriate.

    Directions:

    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. In the pop-up window, select VPC Network as the route type and select the access mode and network.
    5. Click Submit to add the VPC network.
      The 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 need to open all ports after 9092 to the internet on your server, so that the service can be accessed normally.