Tencent Cloud Connect Network (CCN) supports traffic management through the policy-based routing feature. This feature takes precedence over the standard CCN multi-route table lookup process, enabling flexible management of network traffic.
Note:
Currently, the policy-based routing feature is in grayscale release. If needed, please submit a ticket. Enabling policy-based routing will incur inbound traffic processing fees for inter-VPC traffic within the same region and may increase the latency of cross-VPC access within the same region.
Policy-based routing does not take effect for load balancing traffic.
Use Limits
Resource | Default Limit | Quota Increase |
The number of policy-based routing next hop allowed per CCN | 5 | |
The number of policy-based routing matching rules allowed to be created per CCN | 100 | Cannot be increased |
How It Works
Next Hop
The next-hop feature of policy-based routing is used to precisely configure traffic forwarding paths. You can customize next-hop rules for traffic based on actual network requirements, flexibly control packet transmission directions, and ensure network traffic is forwarded along the intended path.
Matching Rule
The matching rules feature is primarily used to identify and capture cross-region network traffic, configuring corresponding next-hop forwarding policies accordingly. You can perform granular traffic matching based on conditions such as source instance ID, source IP range, and destination IP range. When traffic meets the preset conditions, the system automatically forwards it according to the configured next-hop rules. This mechanism enables differentiated routing control for various types of traffic, meeting traffic management requirements in complex network environments. Matching rules support multi-condition combination configurations, allowing you to set precise traffic matching policies according to business needs.
Create Policy-based Routing Next Hop
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. Click the next hop page and click Add.
4. In the Add Next Hop dialog box, configure the policy-based routing next hop information and then click OK.
Configuration Item | Description |
Region | Region of the next hop instance. |
Name | Name of the next hop. |
Instance type of the next hop | The next hop instance type supports VPC, Direct Connect (DC) gateways, and VPN gateways. |
ID of the next hop instance | ID of the next hop instance. |
Type of the next hop access resource | Only when the next hop instance is a VPC can this be configured, supporting High Availability Virtual IP (HAVIP) and Gateway Load Balancer (GWLB) endpoints. |
ID of the next hop access resource | Configurable only when the next hop instance is a VPC. Select the corresponding next hop resource ID. |
Description | Description of the next hop. |
View Policy-based Routing Next Hop
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. Click the Next Hop page to view the configured policy-based routing next hop information for this CCN.
Delete the Policy-based Routing Next Hop
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. On the Next Hop page, batch select the checkboxes on the left side of the rules, then click Delete to perform batch deletion. Alternatively, click Delete on the right side of a rule to delete a single rule.
Note:
If there are matching rules bound to the next hop, please delete the corresponding matching rules first, and then delete this next hop.
Create Policy-based Routing Matching Rule
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. Click the Matching Rules page, then click Add.
4. In the Add Matching Rule dialog box, configure the policy-based routing next hop information, then click OK.
Configuration Item | Description |
Priority | The priority of matching rules, with a valid range: 1-1000. The smaller the number, the higher the priority. CCN will prioritize using higher-priority rules for traffic matching. |
Source Instance Type | The source instance type of data messages supports VPC, Direct Connect (DC) gateways, and VPN gateways. |
Source Instance ID | Source instance ID of data messages. |
Source IP range | Source IP address range of data messages, supporting longest prefix match. For example: 10.0.0.0/16 matches 10.0.1.10/32. |
Destination IP range | Destination IP address range of data messages, supporting longest prefix match. For example: 10.0.0.0/16 matches 10.0.1.10/32. |
Next hop ID | Matched traffic will be forwarded to the next hop ID. |
Remarks | Remarks of the matching rule. |
View Policy-based Routing Matching Rules
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. Click the Match Rules page to view the policy-based routing next hop information configured for this CCN.
Delete Policy-based Routing Match Rules
2. In the CCN list, click the CCN ID that needs to be configured and go to the Policy-based Routing tab in the details page.
3. Click the Match Rules page, batch select the checkboxes on the left side of the rules, then click Delete to perform batch deletion. Alternatively, click Delete on the right side of a rule to delete a single rule.