At present, public Cloud Load Balancer (CLB) supports binding Cloud Virtual Machines (CVMs) across regions, allowing you to select CVMs from other regions and bind them across VPCs and regions. To experience this feature, for cross-region binding within the Chinese mainland, submit a ticket; for cross-region binding outside the Chinese mainland, contact us.
Note:
Private network CLB and classic CLB currently are not available for cross-region CVM instance binding.
For traditional account types, only CLB instances with shared bandwidth package as their network billing mode support cross-region binding 1.0 feature.
Scenarios
1. The cross-region binding feature meets the needs in P2P gaming scenarios where the same server is shared by players from different regions. For example, if your real server cluster is deployed in Guangzhou, you can create CLB instances in Shanghai and Beijing and bind the instances to the same real server cluster in Guangzhou to achieve game acceleration and traffic convergence, ensuring the data transfer quality and reducing the latency.
2. In financial transaction and order payment scenarios, the transfer quality and consistency of key business data can be effectively guaranteed.
Instructions
1. Log in to the Cloud Load Balancer console.
2. On the Instance Management page, click the ID of the target CLB instance.
3. On the Basic Info page, in the Real Server Module, click Cross-region Binding 1.0 followed by Configure to modify the region and network attributes of the backend Cloud Virtual Machines.
Note:
If a public Cloud Load Balancer is already bound to a Cloud Virtual Machine in the same region, you need to unbind the CVM before switching regions. For more information, please refer to Unbinding a CLB Real Server.
4. In the Modify Backend Service Configuration pop-up window, select the desired region and network from the Backend Service Region and Backend Service Network lists, then click Submit.
Note:
Currently, a Cloud Load Balancer (CLB) instance can only be bound to Cloud Virtual Machines (CVMs) in a single region. For example, a CLB instance in the Beijing region can be bound to CVM instances in the Shanghai region, but cannot be bound to those in both the Beijing and Shanghai regions simultaneously.
After modifying the backend instance service attributes, if the new region is different from the CLB region, you will be unable to revert to the original intra-region binding.
Currently, binding CLB and CVM instances across VPCs within the same region is not allowed.
Supports scenarios across Classic Network and VPC.
The bandwidth fees incurred by cross-region binding will be settled daily using peak bandwidth tiered billing. For more information, see Cross-region Binding Billing Description.
Billing description
The cross-region binding feature is implemented based on the principle of cross-region peering connections. For billing details, please refer to Billing Description.