diff --git a/docs/elb/umn/elb_billing_0003.html b/docs/elb/umn/elb_billing_0003.html index 96bc8fbb1..305f7b9bc 100644 --- a/docs/elb/umn/elb_billing_0003.html +++ b/docs/elb/umn/elb_billing_0003.html @@ -33,43 +33,46 @@

Unit price × Required duration

+

Specifications

+ +

You are charged by each specification you select.

+ +

Pay-per-use

+ +

Unit price × Required duration

+ +

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

-
- @@ -95,18 +97,10 @@ - - - -
Table 2 Billing items

Billing Mode

+
- - - - - - - - - - -
Table 2 Billing items

Billing Mode

Specifications

+

Specifications

LCU

-

Load Balancer

+

Billing Item

Pay-per-use

+

Pay-per-use

Elastic

+

Elastic

√

-

√

+

LCU + Load balancer

Pay-per-use

+

Pay-per-use

Fixed

+

Fixed

√

-

×

+

Specifications
-
  • Y indicates that the billing item is involved. × indicates that the billing item is not involved.
  • If you bind an EIP to a load balancer, you will also be charged for the EIP and the bandwidth used by the EIP.
+

If you bind an EIP to a load balancer, you will also be charged for the EIP and the bandwidth used by the EIP.

LCU Pricing

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

@@ -85,8 +88,7 @@

Pay-per-use

-

+

Pay-per-use

Elastic

You are charged for how many LCUs you use.

Fixed

-

For stable traffic

-

You are charged for the LCUs based on each fixed specification you select.

-
-
+

If you deploy a dedicated load balancer in multiple AZs, its performance will multiply as the number of AZs increases.

LCU Billing for Elastic Specifications

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

@@ -147,56 +141,159 @@

Table 5 lists the LCU performance supported by different protocols.

+

For TCP and UDP protocols, it has 3 LCU dimensions, the final LCU dimension will use the dimension which uses the most LCUs after calculation.

+

For HTTP and HTTPS protocol, it has 4 LCU dimensions, the final LCU dimension will use the dimension which uses the most LCUs after calculation.

-
Table 5 LCU performance supported by different protocols

Protocol

+
- - - - - - - - - - - - - - - - - - -
Table 5 LCU performance supported by different protocols

Protocol

New Connections per Second

+

New Connections per Second

Maximum Concurrent Connections per Minute

+

Maximum Concurrent Connections per Minute

Processed Bytes

+

Processed Bytes

Rule Evaluations per Second

+

Rule Evaluations per Second

TCP

+

TCP

800

+

800

100,000

+

100,000

1 GB

+

1 GB

-

+

-

UDP

+

UDP

400

+

400

50,000

+

50,000

1 GB

+

1 GB

-

+

-

HTTP/HTTPS

+

HTTP/HTTPS

25

+

25

3,000

+

3,000

1 GB

+

1 GB

1,000

+

1,000
+

Billing Examples

A pricing example for a network load balancer

+

Assume your network load balancer establishes 1,000 new TCP connections per second and handles a maximum of 180,000 concurrent connections per minute. The bytes processed by your load balancer is 1,000 KB per second.

+

The LCU price is calculated as the table shown below.

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 6 LCU calculation

Dimension

+

Example

+

LCUs

+

Rounded Up LCUs

+

New connections per second

+

1,000

+

1,000 ÷ 800 = 1.25

+

2

+

Maximum concurrent connections per minute

+

180,000

+

180,000 ÷ 100,000 = 1.8

+

2

+

Processed bytes per hour

+

1,000 KB/s × 60s × 60 minutes = 3.6 GB

+

3.6 ÷ 1 = 3.6

+

4

+
+
+

In this example, the processed bytes dimension consumes the most LCUs (4 LCUs). Therefore, the LCU price is calculated based on the number of LCUs consumed by processed bytes.

+

A pricing example for an application load balancer

+

Assume your application load balancer establishes 1,000 new HTTP/HTTPS connections per second and handles a maximum of 180,000 concurrent connections per minute. A client sends an average of 400 requests per second and the bytes processed by this load balancer is 1,000 KB per second. You have configured 20 forwarding rules for your load balancer to route requests.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 7 LCU calculation

Dimension

+

Example

+

LCUs

+

Rounded Up LCUs

+

New connections per second

+

1,000

+

1,000 ÷ 25 = 40

+

40

+

Maximum concurrent connections per minute

+

180,000

+

180,000 ÷ 3,000 = 60

+

60

+

Processed bytes per hour

+

1,000 KB/s × 60s × 60 minutes = 3.6 GB

+

3.6 ÷ 1 = 3.6

+

4

+

Rule evaluations per second

+

Rule evaluations are calculated as:

+

Rule evaluations = QPS × (Number of processed rules – 10)

+

= 400 × (20 – 10) = 4,000

+

4,000 ÷ 1,000 = 4

+

4

+
+
+

In this example, the maximum concurrent connection dimension consumes the most LCUs (60 LCUs). So the LCU price is calculated based on the LCUs consumed by the maximum concurrent connections.

+

Load Balancer Pricing

You are charged for how long each load balancer is retained in your account. If the load balancer is used for less than 1 hour, you will be charged for the actual duration, accurate to seconds. The billing cycle is from the time when the dedicated load balancer is created to the time when it is deleted.

Only load balancers with elastic specifications in pay-per-use billing mode are charged.

diff --git a/docs/elb/umn/elb_ug_fz_0007.html b/docs/elb/umn/elb_ug_fz_0007.html index 325e88ff5..51c5ffcfa 100644 --- a/docs/elb/umn/elb_ug_fz_0007.html +++ b/docs/elb/umn/elb_ug_fz_0007.html @@ -2,7 +2,7 @@

Configuring Modification Protection or Deletion Protection for a Load Balancer

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

-
  • Deletion protection: prevents your load balancers from being deleted by accident. Disable Deletion Protection If you want to delete a load balancer.
  • Modification protection: prevents your load balancers from being modified by accident. Disable Modification Protection if you want to modify or delete a load balancer.
+
  • Deletion protection: prevents your load balancers from being deleted by accident. Disable Deletion Protection if you want to delete a load balancer.
  • Modification protection: prevents your load balancers from being modified by accident. Disable Modification Protection if you want to modify or delete a load balancer.

Enabling or Disabling Deletion Protection

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

    If your load balancer is managed by CCE, deleting the load balancer will affect the running of the CCE cluster.

  6. After deletion protection is enabled, the load balancer cannot be deleted.
diff --git a/docs/elb/umn/en-us_topic_0287737145.html b/docs/elb/umn/en-us_topic_0287737145.html index 7d951fad3..6ab3c0027 100644 --- a/docs/elb/umn/en-us_topic_0287737145.html +++ b/docs/elb/umn/en-us_topic_0287737145.html @@ -48,7 +48,7 @@
-

Elastic Specifications

If your service traffic fluctuates greatly, you can choose elastic specifications and select network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS), or both that best meet your service needs.

+

Elastic Specifications

If your service traffic fluctuates greatly, you can choose elastic specifications and select either network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS), or both that best meet your service needs.

The listener protocol must match the load balancing type. For example, if you select application load balancing (HTTP/HTTPS), you can only add an HTTP or HTTPS listener to this load balancer.

Table 2 describes the dimensions about elastic specifications. When your traffic exceeds the specifications defined in Table 3, new requests will be discarded.