diff --git a/docs/elb/umn/ALL_META.TXT.json b/docs/elb/umn/ALL_META.TXT.json index ad6aff2d0..5a3239734 100644 --- a/docs/elb/umn/ALL_META.TXT.json +++ b/docs/elb/umn/ALL_META.TXT.json @@ -2973,7 +2973,7 @@ "node_id":"elb_faq_210202201.xml", "product_code":"elb", "code":"145", - "des":"You cannot change the VPC and subnet for your Shared load balancers.You can change the subnet but not the VPC for your dedicated load balancers.", + "des":"You cannot change the VPC and subnet for your shared load balancers.You can change the subnet but not the VPC for your dedicated load balancers.", "doc_type":"usermanual", "kw":"Can I Change the VPC and Subnet for My Load Balancer?,ELB Functionality,User Guide", "search_title":"", @@ -3141,7 +3141,7 @@ "node_id":"elb_faq_0065.xml", "product_code":"elb", "code":"153", - "des":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", + "des":"Quotas can limit the number of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota cannot mee", "doc_type":"usermanual", "kw":"What Is Quota?,Load Balancers,User Guide", "search_title":"", diff --git a/docs/elb/umn/CLASS.TXT.json b/docs/elb/umn/CLASS.TXT.json index 71670bad5..d9ca75c15 100644 --- a/docs/elb/umn/CLASS.TXT.json +++ b/docs/elb/umn/CLASS.TXT.json @@ -1296,7 +1296,7 @@ "code":"144" }, { - "desc":"You cannot change the VPC and subnet for your Shared load balancers.You can change the subnet but not the VPC for your dedicated load balancers.", + "desc":"You cannot change the VPC and subnet for your shared load balancers.You can change the subnet but not the VPC for your dedicated load balancers.", "product_code":"elb", "title":"Can I Change the VPC and Subnet for My Load Balancer?", "uri":"elb_faq_210202201.html", @@ -1368,7 +1368,7 @@ "code":"152" }, { - "desc":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", + "desc":"Quotas can limit the number of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota cannot mee", "product_code":"elb", "title":"What Is Quota?", "uri":"elb_faq_0065.html", diff --git a/docs/elb/umn/elb_billing_0003.html b/docs/elb/umn/elb_billing_0003.html index 880e75770..ae825bc08 100644 --- a/docs/elb/umn/elb_billing_0003.html +++ b/docs/elb/umn/elb_billing_0003.html @@ -10,27 +10,27 @@

Billing Mode

-

Formula

+

Billing Formula

LCU

-

You are charged based on the number of LCUs used by a load balancer per hour.

+

You are charged based on the number of LCUs used by a load balancer.

An LCU measures the dimensions on which a dedicated load balancer routes the traffic. See LCU prices in LCU Pricing.

Pay-per-use

-

Unit price x Number of LCUs x Required duration

+

Unit price × Number of LCUs

-

Load Balancer

+

Load balancer

-

You are charged for how long a dedicated load balancer is retained in your account. If the load balancer is retained in your account for less than 1 hour, you will be charged for the actual duration, accurate to seconds.

+

You are charged for how long a dedicated load balancer is retained in your account. If the load balancer is retained in your account for less than 1 hour, you will be charged for the actual duration, accurate to seconds.

Pay-per-use

-

Unit price x Required duration

+

Unit price × Required duration

@@ -38,7 +38,7 @@

The billing items of dedicated load balancers vary by specification type. For details, see Table 2.

-
Table 2 Varied billing items by billing mode

Billing Mode

+
@@ -72,7 +72,7 @@

LCU Pricing

An LCU measures the dimensions on which a dedicated load balancer routes the traffic. See LCU price in Table 3.

-

The unit price of LCU varies depending on the billing mode and specifications. See the actual price of LCU on the console. LCU price = Unit price x Number of LCUs x Required duration.

+

The unit price of LCU varies depending on the specifications. See the actual price of LCU on the console. LCU price = Unit price × Number of LCUs.

Table 2 Billing items

Billing Mode

Specifications
@@ -104,11 +104,11 @@
Table 3 LCU pricing

Billing Mode
-
  • If you deploy a dedicated load balancer in multiple AZs, its performance will multiply as the number of AZs increases.
  • Note the following when calculating the number of LCUs:
    • LCU quantity refers to the number of LCUs corresponding to a specification in a single AZ.
    • If you select multiple AZs for a load balancer, the number of LCUs is calculated as follows: Number of LCUs = LCUs of the selected specification x Number of the selected AZs.
    +
    • If you deploy a dedicated load balancer in multiple AZs, its performance will multiply as the number of AZs increases.
    • Note the following when calculating the number of LCUs:
      • LCU quantity refers to the number of LCUs corresponding to a specification in a single AZ.
      • If you select multiple AZs for a load balancer, the number of LCUs is calculated as follows: Number of LCUs = LCUs of the selected specification × Number of the selected AZs.
-

LCU Billing for Elastic Specifications

An LCU has four dimensions: new connections, maximum concurrent connections, processed bytes, and rule evaluations.

+

LCU Billing for Elastic Specifications

An LCU has four dimensions: new connections, maximum concurrent connections, processed bytes, and rule evaluations.

You can calculate the number of LCUs by taking the maximum LCUs consumed across the four dimensions.

The number of LCUs is rounded up to the nearest integer.

@@ -147,7 +147,7 @@

Table 5 lists the LCU performance supported by different protocols.

-
Table 5 LCU performance supported by different protocols

Protocol

+
@@ -167,7 +167,7 @@ - -
Table 5 LCU performance supported by different protocols

Protocol

New Connections per Second

1 GB

N/A

+

-

UDP

@@ -178,7 +178,7 @@

1 GB

N/A

+

-

HTTP/HTTPS

diff --git a/docs/elb/umn/elb_faq_0024.html b/docs/elb/umn/elb_faq_0024.html index d8bea88d7..fba727a53 100644 --- a/docs/elb/umn/elb_faq_0024.html +++ b/docs/elb/umn/elb_faq_0024.html @@ -3,21 +3,21 @@

How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?

How UDP Health Checks Work

UDP is a connectionless protocol. A UDP health check is implemented as follows:

-
  • The health check node sends an ICMP request to the backend server based on the health check configuration.
    • If the health check node receives an ICMP reply from the backend server, it considers the backend server healthy and continues the health check.
    • If the health check node does not receive an ICMP reply from the backend server, it considers the backend server unhealthy.
    -
  • After receiving the ICMP reply, the health check node sends a UDP probe packet to the backend server.
    • If the health check node receives an ICMP Port Unreachable message from the backend server within the timeout duration, the backend server is considered unhealthy.
    • If the health check node does not receive an ICMP Port Unreachable message from the backend server within the timeout duration, the backend server is considered healthy.
    +
    • The health check node sends an ICMP request to the backend server based on the health check configuration.
      • If the health check node receives an ICMP reply from the backend server, it considers the backend server healthy and continues the health check.
      • If the health check node does not receive an ICMP reply from the backend server, it considers the backend server unhealthy.
      +
    • After receiving the ICMP reply, the health check node sends a UDP probe packet to the backend server.
      • If the health check node receives an ICMP Port Unreachable message from the backend server within the timeout duration, the backend server is considered unhealthy.
      • If the health check node does not receive an ICMP Port Unreachable message from the backend server within the timeout duration, the backend server is considered healthy.

    When you use UDP for health checks, retain default parameter settings.

    Troubleshooting

    If the backend server is unhealthy, use either of the following methods to locate the fault:

    -
    • Check whether the timeout duration is too short.

      One possible cause is that the ICMP Echo Reply or ICMP Port Unreachable message returned by the backend server does not reach the health check node within the timeout duration. As a result, the health check result is inaccurate.

      +
      • Check whether the timeout duration is too short.

        One possible cause is that the ICMP Echo Reply or ICMP Port Unreachable message returned by the backend server does not reach the health check node within the timeout duration. As a result, the health check result is inaccurate.

        It is recommended that you change the timeout duration to a larger value.

        -

        UDP health checks are different from other health checks. If the health check timeout duration is too short, the health check result of the backend server frequently toggles back and forth between Healthy and Unhealthy.

        -
      • Check whether the backend server restricts the rate at which ICMP messages are generated.
      +

      UDP health checks are different from other health checks. If the health check timeout duration is too short, the health check result of the backend server frequently toggles back and forth between Healthy and Unhealthy.

      +
    • Check whether the backend server restricts the rate at which ICMP messages are generated.

    For Linux servers, run the following commands to query the rate limit and rate mask:

    sysctl -q net.ipv4.icmp_ratelimit

    The default rate limit is 1000.

    sysctl -q net.ipv4.icmp_ratemask
    -

    The default rate mask is 6168.

    +

    The default rate mask is 6168.

    If the returned value of the first command is the default value or 0, run the following command to remove the rate limit of Port Unreachable messages:

    sysctl -w net.ipv4.icmp_ratemask=6160

    For more information, see the Linux Programmer's Manual. On the Linux CLI, run the following command to display the manual:

    @@ -27,7 +27,7 @@

Precautions

Note the following when you configure UDP health checks:

-
  • UDP health checks use ping packets to check the health of the backend server. To ensure smooth transmission of these packets, ensure that ICMP is enabled on the backend server by performing the following:

    Log in to the server and run the following command as user root:

    +
    • UDP health checks use ping packets to check the health of the backend server. To ensure smooth transmission of these packets, ensure that ICMP is enabled on the backend server by performing the following:

      Log in to the server and run the following command as user root:

      cat /proc/sys/net/ipv4/icmp_echo_ignore_all

      • If the returned value is 1, ICMP is disabled.
      • If the returned value is 0, ICMP is enabled.
    • The health check result may be different from the actual health of the backend server.

      If the backend server runs Linux, the rate of ICMP packets may be limited due to Linux's defense against ping flood attacks when there is a large number of concurrent requests. In this case, if a service exception occurs, the load balancer will not receive error message port XX unreachable and will consider the health check to be successful. As a result, there is an inconsistency between the health check result and the actual server health.

      diff --git a/docs/elb/umn/elb_faq_0065.html b/docs/elb/umn/elb_faq_0065.html index 628a0c403..907bfdf91 100644 --- a/docs/elb/umn/elb_faq_0065.html +++ b/docs/elb/umn/elb_faq_0065.html @@ -1,16 +1,16 @@

      What Is Quota?

      -

      What Is Quota?

      Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

      +

      Introduction

      Quotas can limit the number of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

      If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.

      -

      How Do I View My Quotas?

      1. Log in to the management console.
      2. Click in the upper left corner and select the desired region and project.
      3. In the upper right corner of the page, click .

        The Service Quota page is displayed.

        +

        How Do I View My Quotas?

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. In the upper right corner of the page, click .

          The Service Quota page is displayed.

        4. View the used and total quota of each type of resources on the displayed page.

          If a quota cannot meet service requirements, apply for a higher quota.

        How Do I Apply for a Higher Quota?

        The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

        Before dialing the hotline number or sending an email, make sure that the following information has been obtained:

        -
        • Domain name, project name, and project ID, which can be obtained by performing the following operations:

          Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.

          +
          • Domain name, project name, and project ID, which can be obtained by performing the following operations:

            Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.

          • Quota information, which includes:
            • Service name
            • Quota type
            • Required quota

          Learn how to obtain the service hotline and email address.

          diff --git a/docs/elb/umn/elb_faq_0085.html b/docs/elb/umn/elb_faq_0085.html index f3faee35a..b9663debd 100644 --- a/docs/elb/umn/elb_faq_0085.html +++ b/docs/elb/umn/elb_faq_0085.html @@ -2,7 +2,7 @@

          What Types of Sticky Sessions Does ELB Support?

          Dedicated load balancers: Source IP address and Load balancer cookie

          -

          Shared load balancers: Source IP address, Load balancer cookie, and Application cookie

          +

          Shared load balancers: Source IP address, Load balancer cookie, and Application cookie

          diff --git a/docs/elb/umn/elb_faq_0088.html b/docs/elb/umn/elb_faq_0088.html index 28990e5f2..b8a2e789d 100644 --- a/docs/elb/umn/elb_faq_0088.html +++ b/docs/elb/umn/elb_faq_0088.html @@ -3,27 +3,27 @@

          What Types of APIs Does ELB Provide? What Are Permissions of ELB?

          ELB supports the following policies:

          -
          Table 1 ELB policies

          Policy Type

          +
          - - - - - - - - @@ -36,266 +36,266 @@
          Table 1 ELB policies

          Policy Type

          Policy Name

          +

          Policy Name

          Description

          +

          Description

          RBAC policy

          +

          RBAC policy

          ELB Administrator

          +

          ELB Administrator

          Has all permissions on ELB.

          +

          Has all permissions on ELB.

          Before assigning the RBAC policy to a user group, check whether the user group has a dependent policy. If yes, set the dependent permission to make the RBAC policy take effect.

          Fine-grained policy

          +

          Fine-grained policy

          ELB FullAccess

          +

          ELB FullAccess

          Has all permissions on ELB.

          +

          Has all permissions on ELB.

          If this function is not enabled, you cannot assign a fine-grained policy to a user group.
          -
          Table 2 Common operations supported by system-defined policies

          Operation

          +
          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/elb/umn/elb_faq_0090.html b/docs/elb/umn/elb_faq_0090.html index aafcf7ef0..07f3ec841 100644 --- a/docs/elb/umn/elb_faq_0090.html +++ b/docs/elb/umn/elb_faq_0090.html @@ -78,9 +78,9 @@ cat localhost_access_log..2021-11-29.txt

          For load balancing at Layer 4 (TCP/UDP), you can enable Transfer Client IP Address to obtain the source IP address.

          • Method 1 (for TCP or UDP listeners): Enable Transfer Client IP Address.
            • After this function is enabled, traffic, such as unidirectional download or push traffic, may be interrupted when backend servers are being migrated during the migration of the associated classic load balancer. After backend servers are migrated, retransmit the packets to restore the traffic.
            • After this function is enabled, the associated backend servers cannot be used as clients to access the listener.
            • If a backend server has been associated with the listener and health checks are enabled, enabling this function will check the health of the backend server, and traffic to this server will be interrupted for two health check intervals.
            -
            1. Perform the following steps to enable the function:
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the load balancer list, click the name of the load balancer.
              5. Click Listeners.
                • To add a listener, click Add Listener.
                • To modify a listener, locate the listener, click on the right of its name, and click Modify Listener. In the Modify Listener dialog box, modify the parameters as needed.
                +
                1. Perform the following steps to enable the function:
                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the load balancer list, click the name of the load balancer.
                  5. Click Listeners.
                    • To add a listener, click Add Listener.
                    • To modify a listener, locate the listener, click on the right of its name, and click Modify Listener. In the Modify Listener dialog box, modify the parameters as needed.
                  6. Enable Transfer Client IP Address.
                  -
                2. Configure security groups, firewalls, and OS and software security policies so that IP addresses of the clients can access these backend servers.

                  If Transfer Client IP Address is enabled, a server cannot serve as both a backend server and a client. If the client and the backend server use the same server and the Transfer Client IP Address option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.

                  +
                3. Configure security groups, firewalls, and OS and software security policies so that IP addresses of the clients can access these backend servers.

                  If Transfer Client IP Address is enabled, a server cannot serve as both a backend server and a client. If the client and the backend server use the same server and the Transfer Client IP Address option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.

          diff --git a/docs/elb/umn/elb_faq_0212.html b/docs/elb/umn/elb_faq_0212.html index 0f981585e..e4c123204 100644 --- a/docs/elb/umn/elb_faq_0212.html +++ b/docs/elb/umn/elb_faq_0212.html @@ -1,8 +1,11 @@ -

          ELB Use

          -

          + +

          ELB Use

          + +

          +
          • ELB Functionality
            diff --git a/docs/elb/umn/elb_faq_05_0008.html b/docs/elb/umn/elb_faq_05_0008.html index 256d2cc0d..5a70de74b 100644 --- a/docs/elb/umn/elb_faq_05_0008.html +++ b/docs/elb/umn/elb_faq_05_0008.html @@ -5,9 +5,9 @@
          Table 2 Common operations supported by system-defined policies

          Operation

          ELB FullAccess

          +

          ELB FullAccess

          ELB ReadOnlyAccess

          +

          ELB ReadOnlyAccess

          ELB Administrator

          +

          ELB Administrator

          Creating a load balancer

          +

          Creating a load balancer

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Querying a load balancer

          +

          Querying a load balancer

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Querying a load balancer and associated resources

          +

          Querying a load balancer and associated resources

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Querying load balancers

          +

          Querying load balancers

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Modifying a load balancer

          +

          Modifying a load balancer

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Deleting a load balancer

          +

          Deleting a load balancer

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Adding a listener

          +

          Adding a listener

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Querying a listener

          +

          Querying a listener

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Modifying a listener

          +

          Modifying a listener

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Deleting a listener

          +

          Deleting a listener

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Adding a backend server group

          +

          Adding a backend server group

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Querying a backend server group

          +

          Querying a backend server group

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Modifying a backend server group

          +

          Modifying a backend server group

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Deleting a backend server group

          +

          Deleting a backend server group

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Adding a backend server

          +

          Adding a backend server

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Querying a backend server

          +

          Querying a backend server

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Modifying a backend server

          +

          Modifying a backend server

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Deleting a backend server

          +

          Deleting a backend server

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Configuring a health check

          +

          Configuring a health check

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Querying a health check

          +

          Querying a health check

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Modifying a health check

          +

          Modifying a health check

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Disabling a health check

          +

          Disabling a health check

          Supported

          +

          √

          Not supported

          +

          ×

          Supported

          +

          √

          Assigning an EIP

          +

          Assigning an EIP

          Not supported

          +

          ×

          Not supported

          +

          ×

          Supported

          +

          √

          Binding an EIP to a load balancer

          +

          Binding an EIP to a load balancer

          Not supported

          +

          ×

          Not supported

          +

          ×

          Supported

          +

          √

          Querying an EIP

          +

          Querying an EIP

          Supported

          +

          √

          Supported

          +

          √

          Supported

          +

          √

          Unbinding an EIP from a load balancer

          +

          Unbinding an EIP from a load balancer

          Not supported

          +

          ×

          Not supported

          +

          ×

          Supported

          +

          √

          Viewing metrics

          +

          Viewing metrics

          Not supported

          +

          ×

          Not supported

          +

          ×

          Supported

          +

          √

          Viewing access logs

          +

          Viewing access logs

          Not supported

          +

          ×

          Not supported

          +

          ×

          Supported

          +

          √
          - - @@ -15,9 +15,9 @@ - - @@ -38,9 +38,9 @@ - - @@ -61,9 +61,9 @@ - - @@ -86,23 +86,23 @@
          Table 1 Sticky sessions supported by dedicated load balancers

          Load Balancing Algorithm

          Sticky Session Type

          +

          Sticky Session Type

          Layer 4 (TCP/UDP)

          +

          Layer 4 (TCP/UDP)

          Layer 7 (HTTP/HTTPS)

          Weighted round robin

          Source IP address

          +

          Source IP address

          Supported

          +

          Supported

          Not supported

          Weighted least connections

          Source IP address

          +

          Source IP address

          Not supported

          +

          Not supported

          Not supported

          Source IP hash

          Source IP address

          +

          Source IP address

          N/A

          +

          N/A

          Not supported

          -
          Table 2 Sticky sessions supported by shared load balancers

          Load Balancing Algorithm

          +
          - - - - - - - - - - - - - - -
          Table 2 Sticky sessions supported by shared load balancers

          Load Balancing Algorithm

          Sticky Session Type

          +

          Sticky Session Type

          Layer 4 (TCP/UDP)

          +

          Layer 4 (TCP/UDP)

          Layer 7 (HTTP/HTTPS)

          +

          Layer 7 (HTTP/HTTPS)

          Weighted round robin

          +

          Weighted round robin

          Source IP address

          +

          Source IP address

          Supported

          +

          Supported

          Not supported

          +

          Not supported

          Load balancer cookie

          @@ -119,13 +119,13 @@

          Supported

          Weighted least connections

          +

          Weighted least connections

          Source IP address

          +

          Source IP address

          Not supported

          +

          Not supported

          Not supported

          +

          Not supported

          Load balancer cookie

          @@ -142,13 +142,13 @@

          Not supported

          Source IP hash

          +

          Source IP hash

          Source IP address

          +

          Source IP address

          N/A

          +

          N/A

          Not supported

          +

          Not supported

          Load balancer cookie

          diff --git a/docs/elb/umn/elb_faq_210202201.html b/docs/elb/umn/elb_faq_210202201.html index 279526df1..a5042db16 100644 --- a/docs/elb/umn/elb_faq_210202201.html +++ b/docs/elb/umn/elb_faq_210202201.html @@ -1,7 +1,7 @@

          Can I Change the VPC and Subnet for My Load Balancer?

          -

          You cannot change the VPC and subnet for your Shared load balancers.

          +

          You cannot change the VPC and subnet for your shared load balancers.

          You can change the subnet but not the VPC for your dedicated load balancers.

          diff --git a/docs/elb/umn/elb_faq_21020221.html b/docs/elb/umn/elb_faq_21020221.html index af539b0f2..31c2a7116 100644 --- a/docs/elb/umn/elb_faq_21020221.html +++ b/docs/elb/umn/elb_faq_21020221.html @@ -1,7 +1,7 @@

          Can I Upgrade a Shared Load Balancer to a Dedicated Load Balancer Without Interrupting Traffic Routing?

          -

          No. Shared load balancers cannot be upgraded to dedicated load balancers.

          +

          No. Shared load balancers cannot be upgraded to dedicated load balancers.

          diff --git a/docs/elb/umn/elb_faq_210310.html b/docs/elb/umn/elb_faq_210310.html index 471e36a9c..a4aa89185 100644 --- a/docs/elb/umn/elb_faq_210310.html +++ b/docs/elb/umn/elb_faq_210310.html @@ -2,7 +2,7 @@

          Do Shared Load Balancers Have Specifications?

          No.

          -

          Shared load balancers share underlying resources, and the performance of one load balancer is affected by other load balancers. Only dedicated load balancers have exclusive use of their underlying resources. The performance of a dedicated load balancer is not affected by other dedicated load balancers on the Internet.

          +

          Shared load balancers share underlying resources, and the performance of one load balancer is affected by other load balancers. Only dedicated load balancers have exclusive use of their underlying resources. The performance of a dedicated load balancer is not affected by other dedicated load balancers on the Internet.

          diff --git a/docs/elb/umn/elb_lb_000006.html b/docs/elb/umn/elb_lb_000006.html index 505998405..f7420f87e 100644 --- a/docs/elb/umn/elb_lb_000006.html +++ b/docs/elb/umn/elb_lb_000006.html @@ -34,6 +34,8 @@

          Specifies the AZ of the load balancer. You can deploy a load balancer in multiple AZs for high availability. If an AZ becomes faulty or unavailable, the load balancers in other AZs can route requests to backend servers to ensure service continuity and improve application reliability.

          If you deploy a load balancer in multiple AZs, its performance such as the number of new connections and the number of concurrent connections will multiply. For example, if you deploy a dedicated load balancer in two AZs, it can handle up to 40 million concurrent connections.

          +
          NOTE:

          By default, all AZs are selected. You can select the AZs as needed.

          +
          NOTE:
          • If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.
          • For requests from a private network:
            • If clients are in an AZ you have selected when you created the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer becomes unavailable, requests are distributed by the load balancer in another AZ you have selected.

              If the load balancer is available but the connections that the load balancer needs to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications.

            • If clients are in an AZ that is not selected when you created the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.
          • If requests are from a Direct Connect connection, the load balancer in the same AZ as the Direct Connect connection routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.
          • If clients are in a VPC that is different from where the load balancer works, the load balancer in the AZ where the original VPC subnet resides routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.
          diff --git a/docs/elb/umn/elb_lb_000011.html b/docs/elb/umn/elb_lb_000011.html index b4c2489a2..c91b1381a 100644 --- a/docs/elb/umn/elb_lb_000011.html +++ b/docs/elb/umn/elb_lb_000011.html @@ -3,10 +3,10 @@

          Adding to or Removing from an IPv6 Shared Bandwidth

          Scenarios

          After you bind an IPv6 address to a dedicated load balancer, you can add the load balancer to a shared bandwidth to enable it to route requests over the Internet. After you are finished with the shared bandwidth, you can remove the load balancer from the shared bandwidth, so that it can only route requests within a VPC.

          -

          Adding to an IPv6 Shared Bandwidth

          1. Log in to the management console.
          2. In the upper left corner of the page, click and select the desired region and project.
          3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
          4. On the Load Balancers page, locate the load balancer that you want to add to a shared bandwidth, and click More > Add to IPv6 Shared Bandwidth in the Operation column.
          5. In the Add to IPv6 Shared Bandwidth dialog box, select the shared bandwidth to which you want to add the dedicated load balancer.

            If no shared bandwidths are available, buy one as prompted.

            +

            Adding to an IPv6 Shared Bandwidth

            1. Log in to the management console.
            2. In the upper left corner of the page, click and select the desired region and project.
            3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
            4. On the Load Balancers page, locate the load balancer that you want to add to a shared bandwidth, and click More > Add to IPv6 Shared Bandwidth in the Operation column.
            5. In the Add to IPv6 Shared Bandwidth dialog box, select the shared bandwidth to which you want to add the dedicated load balancer.

              If no shared bandwidths are available, buy one as prompted.

            6. Click OK.
            -

            Removing from an IPv6 Shared Bandwidth

            1. Log in to the management console.
            2. In the upper left corner of the page, click and select the desired region and project.
            3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
            4. On the Load Balancers page, locate the load balancer that you want to remove from a shared bandwidth, and click More > Remove from IPv6 Shared Bandwidth in the Operation column.
            5. In the displayed dialog box, confirm the shared bandwidth from which you want to remove the load balancer.

              After the load balancer is removed from the shared bandwidth, the load balancer cannot route requests over the Internet.

              +

              Removing from an IPv6 Shared Bandwidth

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. On the Load Balancers page, locate the load balancer that you want to remove from a shared bandwidth, and click More > Remove from IPv6 Shared Bandwidth in the Operation column.
              5. In the displayed dialog box, confirm the shared bandwidth from which you want to remove the load balancer.

                After the load balancer is removed from the shared bandwidth, the load balancer cannot route requests over the Internet.

              6. Click Yes.
              diff --git a/docs/elb/umn/elb_pro_0001.html b/docs/elb/umn/elb_pro_0001.html index 0c8819d58..86894ae98 100644 --- a/docs/elb/umn/elb_pro_0001.html +++ b/docs/elb/umn/elb_pro_0001.html @@ -2,70 +2,70 @@

              Basic Concepts

              -
              Table 1 Some concepts about ELB

              Term

              +
              - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/elb/umn/elb_pro_01_0004.html b/docs/elb/umn/elb_pro_01_0004.html index 74bd58624..c54bfd8e0 100644 --- a/docs/elb/umn/elb_pro_01_0004.html +++ b/docs/elb/umn/elb_pro_01_0004.html @@ -33,7 +33,7 @@
              Table 1 Some concepts about ELB

              Term

              Definition

              +

              Definition

              Load balancer

              +

              Load balancer

              A load balancer distributes incoming traffic across backend servers.

              +

              A load balancer distributes incoming traffic across backend servers.

              Listener

              +

              Listener

              A listener listens on requests from clients and routes the requests to backend servers based on the settings that you configure when you add the listener.

              +

              A listener listens on requests from clients and routes the requests to backend servers based on the settings that you configure when you add the listener.

              Backend server

              +

              Backend server

              A backend server is a cloud server added to a backend server group associated with a load balancer. When you add a listener to a load balancer, you can create or select a backend server group to receive requests from the load balancer by using the port and protocol you specify for the backend server group and the load balancing algorithm you select.

              +

              A backend server is a cloud server added to a backend server group associated with a load balancer. When you add a listener to a load balancer, you can create or select a backend server group to receive requests from the load balancer by using the port and protocol you specify for the backend server group and the load balancing algorithm you select.

              Backend server group

              +

              Backend server group

              A backend server group is a collection of cloud servers that have same features. When you add a listener, you select a load balancing algorithm and create or select a backend server group. Incoming traffic is routed to the corresponding backend server group based on the listener's configuration.

              +

              A backend server group is a collection of cloud servers that have same features. When you add a listener, you select a load balancing algorithm and create or select a backend server group. Incoming traffic is routed to the corresponding backend server group based on the listener's configuration.

              Health check

              +

              Health check

              ELB periodically sends requests to backend servers to check whether they can process requests. If a backend server is detected as unhealthy, the load balancer stops routing requests to it. After the backend server recovers, the load balancer will resume routing requests to it.

              +

              Load balancers periodically send requests to backend servers to check whether they can process requests. If a backend server is detected as unhealthy, the load balancer stops routing requests to it. After the backend server recovers, the load balancer resumes routing requests to it.

              Redirect

              +

              Redirect

              HTTPS is an extension of HTTP. HTTPS encrypts data between a web server and a browser.

              +

              HTTPS is an extension of HTTP. HTTPS encrypts data between a web server and a browser.

              Sticky session

              +

              Sticky session

              Sticky sessions ensure that requests from a client always get routed to the same backend server before a session elapses.

              +

              Sticky sessions ensure that requests from a client always get routed to the same backend server before a session elapses.

              WebSocket

              +

              WebSocket

              WebSocket is a new HTML5 protocol that provides full-duplex communication between the browser and the server. WebSocket saves server resources and bandwidth, and enables real-time communication. Both WebSocket and HTTP depend on TCP to transmit data. A handshake connection is required between the browser and server, so that they can communicate with each other only after the connection is established. However, as a bidirectional communication protocol, WebSocket is different from HTTP. After the handshake succeeds, both the server and browser (or client agent) can actively send data to or receive data from each other.

              +

              WebSocket is a new HTML5 protocol that provides full-duplex communication between the browser and the server. WebSocket saves server resources and bandwidth, and enables real-time communication. Both WebSocket and HTTP depend on TCP to transmit data. A handshake connection is required between the browser and server, so that they can communicate with each other only after the connection is established. However, as a bidirectional communication protocol, WebSocket is different from HTTP. After the handshake succeeds, both the server and browser (or client agent) can actively send data to or receive data from each other.

              SNI

              +

              SNI

              SNI, an extension to Transport Layer Security (TLS), enables a server to present multiple certificates on the same IP address and port number. SNI allows the client to indicate the domain name of the website while sending an SSL handshake request. Once receiving the request, the load balancer queries the right certificate based on the hostname or domain name and returns the certificate to the client. If no certificate is found, the load balancer will return the default certificate.

              +

              SNI, an extension to Transport Layer Security (TLS), enables a server to present multiple certificates on the same IP address and port number. SNI allows the client to indicate the domain name of the website while sending an SSL handshake request. Once receiving the request, the load balancer queries the right certificate based on the hostname or domain name and returns the certificate to the client. If no certificate is found, the load balancer will return the default certificate.

              Persistent connection

              +

              Persistent connection

              A persistent connection allows multiple data packets to be sent continuously over a TCP connection. If no data packet is sent during the connection, the client and server send link detection packets to each other to maintain the connection.

              +

              A persistent connection allows multiple data packets to be sent continuously over a TCP connection. If no data packet is sent during the connection, the client and server send link detection packets to each other to maintain the connection.

              Short connection

              +

              Short connection

              A short connection is a connection established when data is exchanged between the client and server and immediately closed after the data is sent.

              +

              A short connection is a connection established when data is exchanged between the client and server and immediately closed after the data is sent.

              Concurrent connection

              +

              Concurrent connection

              Concurrent connections are total number of TCP connections initiated by clients and routed to backend servers by a load balancer per second.

              +

              Concurrent connections are total number of TCP connections initiated by clients and routed to backend servers by a load balancer per second.
              -
              Table 2 Shared load balancers and their network types

              Load Balancer Type

              +
              @@ -41,7 +41,7 @@ - diff --git a/docs/elb/umn/elb_qs_0001.html b/docs/elb/umn/elb_qs_0001.html index f6719c0d5..763e2df0d 100644 --- a/docs/elb/umn/elb_qs_0001.html +++ b/docs/elb/umn/elb_qs_0001.html @@ -2,11 +2,11 @@

              Overview

              To use ELB to distribute traffic across backend servers, you need to create a dedicated load balancer or a shared load balancer.

              -

              Two examples are given to show how you can quickly create a shared load balancer to distribute incoming traffic across backend servers.

              -
              • Entry level: An application deployed on separated ECSs needs to handle a large number of requests. Health checks are required to monitor the health of the servers to ensure that incoming traffic is routed only to healthy servers to eliminate SPOFs and improve service availability.
                Figure 1 Entry level
                -

                As the incoming traffic increases, you can add more servers to balance the load across backend servers.

                +

                Two examples are given to show how you can quickly create a shared load balancer to distribute incoming traffic across backend servers.

                +
                • Entry level: An application deployed on separated ECSs needs to handle a large number of requests. Health checks are required to monitor the health of the servers to ensure that incoming traffic is routed only to healthy servers to eliminate SPOFs and improve service availability.
                  Figure 1 Entry level
                  +

                  As the incoming traffic increases, you can add more servers to balance the load across backend servers.

                • Advanced level: An application deployed on separated servers uses one domain name but different URLs to provide services, and requests are routed to different servers based on the URLs. Forwarding policies are required to forward requests from different URLs to the servers in the corresponding backend server groups.
                  Figure 2 Advanced level
                  -

                  As the incoming traffic increases, you can add more backend servers to the two backend server groups. You can also configure health checks to monitor the health of backend servers to ensure that incoming traffic is routed only to healthy backend servers.

                  +

                  As the incoming traffic increases, you can add more backend servers to the two backend server groups. You can also configure health checks to monitor the health of backend servers to ensure that incoming traffic is routed only to healthy backend servers.

              diff --git a/docs/elb/umn/elb_ug_bq_0000.html b/docs/elb/umn/elb_ug_bq_0000.html index 07b3d7d16..367b25acd 100644 --- a/docs/elb/umn/elb_ug_bq_0000.html +++ b/docs/elb/umn/elb_ug_bq_0000.html @@ -12,7 +12,7 @@

              Adding a Tag to a Listener

              You can add tags when you add listeners.

              To add a tag to an existing listener, perform the following steps:

              -
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. Locate the load balancer and click its name.
              5. Click Listeners, locate the listener, and click its name.
              6. Under Tags, click Add Tag.
              7. In the Add Tag dialog box, enter a tag key and value and click OK.
                • A maximum of 20 tags can be added to a listener.
                • Each tag is a key-value pair, and the tag key is unique.
                +
                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, and click its name.
                6. Under Tags, click Add Tag.
                7. In the Add Tag dialog box, enter a tag key and value and click OK.
                  • A maximum of 20 tags can be added to a listener.
                  • Each tag is a key-value pair, and the tag key is unique.

                diff --git a/docs/elb/umn/elb_ug_fz_0003_01.html b/docs/elb/umn/elb_ug_fz_0003_01.html index 43c9cf95c..5d21d6411 100644 --- a/docs/elb/umn/elb_ug_fz_0003_01.html +++ b/docs/elb/umn/elb_ug_fz_0003_01.html @@ -1,13 +1,13 @@

                Network Traffic Paths

                -

                Load balancers communicate with backend servers over a private network.

                -
                • If backend servers process only requests routed from load balancers, there is no need to assign EIPs or create NAT gateways.
                • If backend servers need to provide Internet-accessible services or access the Internet, you must assign EIPs or create NAT gateways.
                +

                Load balancers communicate with backend servers over a private network.

                +
                • If backend servers process only requests routed from load balancers, there is no need to assign EIPs or create NAT gateways.
                • If backend servers need to provide Internet-accessible services or access the Internet, you must assign EIPs or create NAT gateways.

                Inbound Network Traffic Paths

                The listeners' configurations determine how load balancers distribute incoming traffic.
                Figure 1 Inbound network traffic
                -
                When a listener uses TCP or UDP to receive incoming traffic:
                • Incoming traffic is routed only through the LVS cluster.
                • The LVS cluster directly routes incoming traffic to backend servers using the load balancing algorithm you select when you add the listener.
                +
                When a listener uses TCP or UDP to receive incoming traffic:
                • Incoming traffic is routed only through the LVS cluster.
                • The LVS cluster directly routes incoming traffic to backend servers using the load balancing algorithm you select when you add the listener.
                -
                When a listener uses HTTP or HTTPS to receive incoming traffic:
                • Incoming traffic is routed first to the LVS cluster, then to the Nginx cluster, and finally across backend servers.
                • For HTTPS traffic, the Nginx cluster validates certificates and decrypts data packets before distributing the traffic across backend servers using HTTP.
                +
                When a listener uses HTTP or HTTPS to receive incoming traffic:
                • Incoming traffic is routed first to the LVS cluster, then to the Nginx cluster, and finally across backend servers.
                • For HTTPS traffic, the Nginx cluster validates certificates and decrypts data packets before distributing the traffic across backend servers using HTTP.

                Outbound Network Traffic Paths

                The outbound traffic is routed back the same way the traffic came in.
                Figure 2 Outbound network traffic
                diff --git a/docs/elb/umn/elb_ug_fz_0005.html b/docs/elb/umn/elb_ug_fz_0005.html index 1fc52552f..d30d07928 100644 --- a/docs/elb/umn/elb_ug_fz_0005.html +++ b/docs/elb/umn/elb_ug_fz_0005.html @@ -3,7 +3,7 @@

                Configuring Deletion Protection for Load Balancers

                Scenarios

                You can enable deletion protection for load balancers to prevent them from being deleted by accident.

                -

                Procedure

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. In the Summary tab, enable Deletion Protection.
                +

                Procedure

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. In the Summary tab, enable Deletion Protection.

                Disable deletion protection before you delete a load balancer.

                diff --git a/docs/elb/umn/elb_ug_hd_0002.html b/docs/elb/umn/elb_ug_hd_0002.html index 372df8cad..6cb6cb655 100644 --- a/docs/elb/umn/elb_ug_hd_0002.html +++ b/docs/elb/umn/elb_ug_hd_0002.html @@ -60,7 +60,7 @@

                Configuring Firewall Rules

                To control traffic in and out of a subnet, you can associate a firewall with the subnet. Firewall 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.

                You can configure an inbound firewall rule to permit access from 100.125.0.0/16.

                ELB translates the public IP addresses used to access backend servers into private IP addresses in 100.125.0.0/16. You cannot configure firewall rules to prevent public IP addresses from accessing backend servers.

                -
                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Virtual Private Cloud.
                4. In the navigation pane on the left, choose Access Control > Firewalls.
                5. In the firewall list, click the name of the firewall to switch to the page showing its details.
                6. On the Inbound Rules or Outbound Rules tab page, click Add Rule to add an inbound or outbound rule.
                  • Type: Select the IP address type supported by the rule. The value can be IPv4 or IPv6.
                  • Action: Select Allow.
                  • Protocol: The protocol must be the same as the backend protocol.
                  • Source: Set it to 100.125.0.0/16.
                  • 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.
                  +
                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Virtual Private Cloud.
                  4. In the navigation pane on the left, choose Access Control > Firewalls.
                  5. In the firewall list, click the name of the firewall to switch to the page showing its details.
                  6. On the Inbound Rules or Outbound Rules tab page, click Add Rule to add an inbound or outbound rule.
                    • Type: Select the IP address type supported by the rule. The value can be IPv4 or IPv6.
                    • Action: Select Allow.
                    • Protocol: The protocol must be the same as the backend protocol.
                    • Source: Set it to 100.125.0.0/16.
                    • 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.
                  7. Click OK.
                diff --git a/docs/elb/umn/elb_ug_ip_0000.html b/docs/elb/umn/elb_ug_ip_0000.html index 98c7357b3..71a7fd238 100644 --- a/docs/elb/umn/elb_ug_ip_0000.html +++ b/docs/elb/umn/elb_ug_ip_0000.html @@ -7,7 +7,7 @@

                Constraints

                • By default, you can create a maximum of 50 IP address groups.
                • An IP address group can be associated with a maximum of 50 listeners.
                -

                Procedure

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
                5. On the displayed page, click Create IP Address Group.
                6. Configure the parameters based on Table 1. +

                  Procedure

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
                  5. On the displayed page, click Create IP Address Group.
                  6. Configure the parameters based on Table 1.
              Table 2 Shared load balancers and their network types

              Load Balancer Type

              Network Type

              Shared load balancers

              +

              Shared load balancers

              Public network
              - + + + diff --git a/docs/elb/umn/elb_ug_jt_0002.html b/docs/elb/umn/elb_ug_jt_0002.html index 412ce5c99..1c0d6a145 100644 --- a/docs/elb/umn/elb_ug_jt_0002.html +++ b/docs/elb/umn/elb_ug_jt_0002.html @@ -27,9 +27,9 @@

              Backend Protocols and Ports

              Backend protocols and ports are used by backend servers to receive requests from load balancers. If Windows servers have Internet Information Services (IIS) installed, the default backend protocol and port are HTTP and 80.

              -
              Table 1 Parameters required for creating an IP address group

              Parameter

              Description

              diff --git a/docs/elb/umn/elb_ug_ip_0002.html b/docs/elb/umn/elb_ug_ip_0002.html index 9704a2c90..fb6bcd3e8 100644 --- a/docs/elb/umn/elb_ug_ip_0002.html +++ b/docs/elb/umn/elb_ug_ip_0002.html @@ -7,17 +7,17 @@
              • Each IP address or CIDR block must be on a separate line and end with a carriage return.
              • Each IP address or CIDR block can include a description with a vertical bar (|) separated, for example, 192.168.10.10 | ECS01. The description is 0 to 255 characters long and cannot contain angle brackets (<>).
              • You can add a maximum of 300 IP addresses and CIDR blocks in each IP address group.

              Adding IP Addresses

              After an IP address group is created, you can add IP addresses to an IP address group.

              -
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, click the name of the target address group.
              6. In the lower part of the displayed page, choose IP Addresses tab and click Add IP Addresses.
              7. On the Add IP Addresses page, add IP addresses.
              8. Click OK.
              +
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, click the name of the target address group.
              6. In the lower part of the displayed page, choose IP Addresses tab and click Add IP Addresses.
              7. On the Add IP Addresses page, add IP addresses.
              8. Click OK.

              Changing IP Addresses

              You can perform the following steps to change all IP addresses in an IP address group:

              -
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, you can:
                1. Modify the basic information and change IP addresses of an IP address group:
                  1. Locate the target address group, click Modify in the Operation column.
                  2. You can modify the name and description of an IP address group, and change all its IP addresses.
                  3. Click OK.
                  +
                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
                  5. On the IP Address Groups page, you can:
                    1. Modify the basic information and change IP addresses of an IP address group:
                      1. Locate the target address group, click Modify in the Operation column.
                      2. You can modify the name and description of an IP address group, and change all its IP addresses.
                      3. Click OK.
                    2. Only change IP addresses:
                      1. Click the name of the target IP address group.
                      2. In the lower part of the displayed page, choose IP Addresses tab and click Change IP Address.
                      3. Change IP addresses as you needed.
                      4. Click OK.

              Deleting an IP Address

              If you want to delete IP addresses in batches from an IP address group, see Changing IP Addresses.

              To delete an IP address from an IP address group, perform the following operations:

              -
              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, click the name of the target address group.
              6. In the IP address list, locate the IP address you want to delete and click Delete in the Operation column.

                A confirmation dialog box is displayed.

                +
                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
                5. On the IP Address Groups page, click the name of the target address group.
                6. In the IP address list, locate the IP address you want to delete and click Delete in the Operation column.

                  A confirmation dialog box is displayed.

                7. Confirm the information and click Yes.
              diff --git a/docs/elb/umn/elb_ug_ip_0004.html b/docs/elb/umn/elb_ug_ip_0004.html index d1a8995bb..bdea3be49 100644 --- a/docs/elb/umn/elb_ug_ip_0004.html +++ b/docs/elb/umn/elb_ug_ip_0004.html @@ -5,7 +5,7 @@

              Constraints

              An IP address group that has been used for controlling access to a listener cannot be deleted. You can view the listeners associated with an IP address group by referring to Viewing the Details of an IP Address Group. For details about how to disassociate an IP address group from a listener, see Configuring Access Control.

              -

              Procedure

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, locate the IP address group, and click Delete in the Operation column.
              6. Click Yes.
              +

              Procedure

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. In the navigation pane on the left, choose Elastic Load Balance > IP Address Groups.
              5. On the IP Address Groups page, locate the IP address group, and click Delete in the Operation column.
              6. Click Yes.
              diff --git a/docs/elb/umn/elb_ug_jl_0000.html b/docs/elb/umn/elb_ug_jl_0000.html index dba31a067..1f77ab9b6 100644 --- a/docs/elb/umn/elb_ug_jl_0000.html +++ b/docs/elb/umn/elb_ug_jl_0000.html @@ -8,7 +8,12 @@

              2024-09-26

              +

              2025-04-08

              +

              Added the description that all AZs are selected by default for dedicated load balancers.

              +

              2024-09-26

              Introduced elastic specifications for dedicated load balancers.
              Table 2 Backend protocols and ports

              Protocol

              +
              - diff --git a/docs/elb/umn/elb_ug_jt_0006.html b/docs/elb/umn/elb_ug_jt_0006.html index 2e269a873..13ffca22c 100644 --- a/docs/elb/umn/elb_ug_jt_0006.html +++ b/docs/elb/umn/elb_ug_jt_0006.html @@ -252,7 +252,7 @@
            6. Click Next: Confirm.
            7. Confirm the configuration and click Submit.

              8. Adding a TCP Listener to a Shared Load Balancer

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. Locate the load balancer and click its name.
              5. Under Listeners, click Add Listener. Configure the parameters based on Table 4. -
              Table 2 Backend protocols and ports

              Protocol

              Port

              +

              Port
              Table 4 Parameters for configuring a listener for a shared load balancer

              Parameter

              +
              @@ -285,7 +285,7 @@ @@ -310,7 +310,7 @@ @@ -345,7 +345,7 @@ @@ -370,8 +370,8 @@ - @@ -463,8 +463,8 @@ @@ -487,7 +487,7 @@ - diff --git a/docs/elb/umn/elb_ug_jt_0007.html b/docs/elb/umn/elb_ug_jt_0007.html index bb0bba001..97b59ff7c 100644 --- a/docs/elb/umn/elb_ug_jt_0007.html +++ b/docs/elb/umn/elb_ug_jt_0007.html @@ -231,7 +231,7 @@
            8. Click Next: Confirm.
            9. Confirm the configuration and click Submit.

              10. Adding a UDP Listener to a Shared Load Balancer

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. Locate the load balancer and click its name.
              5. Under Listeners, click Add Listener. Configure the parameters based on Table 4. -
              Table 4 Parameters for configuring a listener for a shared load balancer

              Parameter

              Description

              Access Control

              Specifies how access to the listener is controlled. The following options are available (for details, see Access Control):

              -
              • All IP addresses
              • Blacklist
              • Whitelist
              +
              • All IP addresses
              • Blacklist
              • Whitelist

              Whitelist

              Idle Timeout

              Specifies the length of time for a connection to keep alive, in seconds. If no request is received within this period, the load balancer closes the connection and establishes a new one with the client when the next request arrives.

              -

              The idle timeout duration ranges from 10 to 4000.

              +

              The idle timeout duration ranges from 10 to 4000.

              300

              Backend Server Group

              Specifies a group of servers with the same features to receive requests from the load balancer. Two options are available:

              -
              • Create new
              • Use existing
                NOTE:

                To associate an existing backend server group, ensure that it is not in use. Select the backend server group with the correct protocol. For example, if the frontend protocol is TCP, the backend protocol must be TCP.

                +
                • Create new
                • Use existing
                  NOTE:

                  To associate an existing backend server group, ensure that it is not in use. Select the backend server group with the correct protocol. For example, if the frontend protocol is TCP, the backend protocol must be TCP.

              Load Balancing Algorithm

              Specifies the algorithm used by the load balancer to distribute traffic. The following options are available:

              -
              • Weighted round robin: Requests are routed to different servers based on their weights, which indicate server processing performance. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests.
              • Weighted least connections: This algorithm is designed based on the least connections algorithm that uses the number of active connections to each backend server to make its load balancing decision. In addition to the number of connections, each server is assigned a weight based on its capacity. Requests are routed to the server with the lowest connections-to-weight ratio.
              • Source IP hash: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hash key, and all backend servers are numbered. The generated key allocates the client to a particular server. This allows requests from different clients to be routed based on source IP addresses and ensures that a client is directed to the same server that it was using previously.
              -
              NOTE:
              • Choose an appropriate algorithm based on your requirements for better traffic distribution.
              • For Weighted round robin or Weighted least connections, no requests will be routed to a server with a weight of 0.
              +
              • Weighted round robin: Requests are routed to different servers based on their weights, which indicate server processing performance. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests.
              • Weighted least connections: This algorithm is designed based on the least connections algorithm that uses the number of active connections to each backend server to make its load balancing decision. In addition to the number of connections, each server is assigned a weight based on its capacity. Requests are routed to the server with the lowest connections-to-weight ratio.
              • Source IP hash: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hash key, and all backend servers are numbered. The generated key allocates the client to a particular server. This allows requests from different clients to be routed based on source IP addresses and ensures that a client is directed to the same server that it was using previously.
              +
              NOTE:
              • Choose an appropriate algorithm based on your requirements for better traffic distribution.
              • For Weighted round robin or Weighted least connections, no requests will be routed to a server with a weight of 0.

              Weighted round robin

              @@ -388,7 +388,7 @@

              Sticky Session Type

              Specifies the type of sticky sessions. Source IP address is the only choice available when TCP or UDP is used as the frontend protocol.

              +

              Specifies the type of sticky sessions. Source IP address is the only choice available when TCP or UDP is used as the frontend protocol.

              Source IP address: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hashing key, and all backend servers are numbered. The system allocates the client to a particular server based on the generated key. This allows requests from the same IP address to be forwarded to the same backend server.

              Source IP address

              @@ -397,7 +397,7 @@

              Stickiness Duration (min)

              Specifies the minutes that sticky sessions are maintained. You can enable sticky sessions only if you select Weighted round robin for Load Balancing Algorithm.

              -
              • Stickiness duration at Layer 4: 1 to 60
              • Stickiness duration at Layer 7: 1 to 1440
              +
              • Stickiness duration at Layer 4: 1 to 60
              • Stickiness duration at Layer 7: 1 to 1440

              20

              Specifies the health check URL, which is the destination on backend servers for health checks. This parameter is available only when the health check protocol is HTTP. The path must start with a slash (/) and can contain 1 to 80 characters.

              The path can contain letters, digits, hyphens (-), slashes (/), periods (.), percent signs (%), ampersands (&), and the following special characters: _~';@$*+,=!:()

              NOTE:

              Example:

              -

              If the URL is http://www.example.com/chat/try/, the health check path is /chat/try/.

              -

              If the URL is http://192.168.63.187:9096/chat/index.html, the health check path is /chat/index.html.

              +

              If the URL is http://www.example.com/chat/try/, the health check path is /chat/try/.

              +

              If the URL is http://192.168.63.187:9096/chat/index.html, the health check path is /chat/index.html.

              /index.html

              @@ -473,7 +473,7 @@

              Interval (s)

              Specifies the maximum time between two consecutive health checks, in seconds.

              -

              The interval ranges from 1 to 50.

              +

              The interval ranges from 1 to 50.

              5

              Maximum Retries

              Specifies the maximum number of health check retries. The value ranges from 1 to 10.

              +

              Specifies the maximum number of health check retries. The value ranges from 1 to 10.

              3
              Table 4 Parameters for configuring a listener for a shared load balancer

              Parameter

              +
              @@ -422,21 +422,21 @@ - - diff --git a/docs/elb/umn/elb_ug_jt_0008.html b/docs/elb/umn/elb_ug_jt_0008.html index c24f5d46d..6286394c8 100644 --- a/docs/elb/umn/elb_ug_jt_0008.html +++ b/docs/elb/umn/elb_ug_jt_0008.html @@ -49,7 +49,7 @@ -
              Table 4 Parameters for configuring a listener for a shared load balancer

              Parameter

              Description

              Interval (s)

              Specifies the maximum time between two consecutive health checks, in seconds.

              -

              The interval ranges from 1 to 50.

              +

              The interval ranges from 1 to 50.

              5

              Timeout (s)

              Specifies the maximum time required for waiting for a response from the health check, in seconds. The timeout duration ranges from 1 to 50.

              +

              Specifies the maximum time required for waiting for a response from the health check, in seconds. The timeout duration ranges from 1 to 50.

              3

              Maximum Retries

              Specifies the maximum number of health check retries. The value ranges from 1 to 10.

              +

              Specifies the maximum number of health check retries. The value ranges from 1 to 10.

              3

              Specifies the HTTPS listener to which requests are redirected.

              listener_HTTPS_443

              +

              listener-9ecd (HTTPS/443)

              Access Control

              @@ -309,7 +309,7 @@
            10. Click Next: Confirm.
            11. Confirm the configuration and click Submit.

              12. Adding an HTTP Listener to a Shared Load Balancer

              1. Log in to the management console.
              2. In the upper left corner of the page, click and select the desired region and project.
              3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
              4. Locate the load balancer and click its name.
              5. Under Listeners, click Add Listener. Configure the parameters based on Table 4. -
                Table 4 Parameters for configuring a listener for a shared enhanced load balancer

                Parameter

                +
                @@ -352,7 +352,7 @@ - @@ -556,7 +556,7 @@ - diff --git a/docs/elb/umn/elb_ug_jt_0009.html b/docs/elb/umn/elb_ug_jt_0009.html index 19dbea97f..f3d6f4e59 100644 --- a/docs/elb/umn/elb_ug_jt_0009.html +++ b/docs/elb/umn/elb_ug_jt_0009.html @@ -362,7 +362,7 @@
              6. Click Next: Confirm.
              7. Confirm the configuration and click Submit.

                8. Adding an HTTPS Listener to a Shared Load Balancer

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Under Listeners, click Add Listener. Configure the parameters based on Table 4. -
                Table 4 Parameters for configuring a listener for a shared load balancer

                Parameter

                Description

                Specifies the HTTPS listener to which requests are redirected.

                listener-9ecd (HTTPS/443)

                +

                listener-9ecd (HTTPS/443)

                Access Control

                @@ -531,7 +531,7 @@

                Health Check

                Specifies whether to enable health checks.

                -

                If the health check is enabled, click next to Advanced Settings to set health check parameters.

                +

                If the health check is enabled, click next to Advanced Settings to set health check parameters.

                N/A

                Health Check Port

                Specifies the port that will be used by the load balancer to check the health of backend servers. The port number ranges from 1 to 65535.

                +

                Specifies the port that will be used by the load balancer to check the health of backend servers. The port number ranges from 1 to 65535.

                NOTE:

                By default, the service port on each backend server is used. You can also specify a port for health checks.
                - diff --git a/docs/elb/umn/en-us_topic_0018127975.html b/docs/elb/umn/en-us_topic_0018127975.html index a29348fa9..056424947 100644 --- a/docs/elb/umn/en-us_topic_0018127975.html +++ b/docs/elb/umn/en-us_topic_0018127975.html @@ -97,7 +97,7 @@

                Checking the Health Check Configuration

                For a dedicated or shared load balancer, click the name of the load balancer to view its details. Navigate to Backend Server Groups and then click the name of the server group. In the Basic Information area, to the right of Health Check, click Configure. Check the following parameters:

                -
                • Heath Check Protocol: The protocol used for health checks.
                • Heath Check Port: The port must be the one used on the backend server, and it cannot be changed. Check whether the health check port is in the listening state on the backend server. If the health check port is not in the listening state on the backend server, the backend server will be identified as unhealthy.
                • Path: If HTTP is used for health checks, you must check this parameter. A simple static HTML file is recommended.
                +
                • Health Check Protocol: The protocol used for health checks.
                • Health Check Port: The port must be the one used on the backend server, and it cannot be changed. Check whether the health check port is in the listening state on the backend server. If the health check port is not in the listening state on the backend server, the backend server will be identified as unhealthy.
                • Path: If HTTP is used for health checks, you must check this parameter. A simple static HTML file is recommended.
                • If the health check protocol is HTTP, the port and the path are used for health checks.
                • If the health check protocol is TCP, only the port is used for health checks.
                • If health check protocol is HTTP and the health check port is normal, change the path or change the health check protocol to TCP.
                • Enter an absolute path.

                  For example:

                  If the URL is http://www.example.com or http://192.168.63.187:9096, enter / as the health check path.

                  @@ -106,7 +106,7 @@
                -

                Checking Security Group Rules

                • Dedicated Load balancers
                  • TCP, HTTP, or HTTPS listeners: Verify that the inbound security group rule allows TCP traffic from the VPC where the dedicated load balancer resides to the backend server over the health check port.
                    • If the health check port is the same as the backend port, the inbound rule must allow traffic over the backend port, for example, port 80.
                    • If the port (port 80 as an example) for health check is different from that used by the backend server (port 443 as an example), inbound security group rules must allow traffic over both ports.

                      You can check the protocol and port in the Basic Information area of the backend server group.

                      +

                      Checking Security Group Rules

                      • Dedicated Load balancers
                        • TCP, HTTP, or HTTPS listeners: Verify that the inbound security group rule allows TCP traffic from the VPC where the dedicated load balancer resides to the backend server over the health check port.
                          • If the health check port is the same as the backend port, the inbound rule must allow traffic over the backend port, for example, port 80.
                          • If the port (port 80 as an example) for health check is different from that used by the backend server (port 443 as an example), inbound security group rules must allow traffic over both ports.

                            You can check the protocol and port in the Basic Information area of the backend server group.

                          Figure 2 Example inbound rule
                          diff --git a/docs/elb/umn/en-us_topic_0114694934.html b/docs/elb/umn/en-us_topic_0114694934.html index eeb6ae7ef..196bbeaad 100644 --- a/docs/elb/umn/en-us_topic_0114694934.html +++ b/docs/elb/umn/en-us_topic_0114694934.html @@ -12,7 +12,7 @@

                          If you add a forwarding policy that is the same as an existing one by calling APIs, there will be a conflict. Even if you delete the existing forwarding policy, the new forwarding policy is still faulty. Delete the newly-added forwarding policy and add a different one.

                      -

                      Adding a Forwarding Policy

                      1. Log in to the management console.
                      2. In the upper left corner of the page, click and select the desired region and project.
                      3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                      4. Locate the load balancer and click its name.
                      5. Click Listeners, locate the listener, and click its name.
                      6. Click on the right of the listener name and select Configure Forwarding Policy.

                        Alternatively, click Forwarding Policies on the right of the page.

                        +

                        Adding a Forwarding Policy

                        1. Log in to the management console.
                        2. In the upper left corner of the page, click and select the desired region and project.
                        3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                        4. Locate the load balancer and click its name.
                        5. Click Listeners, locate the listener, and click its name.
                        6. Click on the right of the listener name and select Configure Forwarding Policy.

                          Alternatively, click Forwarding Policies on the right of the page.

                        7. On the Forwarding Policies tab page, click Add Forwarding Policy.

                          Configure the parameters based on Table 1.

                        8. After the configuration is complete, click Save.
                        @@ -96,9 +96,9 @@ -
                - @@ -109,9 +109,9 @@ - - @@ -149,10 +149,10 @@
                Figure 1 Request forwarding

                In this figure, the system first searches for an exact match of the requested URL (/elb_gls/glossary.html). If there is no exact match, the system searches for a prefix match. If a match is found, the request is forwarded to backend server group 2 even if a regular expression match is also found, because the prefix match has a higher priority.

                -

                Modifying a Forwarding Policy

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, and click its name.
                6. Click on the right of the listener name and select Configure Forwarding Policy.

                  Alternatively, click Forwarding Policies in the right pane.

                  +

                  Modifying a Forwarding Policy

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. Click Listeners, locate the listener, and click its name.
                  6. Click on the right of the listener name and select Configure Forwarding Policy.

                    Alternatively, click Forwarding Policies in the right pane.

                  7. On the Forwarding Policies tab page, select the forwarding policy you want to modify and click Edit.
                  8. Modify the parameters and click Save.
                  -

                  Deleting a Forwarding Policy

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. Click Listeners, locate the listener, and click its name.
                  6. Click on the right of the listener name and select Configure Forwarding Policy.

                    Alternatively, click Forwarding Policies in the right pane.

                    +

                    Deleting a Forwarding Policy

                    1. Log in to the management console.
                    2. In the upper left corner of the page, click and select the desired region and project.
                    3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                    4. Locate the load balancer and click its name.
                    5. Click Listeners, locate the listener, and click its name.
                    6. Click on the right of the listener name and select Configure Forwarding Policy.

                      Alternatively, click Forwarding Policies in the right pane.

                    7. On the Forwarding Policies tab page, select the forwarding policy you want to delete and click Delete.
                    8. In the displayed dialog box, click Yes.
                  diff --git a/docs/elb/umn/en-us_topic_0118147668.html b/docs/elb/umn/en-us_topic_0118147668.html index 190fa789f..bc9ebcbc1 100644 --- a/docs/elb/umn/en-us_topic_0118147668.html +++ b/docs/elb/umn/en-us_topic_0118147668.html @@ -5,11 +5,11 @@

                  Load balancer EIPs are placed in the X-Forwarded-ELB-IP field in the HTTPS or HTTP header in the format of XX.XXX.XX.XXX, as shown below:

                  X-Forwarded-ELB-IP: XX.XXX.XX.XXX
                -

                Enabling the Function

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Under Listeners, click Add Listener.
                6. In the Add Listener dialog box, expand Advanced Settings and enable the function.
                7. Click OK.

                  This function can be enabled only for HTTPS or HTTP listeners.

                  +

                  Enabling the Function

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. Under Listeners, click Add Listener.
                  6. In the Add Listener dialog box, expand Advanced Settings and enable the function.
                  7. Click OK.

                    This function can be enabled only for HTTPS or HTTP listeners.

                  -

                  Disabling the Function

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. On the Listeners tab page, locate the listener, click next to the listener name, and select Modify Listener.
                  6. In the Modify Listener dialog box, expand Advanced Settings and disable the function.
                  +

                  Disabling the Function

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. On the Listeners tab page, locate the listener, click next to the listener name, and select Modify Listener.
                  6. In the Modify Listener dialog box, expand Advanced Settings and disable the function.
                  diff --git a/docs/elb/umn/en-us_topic_0118840332.html b/docs/elb/umn/en-us_topic_0118840332.html index 1d60a64a1..0843e4aaf 100644 --- a/docs/elb/umn/en-us_topic_0118840332.html +++ b/docs/elb/umn/en-us_topic_0118840332.html @@ -8,7 +8,7 @@

                  Prerequisites

                  • You have added an HTTPS listener.
                  • You have added an HTTP listener.
                  -

                  Creating Redirection to HTTPS

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. Locate the load balancer and click its name.
                  5. Click Listeners, locate the HTTP listener, and click its name.
                  6. On the Forwarding Policies tab page, click Add Forwarding Policy.
                    +

                    Creating Redirection to HTTPS

                    1. Log in to the management console.
                    2. In the upper left corner of the page, click and select the desired region and project.
                    3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                    4. Locate the load balancer and click its name.
                    5. Click Listeners, locate the HTTP listener, and click its name.
                    6. On the Forwarding Policies tab page, click Add Forwarding Policy.
                Table 4 Parameters for configuring a listener for a shared enhanced load balancer

                Parameter

                +
                @@ -439,7 +439,7 @@ @@ -658,8 +658,8 @@

                This parameter is available when the health check protocol is HTTP. The path can contain 1 to 80 characters and must start with a slash (/).

                The path can contain letters, digits, hyphens (-), slashes (/), periods (.), question marks (?), percent signs (%), ampersands (&), and underscores (_).

                NOTE:

                Example:

                -

                If the URL is http://www.example.com/chat/try/, the health check path is /chat/try/.

                -

                If the URL is http://192.168.63.187:9096/chat/index.html, the health check path is /chat/index.html.

                +

                If the URL is http://www.example.com/chat/try/, the health check path is /chat/try/.

                +

                If the URL is http://192.168.63.187:9096/chat/index.html, the health check path is /chat/index.html.

                - - diff --git a/docs/elb/umn/elb_ug_pe_0000.html b/docs/elb/umn/elb_ug_pe_0000.html index e9bcf50cc..714964774 100644 --- a/docs/elb/umn/elb_ug_pe_0000.html +++ b/docs/elb/umn/elb_ug_pe_0000.html @@ -1,7 +1,7 @@

                Quotas

                -

                What Is Quota?

                Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

                +

                What Is Quota?

                Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

                If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.

                How Do I View My Quotas?

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. In the upper right corner of the page, click .

                  The Service Quota page is displayed.

                  diff --git a/docs/elb/umn/elb_ug_zs_0001.html b/docs/elb/umn/elb_ug_zs_0001.html index b9f4f6fe1..70126044e 100644 --- a/docs/elb/umn/elb_ug_zs_0001.html +++ b/docs/elb/umn/elb_ug_zs_0001.html @@ -1,7 +1,7 @@

                  Introduction to Certificates

                  -
                  ELB supports two types of certificates. If you need an HTTPS listener, you need to bind a server certificate to it. To enable mutual authentication, you also need to bind a CA certificate to the listener.
                  • Server certificate: used for SSL handshake negotiations if an HTTPS listener is used. Both the certificate content and private key are required.
                  • CA certificate: issued by a certificate authority (CA) and used to verify the certificate issuer. If HTTPS mutual authentication is required, HTTPS connections can be established only when the client provides a certificate issued by a specific CA.
                  +
                  ELB supports two types of certificates. If you need an HTTPS listener, you need to bind a server certificate to it. To enable mutual authentication, you also need to bind a CA certificate to the listener.
                  • Server certificate: used for SSL handshake negotiations if an HTTPS listener is used. Both the certificate content and private key are required.
                  • CA certificate: issued by a certificate authority (CA) and used to verify the certificate issuer. If HTTPS mutual authentication is required, HTTPS connections can be established only when the client provides a certificate issued by a specific CA.

                  Precautions

                  • A certificate can be used by multiple load balancers but only needs to be uploaded to each load balancer once.
                  • If a certificate is used for SNI, you need to specify a domain name for the certificate, and the domain name must be the same as that in the certificate.
                  • For each certificate type, a listener can have only one certificate by default, but a certificate can be bound to more than one listener. If SNI is enabled for the listener, multiple server certificates can be bound.
                  • Only original certificates are supported. That is to say, you cannot encrypt your certificates.
                  • You do not need to configure certificates for both the shared load balancer and the associated backend servers. If you configure a certificate for backend servers, HTTPS listeners cannot be added to the load balancer. In this case, you can add a TCP listener to transparently transmit HTTPS traffic to backend servers. This restriction does not apply to dedicated load balancers.
                  • You can use self-signed certificates. However, note that self-signed certificates pose security risks. Therefore, it is recommended that you use certificates issued by third parties.
                  • ELB supports certificates only in PEM format. If you have a certificate in any other format, you must convert it to a PEM-encoded certificate.
                  • If a certificate has expired, you need to manually replace or delete it.
                  diff --git a/docs/elb/umn/elb_ug_zs_0004.html b/docs/elb/umn/elb_ug_zs_0004.html index 94a9d6436..b00620542 100644 --- a/docs/elb/umn/elb_ug_zs_0004.html +++ b/docs/elb/umn/elb_ug_zs_0004.html @@ -42,7 +42,7 @@ Content of the private key private

                  Modifying a Certificate

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Certificates.
                  5. Locate the certificate and click Modify in the Operation column.
                  6. Modify the parameters as required.
                  7. Click OK.

                  Deleting a Certificate

                  Only certificates that are not in use can be deleted.

                  -
                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Certificates.
                  5. Locate the certificate and click Delete in the Operation column.
                  6. Click Yes.
                  +
                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Certificates.
                  5. Locate the certificate and click Delete in the Operation column.
                  6. Click Yes.
                  diff --git a/docs/elb/umn/elb_ug_zs_0006.html b/docs/elb/umn/elb_ug_zs_0006.html index f4eeff4e8..1fb1d8d24 100644 --- a/docs/elb/umn/elb_ug_zs_0006.html +++ b/docs/elb/umn/elb_ug_zs_0006.html @@ -3,7 +3,7 @@

                  Querying a Listener by Certificate

                  Scenarios

                  You need to quickly view details of the listener to which a certificate is bound.

                  -

                  Procedure

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select the desired region and project.
                  3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                  4. In the navigation pane on the left, choose Certificates.
                  5. In the certificate list, click the listener name in the Listener (Frontend Protocol/Port) column to view its details.

                    If there are more than 5 listeners, no listener is displayed in the Listener (Frontend Protocol/Port) column. Click View All. On the displayed page, click Listeners, locate the listener, and click its name to view it details.

                    +

                    Procedure

                    1. Log in to the management console.
                    2. In the upper left corner of the page, click and select the desired region and project.
                    3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                    4. In the navigation pane on the left, choose Certificates.
                    5. In the certificate list, click the listener name in the Listener (Frontend Protocol/Port) column to view its details.

                      If there are more than 5 listeners, no listener is displayed in the Listener (Frontend Protocol/Port) column. Click View All. On the displayed page, click Listeners, locate the listener, and click its name to view it details.

                  diff --git a/docs/elb/umn/en-us_topic_0000001794660385.html b/docs/elb/umn/en-us_topic_0000001794660385.html index 1b79fa2a6..fbcf30568 100644 --- a/docs/elb/umn/en-us_topic_0000001794660385.html +++ b/docs/elb/umn/en-us_topic_0000001794660385.html @@ -1,7 +1,7 @@

                  Transfer Client IP Address (Dedicated Load Balancers)

                  -

                  Transfer Client IP Address

                  If you enable Transfer Client IP Address, your load balancer will use the IP address of the client to access the backend server.

                  +

                  Transfer Client IP Address

                  If you enable Transfer Client IP Address, your load balancer will use the IP address of the client to access the backend server.

                  Table 1 lists whether you can enable or disable the transfer client IP address function.

                Table 4 Parameters for configuring a listener for a shared load balancer

                Parameter

                Description

                Access Control

                Specifies how access to the listener is controlled. The following options are available (for details, see Access Control):

                -
                • All IP addresses
                • Blacklist
                • Whitelist
                +
                • All IP addresses
                • Blacklist
                • Whitelist

                Whitelist

                /index.html

                @@ -668,21 +668,21 @@

                Interval (s)

                Specifies the maximum time between two consecutive health checks, in seconds.

                -

                The interval ranges from 1 to 50.

                +

                The interval ranges from 1 to 50.

                5

                Timeout (s)

                Specifies the maximum time required for waiting for a response from the health check, in seconds. The timeout duration ranges from 1 to 50.

                +

                Specifies the maximum time required for waiting for a response from the health check, in seconds. The timeout duration ranges from 1 to 50.

                3

                Maximum Retries

                Specifies the maximum number of health check retries. The value ranges from 1 to 10.

                +

                Specifies the maximum number of health check retries. The value ranges from 1 to 10.

                3
                Table 1 Transfer client IP address

                Listener Type

                @@ -30,7 +30,7 @@
                -

                Constraints

                • If you enable Transfer Client IP Address, a server cannot be used as both the client and the backend server.

                  If the client and the backend server are using the same server and the Transfer Client IP Address option is enabled, the backend server will think the packet is sent by itself but not from the client and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.

                  +

                  Constraints

                  • If you enable Transfer Client IP Address, a server cannot serve as both a backend server and a client.

                    If the client and the backend server are using the same server and the Transfer Client IP Address option is enabled, the backend server will think the packet is sent by itself but not from the client and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.

                  • After this function is enabled, unidirectional download or push traffic may be interrupted when backend servers are being migrated. After the backend servers are migrated, retransmit the packets to restore the traffic.
                  • If you add IP addresses as backend servers, the source IP addresses of the clients cannot be passed to these servers.

                  Alternatives for Obtaining the IP Address of the Client

                  You can obtain the IP address of a client in one of the ways listed in Table 2.

                  diff --git a/docs/elb/umn/en-us_topic_0015479966.html b/docs/elb/umn/en-us_topic_0015479966.html index d9d6e0b19..a4abf5f5a 100644 --- a/docs/elb/umn/en-us_topic_0015479966.html +++ b/docs/elb/umn/en-us_topic_0015479966.html @@ -1,21 +1,21 @@

                  What Is ELB?

                  -

                  Elastic Load Balancing (ELB) automatically distributes incoming traffic across multiple backend servers based on the listening rules you configure. ELB expands the service capabilities of your applications and improves their availability by eliminating single points of failure (SPOFs).

                  +

                  Elastic Load Balancing (ELB) automatically distributes incoming traffic across multiple backend servers based on the listening rules you configure. ELB expands the service capabilities of your applications and improves their availability by eliminating single points of failure (SPOFs).

                  As shown in the example in the following figure, ELB distributes incoming traffic to three application servers, and each server processes one third of the requests. ELB also provides health checks, which can detect unhealthy servers. Traffic is distributed only to servers that are running normally, improving the availability of applications.

                  Figure 1 Using a load balancer

                  ELB Components

                  ELB consists of the following components:

                  -
                  • Load balancer: distributes incoming traffic across backend servers in one or more availability zones (AZs).
                  • Listener: uses the protocol and port you specify to check for requests from clients and route the requests to associated backend servers based on the listening rules and forwarding policies you configure. You can add one or more listeners to a load balancer.
                  • Backend server group: contains one or more backend servers to receive requests routed by the listener. You need to add at least one backend server to a backend server group.

                    You can set a weight for each backend server based on their performance.

                    -

                    You can also configure health checks for a backend server group to check the health of each backend server. When a backend server is unhealthy, the load balancer stops routing new requests to this server.

                    +
                    • A load balancer distributes incoming traffic across multiple backend servers in one or more AZs.
                    • A listener uses the protocol and port you specify to check requests from clients and route the requests to associated backend servers based on the routing policies and forwarding policies you configure. You can add one or more listeners to a load balancer.
                    • A backend server group uses the protocol and port you specify to receive the requests from the load balancer and route them to one or more backend servers. You need to add at least one backend server to a backend server group.

                      You can set a weight for each backend server based on their performance.

                      +

                      You can also configure health checks for a backend server group to check the health of each backend server. When a backend server is unhealthy, the load balancer stops routing new requests to it.

                  Figure 2 ELB components
                  -

                  Load Balancer Types

                  ELB provides shared load balancers and dedicated load balancers.

                  +

                  Load Balancer Types

                  ELB provides dedicated load balancers and shared load balancers.

                  Figure 3 Load balancer types
                  • Dedicated load balancers have exclusive use of underlying resources, so that the performance of a dedicated load balancer is not affected by other load balancers. In addition, there are a wide range of specifications available for selection.
                  • In the eu-de region, you can create both dedicated and shared load balancers, and you can create either type of load balancers on the management console or by calling APIs.
                  • In the eu-nl region, you can only create dedicated load balancers, either on the console or by calling APIs.
                  -
                  • Shared load balancers are deployed in clusters and share underlying resources, so that the performance of a load balancer is affected by other load balancers. Shared load balancers were previously named enhanced load balancers.
                  +
                  • Shared load balancers are deployed in clusters. They share underlying resources, so the performance of a load balancer is affected by other load balancers. Shared load balancers were previously named enhanced load balancers.

                  For details about the differences between dedicated and shared load balancers, see Differences Between Dedicated and Shared Load Balancers.

                  Accessing ELB

                  You can use either of the following methods to access ELB:

                  diff --git a/docs/elb/umn/en-us_topic_0015479967.html b/docs/elb/umn/en-us_topic_0015479967.html index 81e64855c..d39581763 100644 --- a/docs/elb/umn/en-us_topic_0015479967.html +++ b/docs/elb/umn/en-us_topic_0015479967.html @@ -94,7 +94,7 @@

                Description

                Example Value

                +

                Example Value

                N/A

                +

                N/A

                N/A

                +

                N/A

                /elb/index.html

                /index.html

                Exact match

                +

                Exact match

                /elb/index.html

                +

                /elb/index.html

                √
                Table 1 Configuring parameters for redirection

                Parameter

                Setting

                @@ -31,13 +31,13 @@
              8. After the forwarding policy is added, click Save.

                9. -
                • If requests to an HTTP listener are redirected, the listener will become invalid, but access control to the listener will still take effect.
                • If you create a redirect for an HTTP listener, the backend server will return HTTP 301 Move Permanently to the clients.
                +
                • If requests to an HTTP listener are redirected, the listener will become invalid, but access control to the listener will still take effect.
                • If you create a redirect for an HTTP listener, the backend server will return HTTP 301 Move Permanently to the clients.

                -

                Modifying Redirection to HTTPS

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the HTTP listener, and click its name.
                6. On the Forwarding Policies tab page, click Edit.
                7. You can change the HTTPS listener to which requests are redirected as required.
                8. Click Save.
                +

                Modifying Redirection to HTTPS

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the HTTP listener, and click its name.
                6. On the Forwarding Policies tab page, click Edit.
                7. You can change the HTTPS listener to which requests are redirected as required.
                8. Click Save.
                -

                Deleting Redirection to HTTPS

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, and click its name.
                6. On the Forwarding Policies tab page, click Delete on the right of the target forwarding policy.
                7. In the displayed dialog box, click Yes.
                +

                Deleting Redirection to HTTPS

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, and click its name.
                6. On the Forwarding Policies tab page, click Delete on the right of the target forwarding policy.
                7. In the displayed dialog box, click Yes.
                diff --git a/docs/elb/umn/en-us_topic_0150301849.html b/docs/elb/umn/en-us_topic_0150301849.html index 44edd8f50..4c7fce6c3 100644 --- a/docs/elb/umn/en-us_topic_0150301849.html +++ b/docs/elb/umn/en-us_topic_0150301849.html @@ -5,9 +5,9 @@

                Constraints

                You can enable HTTP/2 only for HTTPS listeners.

                -

                Enabling HTTP/2 When Adding a Listener

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Under Listeners, click Add Listener.
                6. In the Add Listener dialog box, set Frontend Protocol to HTTPS.
                7. Expand Advanced Settings and enable HTTP/2.
                8. Walk through the steps, set relevant parameters and in the end click Submit.
                +

                Enabling HTTP/2 When Adding a Listener

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Under Listeners, click Add Listener.
                6. In the Add Listener dialog box, set Frontend Protocol to HTTPS.
                7. Expand Advanced Settings and enable HTTP/2.
                8. Walk through the steps, set relevant parameters and in the end click Submit.
                -

                Enabling or Disabling HTTP/2 When Modifying a Listener

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, click next to the listener name, and select Modify Listener.
                6. In the Modify Listener dialog box, expand Advanced Settings and enable or disable HTTP/2.
                7. Confirm the parameters, and click Next.
                8. Click Finish.
                9. Click OK.
                +

                Enabling or Disabling HTTP/2 When Modifying a Listener

                1. Log in to the management console.
                2. In the upper left corner of the page, click and select the desired region and project.
                3. Click in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
                4. Locate the load balancer and click its name.
                5. Click Listeners, locate the listener, click next to the listener name, and select Modify Listener.
                6. In the Modify Listener dialog box, expand Advanced Settings and enable or disable HTTP/2.
                7. Confirm the parameters, and click Next.
                8. Click Finish.
                9. Click OK.
                diff --git a/docs/elb/umn/en-us_topic_0171274900.html b/docs/elb/umn/en-us_topic_0171274900.html index 3dea26e0c..b549c6401 100644 --- a/docs/elb/umn/en-us_topic_0171274900.html +++ b/docs/elb/umn/en-us_topic_0171274900.html @@ -10,38 +10,38 @@

                You can grant permissions by using roles and policies.

                • Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
                • Policies: A fine-grained authorization strategy provided by IAM to assign permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant ELB users only permissions to manage a certain type of resources. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by ELB, see Elastic Load Balance API Reference.
                Table 1 lists all the system-defined permissions for ELB. -
                Table 1 System-defined permissions for ELB

                Role/Policy Name

                +
                - - - - - - - - - - - @@ -50,266 +50,266 @@

                Table 2 describes common operations supported by each system policy of ELB.

                -
                Table 1 System-defined permissions for ELB

                Role/Policy Name

                Description

                +

                Description

                Type

                +

                Type

                ELB FullAccess

                +

                ELB FullAccess

                Permissions: all permissions on ELB resources

                +

                Permissions: all permissions on ELB resources

                Scope: project-level service

                System-defined policy

                +

                System-defined policy

                ELB ReadOnlyAccess

                +

                ELB ReadOnlyAccess

                Permissions: read-only permissions on ELB resources

                +

                Permissions: read-only permissions on ELB resources

                Scope: project-level service

                System-defined policy

                +

                System-defined policy

                ELB Administrator

                +

                ELB Administrator

                Permissions: all permissions on ELB resources. To be granted this permission, users must also have the Tenant Administrator, VPC Administrator, CES Administrator, Server Administrator and Tenant Guest permissions.

                +

                Permissions: all permissions on ELB resources. To be granted this permission, users must also have the Tenant Administrator, VPC Administrator, CES Administrator, Server Administrator and Tenant Guest permissions.

                Scope: project-level service

                NOTE:

                If your account has applied for fine-grained permissions, configure fine-grained policies for ELB system permissions, instead of ELB Administrator policies.

                System-defined role

                +

                System-defined role
                Table 2 Common operations supported by system-defined policies

                Operation

                +
                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/elb/umn/en-us_topic_0287737145.html b/docs/elb/umn/en-us_topic_0287737145.html index 6933f25d4..7d951fad3 100644 --- a/docs/elb/umn/en-us_topic_0287737145.html +++ b/docs/elb/umn/en-us_topic_0287737145.html @@ -181,9 +181,9 @@ - -
                Table 2 Common operations supported by system-defined policies

                Operation

                ELB FullAccess

                +

                ELB FullAccess

                ELB ReadOnlyAccess

                +

                ELB ReadOnlyAccess

                ELB Administrator

                +

                ELB Administrator

                Creating a load balancer

                +

                Creating a load balancer

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying a load balancer

                +

                Querying a load balancer

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Querying a load balancer and associated resources

                +

                Querying a load balancer and associated resources

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Querying load balancers

                +

                Querying load balancers

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Modifying a load balancer

                +

                Modifying a load balancer

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Deleting a load balancer

                +

                Deleting a load balancer

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Adding a listener

                +

                Adding a listener

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying a listener

                +

                Querying a listener

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Modifying a listener

                +

                Modifying a listener

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Deleting a listener

                +

                Deleting a listener

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Adding a backend server group

                +

                Adding a backend server group

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying a backend server group

                +

                Querying a backend server group

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Modifying a backend server group

                +

                Modifying a backend server group

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Deleting a backend server group

                +

                Deleting a backend server group

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Adding a backend server

                +

                Adding a backend server

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying a backend server

                +

                Querying a backend server

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Modifying a backend server

                +

                Modifying a backend server

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Deleting a backend server

                +

                Deleting a backend server

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Configuring a health check

                +

                Configuring a health check

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying a health check

                +

                Querying a health check

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Modifying a health check

                +

                Modifying a health check

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Disabling a health check

                +

                Disabling a health check

                Supported

                +

                Supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Assigning an EIP

                +

                Assigning an EIP

                Not supported

                +

                Not supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Binding an EIP to a load balancer

                +

                Binding an EIP to a load balancer

                Not supported

                +

                Not supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Querying an EIP

                +

                Querying an EIP

                Supported

                +

                Supported

                Supported

                +

                Supported

                Supported

                +

                Supported

                Unbinding an EIP from a load balancer

                +

                Unbinding an EIP from a load balancer

                Not supported

                +

                Not supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Viewing metrics

                +

                Viewing metrics

                Not supported

                +

                Not supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                Viewing access logs

                +

                Viewing access logs

                Not supported

                +

                Not supported

                Not supported

                +

                Not supported

                Supported

                +

                Supported

                New HTTP and HTTPS connections

                1,000 + 50 x 10 = 1,500

                +

                1,000 + 50 × 10 = 1,500

                1,000 + 150 x 10 = 2,500

                +

                1,000 + 150 × 10 = 2,500

                Description

                @@ -201,7 +201,7 @@

                Table 6 and Table 7 list the fixed specifications of dedicated load balancers.

                -
                Table 6 Fixed specifications for a network load balancer (TCP/UDP)

                Type

                +
                @@ -283,7 +283,7 @@
                Table 6 Fixed specifications for a network load balancer (TCP/UDP)

                Specification

                Maximum Connections

                -
                Table 7 Fixed specifications for an application load balancer (HTTP/HTTPS)

                Type

                +
                Table 7 Fixed specifications for an application load balancer (HTTP/HTTPS)

                Specification

                Maximum Connections