Help Center/ Cloud Adoption Framework / Cloud Adoption Framework and Practices/ Surveys/ Cloud Service Selection/ Network Service Selection
Updated on 2025-05-07 GMT+08:00
View PDF
Share

Network Service Selection

Huawei Cloud provides the following network services: VPC, Enterprise Router (ER), Enterprise Switch (ESW), Direct Connect, Virtual Private Network (VPN), Global Accelerator (GA), Elastic Load Balance (ELB), NAT Gateway, and Elastic IP (EIP). The following are the network service selection suggestions:

  • VPC peering connections are used for communication between a small number of VPCs in the same region, Cloud Connect is used for communication between VPCs in different regions, and Direct Connect or VPN is used for communication between on-premises and cloud. Enterprise Router is used to simplify the interconnection and route management between VPCs and between on-premises and cloud.
  • The cloud and on-premises subnets overlap and IP addresses are separated. Layer 2 interconnection is required to connect to enterprise switches.
  • The cloud and on-premises subnets overlap or routes between the two subnets cannot be directly enabled due to management reasons, but services need to communicate with each other. In this case, you need to use the private NAT gateway.
  • You need to build an HA system on the cloud. It is recommended that the two ECSs be deployed in the same subnet and across AZs, and be bound with a virtual IP address and keep-alive mechanism.
  • If you need to improve the cross-border resource experience of users in a specified region, you can use Cloud Connect and Global Accelerator to reduce the latency of traffic through the Huawei Cloud backbone network.
  • In low-concurrency and heavy-traffic basic Layer 4/Layer 7 load distribution scenarios, you are advised to select a shared load balancer and enable the performance assurance mode (supporting 50,000 concurrent requests). Purchase two instances and use domain name resolution to support more concurrent requests.
  • Dedicated load balancers are recommended when the number of concurrent users exceeds 100,000 and full-link HTTPS or advanced forwarding policies are required.
  • When an ECS needs to access the Internet, you are not advised to bind an EIP to the ECS. Instead, you are advised to configure a public network NAT gateway to use SNAT for flexible management.
  • If services need to be provided for the public network, you are advised to bind the public IP address to the ELB or NAT gateway instead of the ECS for flexible expansion and control adjustment.
  • Unless otherwise specified, you are advised to use the default dynamic BGP for the EIP link type.
Parent topic: Cloud Service Selection