Memory
@@ -122,11 +122,11 @@ systemctl enable nginx
Creating a Load BalancerEach ECS needs an EIP for accessing the Internet and configuring the application on the ECS. The load balancer needs an EIP to access the application deployed on the ECSs over the Internet. You can determine whether to bind an EIP to the load balancer based on your requirements. For details, see Load Balancing on a Public or Private Network.
- - In the upper left corner of the page, click
 and select the desired region and project. - Hover on
 in the upper left corner to display Service List and choose Network > Elastic Load Balancing. - Click Create Elastic Load Balancer and then configure the parameters.
- Click Create Now.
- Confirm the configuration and submit your request.
- View the newly created load balancer in the load balancer list.
+ - In the upper left corner of the page, click and select the desired region and project.
- Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Click Create Elastic Load Balancer and then configure the parameters.
- Click Create Now.
- Confirm the configuration and submit your request.
- View the newly created load balancer in the load balancer list.
 After you create a dedicated load balancer, configure the security group that contains the ECSs to allow traffic from the VPC where the load balancer works.
Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, click the name of the ECS that has been added to a backend server group.
The page providing details about the ECS is displayed.
+Configuring Security Group Rules- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click
 in the upper left corner to display Service List and choose Computing > Elastic Cloud Server. - On the Elastic Cloud Server page, click the name of the ECS that has been added to a backend server group.
The page providing details about the ECS is displayed.
- Click Security Groups, locate the security group, and view security group rules.
- Click the security group rule ID or Modify Security Group Rule. The security group details page is displayed.
- On the Inbound Rules tab page, click Add Rule. Configure an inbound rule based on Table 2.
Table 2 Security group rulesBackend Protocol
|
@@ -143,7 +143,7 @@ systemctl enable nginx
Allow
|
Protocol: TCP
-Port: the port used by the backend server and health check port
+Port: the port used by the backend server and health check port
|
Backend subnet of the load balancer
|
@@ -171,26 +171,26 @@ systemctl enable nginx
- Click OK.
-Firewall RulesTo control traffic in and out of a subnet, you can associate a firewall with the subnet. Firewalls rules control access to subnets and add an additional layer of defense to your subnets. The default firewall rule denies all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a firewall rule associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.
+ Firewall RulesTo control traffic in and out of a subnet, you can associate a firewall with the subnet. Firewalls rules control access to subnets and add an additional layer of defense to your subnets. Default firewall rules reject all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a firewall associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.
Configure an inbound firewall rule to allow traffic from the VPC where the load balancer resides to backend servers.
- - Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click
 in the upper left corner of the page and choose Network > Virtual Private Cloud. - In the navigation pane on the left, choose Access Control > Firewalls.
- In the firewall list, click the name of the firewall to switch to the page showing its details.
- On the Inbound Rules or Outbound Rules tab page, click Add Rule to add a rule.
- Action: Select Allow.
- Protocol: The protocol must be the same as the one you selected for the listener.
- Source: Set it to the VPC CIDR block.
- Source Port Range: Select a port range.
- Destination: Enter a destination address allowed in this direction. The default value is 0.0.0.0/0, which indicates that traffic from all IP addresses is permitted.
- Destination Port Range: Select a port range.
- (Optional) Description: Describe the firewall rule if necessary.
+- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click in the upper left corner of the page and choose Network > Virtual Private Cloud.
- In the navigation pane on the left, choose Access Control > Firewalls.
- In the firewall list, click the name of the firewall to switch to the page showing its details.
- On the Inbound Rules or Outbound Rules tab page, click Add Rule to add a rule.
- Action: Select Allow.
- Protocol: The protocol must be the same as the one you selected for the listener.
- Source: Set it to the VPC CIDR block.
- Source Port Range: Select a port range based on the service requirements.
- Destination: Enter a destination address allowed in this direction. The default value is 0.0.0.0/0, which indicates that traffic from all IP addresses is permitted.
- Destination Port Range: Select a port range based on the service requirements.
- (Optional) Description: Describe the firewall rule if necessary.
- Click OK.
- Adding a ListenerAdd a listener to the created load balancer. When you add the listener, create a backend server group, configure a health check, and add the two ECSs to the created backend server group.
+ Adding a ListenerAdd a listener to the created load balancer. When you add the listener, create a backend server group, configure a health check, and add the two ECSs to the created backend server group. If a backend server is detected unhealthy, the load balancer will stop routing traffic to it until the backend server recovers.
Configure two forwarding policies to forward HTTP requests to the two ECSs, for example, requests from www.example.com/ELB01/ to ECS01, and those from www.example.com/ELB02/ to ECS02. Figure 4 Traffic forwarding
- - Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener.
- Configure the listener and click Next.
- Name: Enter a name, for example, listener-HTTP.
- Frontend Protocol/Port: Select a protocol and enter a port for the load balancer to receive requests. For example, set it to HTTP and 80.
- - Create a backend server group, configure a health check, and click Finish.
- Backend Server Group
- Name: Enter a name, for example, server_group-ELB.
- Load Balancing Algorithm: Select an algorithm that the load balancer will use to route requests, for example, Weighted round robin.
+- Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener.
- Configure the listener and click Next.
- Name: Enter a name, for example, listener-HTTP.
- Frontend Protocol/Port: Select a protocol and enter a port for the load balancer to receive requests. For example, set it to HTTP and 80.
+ - Create a backend server group, configure a health check, and click Finish.
- Backend server group
- Name: Enter a name, for example, server_group-ELB.
- Load Balancing Algorithm: Select an algorithm that the load balancer will use to route requests, for example, Weighted round robin.
-
Adding a Forwarding Policy- Click the name of the newly added listener and then click Add next to Forwarding Policies.
- Configure the forwarding policy and click Next.
- Name: Enter a name for the forwarding policy, for example, forwarding_policy-ELB01.
- Domain Name: Enter a domain name that will be used to forward the requests, for example, www.example.com. The domain name in the request must exactly match that specified in the forwarding policy.
- URL: You can also specify a URL to forward the requests, for example, /ELB01/.
- URL Matching Rule: Select a rule for matching the specified URL string with the URL in the request. Three options are available, Exact match, Prefix match, and Regular expression match. Exact match enjoys the highest priority, and Regular expression match the lowest priority. Select Exact match here.
- - Create a backend server group, configure a health check, and click Finish.
- Backend Server Group
- Name: Enter a name, for example, server_group-ELB01.
- Load Balancing Algorithm: Select an algorithm that the load balancer will use to route requests, for example, Weighted round robin.
+ - Create a backend server group and configure a health check.
- Backend server group
- Name: Enter a name, for example, server_group-ELB01.
- Load Balancing Algorithm: Select an algorithm that the load balancer will use to route requests, for example, Weighted round robin.
-
- On the CLI of your PC, run the following command to check whether the domain name is mapped to the load balancer EIP:
ping www.example.com
If data packets are returned, the domain name has been mapped to the load balancer EIP.
- - Use your browser to access http://www.example.com/ELB01/. If the following page is displayed, the load balancer has routed the request to ECS01.
Figure 6 Accessing ECS01
+ - Use your browser to access http://www.example.com/ELB01/. If the following page is displayed, the load balancer has routed the request to ECS01.
Figure 6 Accessing ECS01
ELB01/ indicates that the default directory named ECS01 is accessed, while ELB01 indicates the file name. Therefore, the slash (/) following ELB01 must be retained.
- - Use your browser to access http://www.example.com/ELB02/. If the following page is displayed, the load balancer has routed the request to ECS02.
Figure 7 Accessing ECS02
+ - Use your browser to access http://www.example.com/ELB02/. If the following page is displayed, the load balancer has routed the request to ECS02.
Figure 7 Accessing ECS02
Adding a Tag to a Load BalancerYou can add a tag to a load balancer in the following method:
|---|
|
