CLB Instance Cross-Region Binding

Last updated: 2020-08-18 16:42:39

    Currently, a public network CLB instance supports cross-region binding of CVM. You can select the region of real servers and bind them across VPCs or regions. For cross-region binding in Mainland China, please submit a ticket for application. For cross-region binding outside Mainland China, please contact your Tencent Cloud rep.

    Cross-region CVM instance binding is currently not supported for private network CLB and classic CLB.

    Use Cases

    1. This feature can meet the needs of P2P and other gaming businesses to access the server from multiple regions. For example, if your real server cluster is deployed in Guangzhou, you can create CLB instances in Shanghai and Beijing and bind them to the same real server cluster in Guangzhou for game acceleration and traffic convergence, effectively ensuring the data transfer quality and reducing the latency.
    2. This feature can meet the needs in financial business and payment scenarios by effectively ensuring the transfer quality and consistency of data in key businesses.

    Operation Examples

    After purchasing a public network CLB instance, you can view the region attribute of the real server on the instance details page. At the time of purchase, the region attribute of the real server is the same as that of the CLB instance by default.
    If a public network CLB instance has been bound to a CVM instance in the same region, you need to unbind the CVM instance first before switching the region.

    Click Edit to modify the region and network attributes of the real server. Fees for cross-region binding will be charged daily by bandwidth. After the modification is completed, you can select a CVM instance in the corresponding backend region on the CVM instance binding page for cross-region binding. Currently, only real servers in the same region can be bound.

    • Currently, one CLB instance can be bound to CVM instances in only one region. For example, one CLB instance in Beijing can be bound to CVM instances in Beijing but cannot be bound to CVM instances in Beijing and Shanghai at the same time.
    • After you modify the region attribute of the backend CVM instance, if the new region is different from that of the CLB instance, you cannot change back to the original same-region binding.
    • Currently, it is not allowed to bind CLB instances to CVM instances across VPCs in the same region.
    • Classic network-VPC binding is supported.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback