Getting Started with ELB in Six Steps

Preparations

Establish a Huawei account, complete real-name verification, and ensure the account has an adequate balance to buy the necessary resources.

Creating ECSs

Create two ECSs on the ECS console.

Deploying Your Application

Deploy your workloads on the two ECSs.

Creating a Load Balancer

Create a load balancer on the ELB console.

Adding a Listener

Add a listener to the created load balancer.

Verify Load Balancing

Verify that the load balancer can route requests across the two ECSs.

Learn More

Getting Started in 10 Minutes

ELB Overview

Creating a Load Balancer

Configuring Access Logging

ELB Overview

Creating a Load Balancer

Configuring Access Logging

Best Practices

Using ELB to Redirect HTTP Requests to an HTTPS Listener for Higher Service Security

HTTPS is an extension of HTTP. HTTPS encrypts data between a web server and a browser. You can use ELB to redirect HTTP requests to an HTTPS listener to improve your service security.

Configuring HTTPS at the Frontend and Backend for Access Encryption

If your sensitive service data (such as finance and government service data) requires high secure data transmission on the cloud, you can use HTTPS as the frontend and backend protocols. This allows you to use ELB to route traffic securely from clients to backend servers, ensuring high performance and O&M efficiency.

Using IP as a Backend to Route Traffic Across Backend

Dedicated load balancers support hybrid load balancing. You can add servers in the VPC where the load balancer is created, in a different VPC, or in an on-premises data center, by using their private IP addresses, to the backend server group of this load balancer. In this way, incoming traffic can be flexibly distributed to cloud servers and on-premises servers.

Using Advanced Forwarding for Application Iteration

As the business grows, you may need to upgrade your application based on user feedback. In this process, you can use advanced forwarding to redirect requests from users to both the new and old version first. When the application of the new version runs stably, direct all the requests to the new version.