Overview
This document describes how to implement mutual access between the resources in your current VPC and TDMQ for Apache Pulsar. Therefore, it can be ensured that the deployed producer/consumer clients can properly communicate with TDMQ for Apache Pulsar.
Prerequisites
You have purchased CVM or TKE resources and configured a VPC.
Directions
1. Log in to the TDMQ for Apache Pulsar console. Enter the Cluster Managent page, and click the ID of the target cluster to enter the basic information page. 2. Select the Access Point tab, and click Create. In the new VPC access point dialog box, select the VPC and subnet, and fill in the remarks.
VPC: Select the VPC network where your deployed producer or consumer resides.
Subnet: Select the subnet according to your IP allocation method.
3. Click Submit to complete the access to the VPC network.
4. Configure a security group policy. Ensure that the security group hosting the test program allows traffic through on TCP ports 6000-7000.
Note
You can copy the access point address from the address bar within the access point list. For detailed information, see SDK Overview. Public Network Access
Currently, only the professional edition supports creating public network access points. Unless necessary, recommend you use VPC internal network access.
Operation Steps
1. Log in to the TDMQ for Apache Pulsar console, enter the cluster management page, click the "ID" of the target cluster, and enter the basic information page. 2. Select the Access Point tab, click Create, and select Public Network for the routing type.
3. Click Submit to complete public network access.
4. Operation list. Click security policy configuration to configure the IP list to be allowed.
Instructions
1. Public network access point. A cluster can only create one.
2. If you do not configure a security policy, default to all deny. Display 127.0.0.1 on the interface.
3. The number of security policies cannot exceed 50.
4. Supports configuration of subnet ranges: /24 ~ /32.
Billing Information
Public network bandwidth cost. Currently only support annual and monthly billing mode.
|
| Beijing, Guangzhou, Shenzhen Finance, Shanghai, Nanjing, Chengdu, Chongqing, Qingyuan | Hong Kong (China), Taipei (China), Silicon Valley, Virginia, São Paulo | Singapore, Frankfurt | Bangkok, Tokyo, Seoul | Shanghai Auto-Driving Zone |
1Mbps | 3.150 | 4.110 | 3.151 | 3.425 | 4.726 |
2Mbps | 6.301 | 8.219 | 6.301 | 6.849 | 9.452 |
3Mbps | 9.726 | 12.329 | 9.452 | 10.274 | 14.589 |
4Mbps | 13.151 | 16.438 | 12.603 | 13.699 | 19.726 |
5Mbps | 17.123 | 20.548 | 15.753 | 17.123 | 25.685 |
6 Mbps or higher (n is the configured bandwidth limit) | 17.123+ 10.959 ×(n - 5) | 20.548+ 13.699 ×(n - 5) | 15.753+ 10.959 ×(n - 5) | 17.123+ 10.959 ×(n - 5) | 25.685+ 16.438 ×(n - 5) |