Elastic Load Balancing Pricing

价格计算器

Free Tier

ELB Free Tier is available in the Amazon Web Services China (Ningxia) Region operated by NWCD and Amazon Web Services China (Beijing) Region operated by Sinnet. The Free Tier includes 750 Hours per month shared between Classic, Application and Network load balancers, 15 GB of data processing for Classic load balancers, 15 LCUs for Application load balancers, 15 LCUs for Network load balancers each month for one year.

Classic Load Balancer Pricing

With Elastic Load Balancing, you only pay for what you use. You are charged for each hour or partial hour your elastic load balancer is running and for each GB of data transferred through your elastic load balancer. You will be charged at the end of each month for your Elastic Load Balancing resources actually consumed.

Partial hours are billed as full hours. Regular Amazon EC2 service fees apply and are billed separately.

China (Ningxia) Region

¥ 0.156 per elastic load balancer-hour (or partial hour)

¥ 0.072 per GB of data processed by an elastic load balancer

China (Beijing) Region

¥ 0.156 per elastic load balancer-hour (or partial hour)

¥ 0.072 per GB of data processed by an elastic load balancer

Pricing example

Pricing example 1:

A medium-sized website running on 10 Amazon EC2 instances in the Amazon Web Services China (Ningxia) Region could use one load balancer to balance incoming traffic. If the load balancer ended up transferring 100 GB of data over a 30 day period, the monthly charge would amount to ¥ 112.32 (or ¥ 0.156 per hour x 24 hours per day x 30 days x 1 load balancer) for the load balancer hours and ¥ 7.2 (or ¥ 0.072 per GB x 100 GB) for the data transferred through the load balancer, for a total monthly charge of ¥ 119.52. Partial hours are billed as full hours. Amazon EC2 service fees apply and are billed separately.

Application Load Balancer Pricing

With the Application Load Balancer, you only pay for what you use. You are charged for each hour or partial hour your Application Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used.

Partial hours are billed as full hours. Regular Amazon EC2 service fees apply and are billed separately.

China (Ningxia) Region

¥ 0.156 per Application load balancer-hour (or partial hour)

¥ 0.072 per LCU-hour (or partial hour)

China (Beijing) Region

¥ 0.156 per Application load balancer-hour (or partial hour)

¥ 0.072 per LCU-hour (or partial hour)

Pricing examples

Pricing example 1

Let’s assume your application receives an average of 1 new connection per second, each lasting 2 minutes. A client sends an average of 5 requests per second and the total processed bytes for requests and responses is 300 KB per second. You have configured 60 rules on the load balancer to route your client requests. We calculate your monthly Application Load Balancer costs using pricing in the Amazon Web Services China (Ningxia) Region as follows:

·  New connections (per second): Each LCU provides 25 new connections per second (averaged over the hour). Since your application receives 1 new connection per second, this translates to 0.04 LCUs (1 connection per second / 25 connections per second)

·  Active connections (per minute): Each LCU provides 3,000 active connections per minute. Your application receives 1 new connection per second, each lasting 2 minutes. This translates to 120 active connections per minute, or 0.04 LCUs (120 active connections per minute / 3,000 active connections per minute)

· Processed Bytes (GBs per hour): Each LCU provides 1 GB of processed bytes per hour. Since each client connection transfers 300 KB of data per second, it translates to 1.08 GB per hour or 1.08 LCUs (1.08 GB/1 GB).

·  Rule Evaluations (per second): For simplicity, assume that all configured rules are processed for a request. Each LCU provides 1,000 rule evaluations per second (averaged over the hour). Since your application receives 5 requests/sec, 60 processed rules for each request results in a maximum 250 rule evaluations per second (60 processed rules – 10 free rules) * 5 or 0.25 LCU (250 rule evaluations per second / 1,000 rule evaluations per second)

Using these values, the hourly bill is calculated by taking the maximum LCUs consumed across the four dimensions. In this example, the processed bytes dimension (1.08 LCUs) is greater than new connections (0.04 LCUs), active connections (0.04 LCUs), and rule evaluations (0.25 LCU) resulting in a total charge of  ¥ 0.072 per hour (1.08 LCUs * ¥ 0.072 per LCU) or ¥ 51.84 per month (¥ 0.072* 24 hours * 30 days).

Adding the hourly charge of ¥ 0.156, the total Application Load Balancer costs are:

·  ¥ 0.228 per hour (¥ 0.156 hourly charge + ¥ 0.072 LCU charge); or

·  ¥ 164.16 per month (¥ 0.228 * 24 hours * 30 days).

 

Pricing example 2

Let’s assume that your mobile application receives an average 100 new connections per second, each lasting 3 minutes. A client sends an average of 4 requests per second per connection and 1,000 bytes are processed per connection. You have configured 20 rules on the load balancer to route your client requests. We calculate your monthly Application Load balancer costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

·  New connections (per second): Each LCU provides 25 connections per second. Since our mobile application uses 100 new connections per second, this translates to 4 LCUs (100 connections per second / 25 connections per second)

·  Active connections (per minute): Each LCU provides 3,000 active connections per minute. Since your mobile application receives 100 new connections per second, each lasting 3 minutes, this translates to 18,000 maximum active connections per minute, or 6 LCUs (18,000 active connections per minute / 3,000 active connections per minute)

·  Processed bytes (GBs per hour): Each LCU provides 1 GB per hour. Since our mobile application transfers 1,000 bytes of data per connection on average, it translates to 0.36 GB per hour, or 0.36 LCUs (0.36 GB/1 GB).

·  Rule evaluations (per second): Each LCU provides 1,000 rule evaluations per second. Since your application receives 4 requests/sec per connection, it translates to 400 requests/sec across all connections. With 20 configured rules this results in a maximum of 4,000 rule evaluations per second (20 configured rules – 10 free rules) * 400 or 4 LCUs (4,000 rule evaluations per second / 1,000 rule evaluations per second)

Using these values, the hourly bill is calculated by taking the maximum LCUs consumed across the four dimensions. In this example, the active connections (6 LCUs) is greater than the new connections (4 LCUs), bandwidth (0.36 LCUs) and rule evaluations (4 LCUs). This results in a total charge of ¥ 0.432 per hour (6 LCUs * ¥ 0.072) or ¥ 311.04 per month (¥ 0.432 * 24 hours * 30 days).

Adding an hourly charge of ¥ 0.156, the total Application Load Balancer costs are:

·  ¥ 0.588 per hour (¥ 0.156 hourly charge + ¥ 0.432 LCU charge); or

·  ¥ 423.36 per month (¥ 0.588 * 24 hours * 30 days).

 

Pricing example 3: Application Load Balancer with Lambda targets only

Let’s assume your application receives an average of 100 new connections per second and each connection lasts 200 milliseconds. A client sends an average of 100 requests per second and 14 KB are the processed bytes for Lambda requests and responses for duration of the connection. You have configured 20 rules on the load balancer to route your client requests. We calculate your monthly Application Load Balancer costs using pricing in the Amazon Web Services China (Ningxia) Region as follows:

·  New connections (per second): Each LCU provides 25 new connections per second (averaged over the hour). Since your application receives 100 new connection per second, this translates to 4 LCUs (100 connection per second / 25 connections per second)

·  Active connections (per minute): Each LCU provides 3,000 active connections per minute. Your application receives 100 new connection per second, each lasting 200 milliseconds. This translates to 100 active connections per minute, or 0.03 LCUs (100 active connections per minute / 3,000 active connections per minute)

·  Processed bytes (GBs per hour): Each LCU provides 0.4 GB per hour for Lambda traffic. Since each client connection transfers 14KB of data on average, it translates 5.04 GB per hour (14KB processed bytes per request+ response *100 requests per second*3600 seconds) or 12.6 LCUs (5.04 GB/0.4 GB) per hour.

·  Rule Evaluations (per second): For simplicity, assume that all configured rules are processed for a request. Each LCU provides 1,000 rule evaluations per second (averaged over the hour). Since your application receives 100 requests/sec, 20 processed rules for each request results in a maximum 1000 rule evaluations per second (20 processed rules – 10 free rules) * 100 or 1 LCU (1000 rule evaluations per second / 1,000 rule evaluations per second).

In this case the dimension with the most LCU usage is processed bytes dimension and hence we will use the LCU usage for processed bytes dimension in our billing calculation. The hourly LCU charge is ¥ 0.9072 (12.6 LCUs*¥ 0.072 per LCU). Adding the hourly charge of ¥ 0.156, the total Application Load Balancer costs are:

·  ¥ 1.0632 per hour (¥ 0.156 hourly charge + ¥ 0.9072 LCU charge); or

·  ¥ 765.504 per month (¥ 1.0632 * 24 hours * 30 days).

100 requests per second translates to 259.2 million (100*3600*24*30) requests per month. This translates to ¥2.953/million requests (¥ 765.504 /259.2).

 

Pricing example 4: Application Load Balancer with both EC2 and Lambda targets

Let’s assume your application receives an average of 1 new connection per second, each lasting 2 minutes. A client sends an average of 50 requests per seconds. The total bidirectional bytes transferred through the load balancer for each request/response is 10 KB. On an average 60% of the requests are served by EC2 instances as targets and 40% by Lambda functions as targets. You have configured 50 rules on the load balancer to route your client requests. We calculate your monthly Application Load Balancer costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

·  New connections (per second): Each LCU provides 25 new connections per second (averaged over the hour). Since your application receives 1 new connection per second, this translates to 0.04 LCUs (1 connection per second / 25 connections per second)

·  Active connections (per minute): Each LCU provides 3,000 active connections per minute. Your application receives 1 new connection per second, each lasting 2 minutes. This translates to 120 active connections per minute, or 0.04 LCUs (120 active connections per minute / 3,000 active connections per minute)

·  Processed bytes (GBs per hour): Each LCU provides 1 GB of processed bytes per hour for EC2 targets. Since each client connection transfers 300 KB of data on average for EC2 instance as target it translates to 1.08 GB per hour or 1.08 LCUs (1.08 GB/1 GB) for EC2 targets. Each LCU provides 0.4 GB of processed bytes for Lambda targets. Since each client connection transfers 200 KB for Lambda targets, it translates to 0.72 GB per hour or 1.8 LCUs (0.72 GB/ 0.4 GB) for Lambda targets. The total LCU usage for processed bytes dimension across EC2 and Lambda targets is 2.88 LCUs.

·  Rule Evaluations (per second): For simplicity, assume that all configured rules are processed for a request. Each LCU provides 1,000 rule evaluations per second (averaged over the hour). Since your application receives 50 requests/sec, 50 processed rules for each request results in a maximum 2000 rule evaluations per second (50 processed rules – 10 free rules) * 50 or 2.00 LCUs (2000 rule evaluations per second / 1,000 rule evaluations per second)

Using these values, the hourly bill is calculated by taking the maximum LCUs consumed across the four dimensions. In this example, the LCU usage for processed bytes dimension (2.88 LCUs) is greater than new connections (0.04 LCUs), active connections (0.04 LCUs), and rule evaluations (2.00 LCU) resulting in a total charge of ¥ 0.20736 per hour (2.88 LCUs * ¥ 0.072 per LCU) or ¥ 149.2992 per month (¥ 0.20736 * 24 hours * 30 days).

Adding the hourly charge of ¥ 0.156, the total Application Load Balancer costs are:

·  ¥ 0.36336 per hour (¥ 0.156 hourly charge + ¥ 0.20736 LCU charge); or

·  ¥ 261.6192 per month (¥ 0.36336 * 24 hours * 30 days)

The load balancer receives 20 requests per second for Lambda targets and it translates to about 51.8 million requests per month. Your monthly LCU usage cost for Lambda requests is ¥93.312 (1.8 LCU/Hour* 24 hours * 30 days* ¥ 0.072 per LCU charge). This translates to ¥1.8014 per million requests as LCU usage costs for Lambda targets.

 

Network Load Balancer Pricing

With the Network Load Balancer, you only pay for what you use. You are charged for each hour or partial hour your Network Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used.

Partial hours are billed as full hours. Regular Amazon EC2 service fees apply and are billed separately.

China (Ningxia) Region

¥ 0.156 per Network load balancer-hour (or partial hour)

¥ 0.072 per LCU-hour (or partial hour)

China (Beijing) Region

¥ 0.156 per Network load balancer-hour (or partial hour)

¥ 0.072 per LCU-hour (or partial hour)

Pricing examples

Pricing example 1

Let’s assume your application receives 1 new TCP connection per second, each lasting 2 minutes and consuming 300 KB in processed bytes. We calculate your monthly Network Load Balancer costs using pricing in the Amazon Web Services China (Ningxia) Region as follows:

·  New connections or flows for TCP traffic: each NLCU provides up to 800 new connections per second. Since your application receives 1 new connection per second, this translates to 0.00125 NLCUs (1 connection per second / 800 connections per second);

·  Active connections/flows for TCP traffic: each NLCU provides up to 100,000 active connections per minute. Your application receives 1 new connection per second, each lasting 2 minutes. This translates to 120 active connections, or 0.0012 NLCUs (120 active connections / 100,000 active connections);

·  Bytes processed for TCP traffic: each NLCU provides 1GB. Since on average, each client connection transfers 300 KB in bandwidth, this translates to 1.08 GB per hour or 1.08 LCUs (1.08 GB/1 GB).

dimensions and averaged over the hour. In this example, the Bytes processed dimension (1.08 NLCUs) is greater than both the new connections (0.00125 NLCUs) and active connections (0.0012 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.07776 per hour (1.08 NLCUs * ¥ 0.072 per NLCU) or ¥55.9872 per month (¥ 0.07776 * 24 hours * 30 days).

Adding the hourly charge of ¥ 0.156, the total Network Load Balancer costs are:

·  ¥ 0.23376 per hour (¥ 0.156 hourly charge + ¥ 0.07776 NLCU charge); or

·  ¥ 168.3072 per month (¥ 0.23376 * 24 hours * 30 days).

 

Pricing example 2

Let’s assume that your mobile application receives 100 new TCP connections per second and 100 new TLS connections per second, each lasting 3 minutes and consuming 1,000 processed bytes. We calculate our monthly Network Load Balancer costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

TCP Traffic

· New connections/flows for TCP traffic: each NLCU provides 800 TCP connections per second. Since our mobile application uses 100 new TCP connections per second, this translates to 0.125 NLCUs (100 connections per second / 800 connections per second);

·  Active connections/flows for TCP traffic: each NLCU provides 100,000 active TCP connections per minute. Since our mobile application receives 100 new TCP connections per second, each lasting 3 minutes, this translates to 18,000 maximum active TCP connections, or 0.18 NLCUs (18,000 active connections / 100,000 active connections);

·  Processed Bytes for TCP Traffic: each NLCU provides 1GB per hour. Since on average our mobile application transfers 1,000 processed bytes for each TCP client connection, this translates to 0.36 GB per hour, or 0.360 NLCUs (0.36 GB / 1GB) across all connections.

TLS Traffic

·  New connections/flows for TLS traffic: each NLCU provides 50 TLS connections per second. Since our mobile application uses 100 new TLS connections per second, this translates to 2 NLCUs (100 connections per second / 50 connections per second);

·  Active connections/flows for TLS traffic: each NLCU provides 3,000 active TLS connections per minute. Since our mobile application receives 100 new TLS connections per second, each lasting 3 minutes, this translates to 18,000 active connections, or 6 NLCUs (18,000 active connections / 3,000 active connections);

·  Bandwidth for TLS Traffic: each NLCU provides 1GB per hour. Since on average our mobile application transfers 1,000 processed bytes for each TLS client connection, this translates to 0.36 GB per hour, or 0.36 NLCUs (0.36 GB /1 GB) across all connections.

Using these values, the hourly bill is calculated by taking the maximum NLCUs consumed across the three dimensions and averaged over the hour for both TCP connections and TLS connections.

In this example for TCP traffic, the processed bytes (0.36 NLCUs) is greater than both the new connections (0.125 NLCUs) and active connections (0.18 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.02592 per hour for TCP traffic (0.36 NLCUs * ¥ 0.072) or ¥18.6624 per month for TCP Traffic (¥ 0.02592  * 24 hours * 30 days).

In this example for TLS traffic, the active connections (6 NLCUs) is greater than both the new connections (2NLCUs) and processed bytes (0.36 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.432 per hour for TLS traffic (6 NLCUs * ¥ 0.072) or ¥ 311.04 per month for TLS traffic (¥ 0.432 *24*30).

Adding the hourly charge of ¥ 0.156 and the usage charges for TCP traffic and TLS traffic total Network Load Balancer costs are:

·  ¥ 0.61392 per hour (¥ 0.156hourly charge + ¥ 0.02592 NLCU charge for TCP traffic + ¥ 0.432 NLCU charge for TLS traffic); or

·  ¥ 442.0224 per month (¥ 0.61392 * 24 hours * 30 days).

 

Pricing example 3

Let’s assume that your mobile application receives 100 new TCP connections per second and 100 new UDP flows per second, the TCP connections is lasting 3 minutes and consuming 1,000 processed bytes while the UDP flow is lasting 2 minutes and consuming 1000 bytes. We calculate our monthly Network Load Balancer costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

TCP Traffic

·  New connections/flows for TCP traffic: each NLCU provides 800 TCP connections per second. Since our mobile application uses 100 new TCP connections per second, this translates to 0.125 NLCUs (100 connections per second / 800 connections per second);

·  Active connections/flows for TCP traffic: each NLCU provides 100,000 active TCP connections per minute. Since our mobile application receives 100 new TCP connections per second, each lasting 3 minutes, this translates to 18,000 maximum active TCP connections, or 0.18 NLCUs (18,000 active connections / 100,000 active connections);

·  Processed Bytes for TCP Traffic: each NLCU provides 1GB per hour. Since on average our mobile application transfers 1,000 processed bytes for each TCP client connection, this translates to 0.36 GB per hour, or 0.360 NLCUs (0.36 GB / 1GB) across all connections.

UDP Traffic

·  New flows for UDP traffic: each NLCU provides 400 UDP flows per second. Since our mobile application uses 100 new UDP flows per second, this translates to 0.25 NLCUs (100 flows per second / 400 connections per second);

·  Active flows for UDP traffic: each NLCU provides 50,000 active UDP flows per minute. Since our mobile application receives 100 new UDP flows per second, each lasting 120 seconds, which translates to 12,000 active flows, or 0.24 NLCUs (12,000 active flows / 50,000 active connections);

·   Processed Bytes for UDP Traffic: each NLCU provides 1GB per hour. Since on average our mobile application transfers 1,000 processed bytes for each UDP client flow, this translates to 0.36 GB per hour, or 0.36 NLCUs (0.36 GB /1 GB) across all UDP flows.

Using these values, the hourly bill is calculated by taking the maximum NLCUs consumed across the three dimensions for each protocol.

In this example for TCP traffic, the processed bytes (0.36 NLCUs) is greater than both the new connections (0.125 NLCUs) and active connections (0.18 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.02592 per hour for TCP traffic (0.36 NLCUs * ¥ 0.072) or ¥18.6624 per month for TCP Traffic (¥ 0.02592 * 24 hours * 30 days).

For UDP traffic, the processed bytes (0.36 NLCUs) is greater than both the new flows (0.25NLCUs) and active flows (0.24 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.02592 per hour for UDP traffic (0.36 NLCUs * ¥ 0.072) or ¥18.6624 per month for UDP traffic (¥ 0.02592 *24*30).

Adding the hourly charge of ¥ 0.156 and the usage charges for TCP traffic and UDP traffic total Network Load Balancer costs are:

·  ¥ 0.07434 per hour (¥0225 hourly charge + ¥ 0.02592 NLCU charge for TCP traffic + ¥ 0.02592 NLCU charge for UDP traffic); or

·   ¥ 53.5248 per month (¥ 0.07434 * 24 hours * 30 days).

 

Gateway Load Balancer Pricing

With the Gateway Load Balancer, you only pay for what you use. You are charged for each hour or partial hour your Gateway Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used.

Partial hours are billed as full hours. Regular Amazon EC2 service fees apply and are billed separately.

China (Ningxia) Region

¥ 0.1005 per Gateway load balancer-hour (or partial hour)

¥ 0.0287 per LCU-hour (or partial hour)

China (Beijing) Region

¥ 0.1005 per Gateway load balancer-hour (or partial hour)

¥ 0.0287 per LCU-hour (or partial hour)

Pricing examples

Pricing example 1

Let’s assume your single-zone deployment Gateway Load Balancer and Gateway Load Balancer Endpoint each receives 1 new connection per second, each lasting 2 minutes and consuming 300 KB in processed bytes. We calculate your monthly costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

For one Gateway Load Balancer:

·  New connections or flows (per second): each GLCU provides up to 600 new connections per second. Since your Gateway Load Balancer receives 1 new connection per second, this translates to 0.00167 GLCUs (1 new connection per second / 600 new connections per second).

·  Active connections or flows (per minute): each GLCU provides up to 60,000 active connections per minute. Your Gateway Load Balancer receives 1 new connection per second, each lasting 2 minutes. This translates to 120 active connections, or 0.002 GLCUs (120 active connections per minute / 60,000 active connections per minute).

·   Bytes processed (GBs per hour): each GLCU provides 1GB. Since on average, each connection transfers 300 KB in bandwidth, this translates to 1.08 GB per hour (1 new connection per second * 300 KB per connection * 3600 seconds) or 1.08 GLCUs (1.08 GB per hour / 1 GB per hour).

Using these values, the hourly bill is calculated by taking the maximum GLCUs consumed across the three dimensions and averaged over the hour. In this example, the Bytes processed dimension (1.08 GLCUs) is greater than both the New connections (0.00167 GLCUs) and Active connections (0.002 GLCUs) dimensions. Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.030996 per hour (1.08 GLCUs * ¥ 0.0287 per GLCU) or ¥ 22.31712 per month (¥ 0.030996 * 24 hours * 30 days).

Adding the hourly charge of ¥ 0.1005, the total Gateway Load Balancer costs are:

·  ¥ 0.131496 per hour (¥ 0.1005 hourly charge + ¥ 0.030996 GLCU charge); or

·   ¥ 94.57712 per month (¥ 0.131496 * 24 hours * 30 days).

For one Gateway Load Balancer Endpoint, we calculate your monthly costs using the hourly charge of ¥0.0875 and per GB data transfer charge of ¥0.0245. This results in a total charge of:

·  ¥0.112 per hour (¥0.0875 hourly charge + ¥0.0245 per GB * 1.08 GB per hour); or

·   ¥80.64 per month (¥0.112 * 24 hours * 30 days).

Altogether, the grand total Gateway Load Balancer and Gateway Load Balancer Endpoint costs are:

·  ¥ 0.243496 per hour (¥ 0.131496 per hour for Gateway Load Balancer + ¥0.112 per hour for Gateway Load Balancer Endpoint); or

·   ¥ 175.31712 per month (¥ 0.243496 * 24 hours * 30 days).

Pricing example 2

Let’s assume your single-zone deployment Gateway Load Balancer and Gateway Load Balancer Endpoint each receives 100 new connections per second, each lasting 4 minutes and consuming 1 KB in processed bytes. We calculate your monthly costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

For one Gateway Load Balancer:

·   New connections or flows (per second): each GLCU provides up to 600 new connections per second. Since your Gateway Load Balancer receives 100 new connections per second, this translates to 0.167 GLCUs (100 new connections per second / 600 new connections per second).

·   Active connections or flows (per minute): each GLCU provides up to 60,000 active connections per minute. Your Gateway Load Balancer receives 100 new connections per second, each lasting 4 minutes. This translates to 24,000 active connections, or 0.4 GLCUs (24,000 active connections per minute / 60,000 active connections per minute).

·  Bytes processed (GBs per hour): each GLCU provides 1GB. Since on average, each connection transfers 1 KB in bandwidth, this translates to 0.36 GB (100 new connections per second * 1 KB per connection * 3600 seconds) per hour or 0.36 GLCUs (0.36 GB per hour / 1 GB per hour).

Using these values, the hourly bill is calculated by taking the maximum GLCUs consumed across the three dimensions and averaged over the hour. In this example, the Active connections dimension (0.4 GLCUs) is greater than both the New connections (0.167 GLCUs) and Bytes processed (0.36 GLCUs) dimensions. Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.01148 per hour (0.4 GLCUs * ¥ 0.0287 per GLCU) or ¥ 8.2656 per month (¥ 0.01148 * 24 hours * 30 days).

Adding the hourly charge of ¥ 0.1005, the total Gateway Load Balancer costs are:

·  ¥ 0.11198 per hour (¥ 0.1005 hourly charge + ¥ 0.01148 GLCU charge); or

·   ¥ 80.6256 per month (¥ 0.11198* 24 hours * 30 days).

For one Gateway Load Balancer Endpoint, we calculate your monthly costs using the hourly charge of ¥0.0875 and per GB data transfer charge of ¥0.0245. This results in a total charge of:

·  ¥0.09632 per hour (¥0.0875 hourly charge + ¥0.0245 per GB * 0.36 GB per hour); or

·   ¥69.3504 per month (¥0.09632 * 24 hours * 30 days).

Altogether, the grand total Gateway Load Balancer and Gateway Load Balancer Endpoint costs are:

·  ¥0.2083 per hour (¥ 0.11198 per hour for Gateway Load Balancer + ¥0.09632 per hour for Gateway Load Balancer Endpoint); or

·  ¥149.976 per month (¥0.2083 * 24 hours * 30 days).

 

Pricing example 3: Multiple Availability Zones and Gateway Load Balancer Endpoints

Let’s assume your Gateway Load Balancer is deployed in 2 Availability Zones and serves 4 Gateway Load Balancer Endpoints. Each Gateway Load Balancer Endpoint receives 25 new connections per second, each lasting 4 minutes and consuming 1 KB in processed bytes, resulting in the Gateway Load Balancer receiving 100 new connections per second. We calculate your monthly costs using pricing in the Amazon Web Services China (Ningxia)  Region as follows:

For the Gateway Load Balancer:

·  New connections or flows (per second): each GLCU provides up to 600 new connections per second. Since your Gateway Load Balancer receives 100 new connections per second, this translates to 0.167 GLCUs (100 new connections per second / 600 new connections per second).

·   Active connections or flows (per minute): each GLCU provides up to 60,000 active connections per minute. Your Gateway Load Balancer receives 100 new connections per second, each lasting 4 minutes. This translates to 24,000 active connections, or 0.4 GLCUs (24,000 active connections per minute / 60,000 active connections per minute).

·   Bytes processed (GBs per hour): each GLCU provides 1GB. Since on average, each connection transfers 1 KB in bandwidth, this translates to 0.36 GB (100 new connections per second * 1 KB per connection * 3600 seconds) per hour or 0.36 GLCUs (0.36 GB per hour / 1 GB per hour).

Using these values, the hourly bill is calculated by taking the maximum GLCUs consumed across the three dimensions and averaged over the hour. In this example, the Active connections dimension (0.4 GLCUs) is greater than both the New connections (0.167 GLCUs) and Bytes processed (0.36 GLCUs) dimensions. Assuming this usage is consistent over 60 minutes, this results in a total charge of ¥ 0.01148 per hour (0.4 GLCUs * ¥ 0.0287 per GLCU) or ¥ 8.2656 per month (¥ 0.01148 * 24 hours * 30 days).

Adding the hourly charge of ¥ 0.1005 per Availability Zone, the total Gateway Load Balancer costs are:

·  ¥ 0.21248 per hour (¥ 0.1005 hourly charge per each Availability Zone * 2 Availability Zones deployed + ¥ 0.01148 GLCU charge); or

·  ¥ 152.9856 per month (¥ 0.21248 * 24 hours * 30 days).

For your Gateway Load Balancer Endpoints, we calculate your monthly costs using the hourly charge of ¥0.0875 per Gateway Load Balancer Endpoint and per GB data transfer charge of ¥0.0245. This results in a total charge of:

·  ¥0.35882 per hour (¥0.0875 hourly charge * 4 Gateway Load Balancer Endpoints + ¥0.0245 per GB * 0.36 GB per hour); or

·  ¥258.3504  per month (¥0.35882 * 24 hours * 30 days).

Altogether, the grand total Gateway Load Balancer and Gateway Load Balancer Endpoint costs are:

·   ¥0.5713 per hour (¥ 0.21248 per hour for Gateway Load Balancer + ¥0.35882 per hour for Gateway Load Balancer Endpoint); or

·  ¥ 411.336 per month (¥0.5713* 24 hours * 30 days).

 

 

Noted:
You are not charged for regional data transfer between Availability Zones when you enable cross-zone load balancing for your Application Load Balancer or Classic Load Balancer. You will be charged for data transfer between Availability Zones with Network Load Balancer or Gateway Load Balancer when cross-zone load balancing is enabled. Check the charges in the data-transfer section at Amazon EC2 On-Demand Pricing page.