With Application, Network, and Classic Load Balancers, you only pay for what you use. See FAQs for details.

You are charged for each hour or partial hour that an Application Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used per hour.

You are charged for each hour or partial hour that a Network Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used by Network Load Balancer per hour.

You are charged for each hour or partial hour that a Classic Load Balancer is running and for each GB of data transferred through your load balancer.

Get Started with AWS for Free

Create a Free Account
Or Sign In to the Console

AWS Free Tier Includes 750 hours of Elastic Load Balancing per month for one year and 15GB data processing with Amazon Elastic Load Balancing.

View AWS Free Tier Details »


  • Application Load Balancer Pricing

    US East (N. Virginia and Ohio) and US West (Oregon)
    $0.0225 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    US West (N. California)
    $0.0252 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    Canada (Central)
    $0.02475 per Application Load Balancer-hour (or partial hour)
    $0.0088 per LCU-hour (or partial hour)
    South America (São Paulo)
    $0.0340 per Application Load Balancer-hour (or partial hour)
    $0.011 per LCU-hour (or partial hour)
    EU (Ireland)
    $0.0252 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    EU (Frankfurt)
    $0.0270 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    EU (London)
    $0.02646 per Application Load Balancer-hour (or partial hour)
    $0.0084 per LCU-hour (or partial hour)
    Asia Pacific (Tokyo)
    $0.0243 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    Asia Pacific (Seoul)
    $0.0225 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    Asia Pacific (Singapore and Sydney)
    $0.0252 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)
    Asia Pacific (Mumbai)
    $0.0239 per Application Load Balancer-hour (or partial hour)
    $0.008 per LCU-hour (or partial hour)

    An LCU measures the dimensions on which the Application Load Balancer processes your traffic (averaged over an hour). The four dimensions measured are:

    • New connections: Number of newly established connections per second. Typically, many requests are sent per connection.
    • Active connections: Number of active connections per minute.
    • Bandwidth: The amount of traffic processed by the load balancer in Mbps
    • Rule evaluations:  It is the product of number of rules processed by your load balancer and the request rate. The first 10 processed rules are free (Rule evaluations = Request rate * (Number of rules processed - 10 free rules)

     

    You are charged only on the dimension with the highest usage. An LCU contains:

    • 25 new connections per second.
    • 3,000 active connections per minute.
    • 2.22 Mbps (which translates to 1 GB per hour)
    • 1,000 rule evaluations per second
    Note 1: For HTTPS listeners, 25 new connections/sec for LCU computation is applicable for RSA certificates with key size <=2K and ECDSA certificates with key size <=256. For certificates with larger key sizes, please refer to the pricing FAQs
    Note 2: If you have 10 or fewer rules configured, the rule evaluations dimension is ignored in LCU computation.
    Note:2 If you have 10 or fewer rules configured, the rule evaluations dimension is ignored in LCU computation.
    Note:2 If you have 10 or fewer rules configured, the rule evaluations dimension is ignored in LCU computation.

    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 consumes 300 KB in bandwidth for the duration of the connection. 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 US-East-1 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)
    • Bandwidth (Mbps): Each LCU provides 2.22 Mbps averaged over the hour. Since each client connection transfers 300KB of data on average, it translates to 2.4 Mbps or 1.08 LCUs (2.4 Mbps / 2.22 Mbps) across all connections.
    • 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 bandwidth 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.00864 per hour (1.08 LCUs * $0.008 per LCU) or $6.22 per month ($0.00864 * 24 hours * 30 days).

     

    Adding the hourly charge of $0.0225, the total Application Load Balancer costs are:

    • $0.03114 per hour ($0.0225 hourly charge + $0.00864 LCU charge); or
    • $22.42 per month ($0.03114 * 24 hours * 30 days).

    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 consumes 1,000 bytes in bandwidth. 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 US-East 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)
    • Bandwidth (Mbps): Each LCU provides 2.22 Mbps. Since our mobile application transfers 1,000 bytes of data per connection on average, it translates to 0.8 Mbps, or 0.36 LCUs (0.8 Mbps / 2.22 Mbps) across all connections.
    • 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.048 per hour (6 LCUs * $0.008) or $34.56 per month ($0.048 * 24 hours * 30 days).
     
     
    Adding an hourly charge of $0.0225, the total Application Load Balancer costs are:
    • $0.0705 per hour ($0.0225 hourly charge + $0.048 LCU charge); or
    • $50.76 per month ($0.048 * 24 hours * 30 days).
     
  • Network Load Balancer Pricing

    US East (N. Virginia and Ohio) and US West (Oregon)
    $0.0225 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    US West (N. California)
    $0.0252 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    Canada (Central)
    $0.0248 per Network Load Balancer-hour (or partial hour)
    $0.0066 per LCU-hour (or partial hour)
    South America (São Paulo)
    $0.034 per Network Load Balancer-hour (or partial hour)
    $0.0083 per LCU-hour (or partial hour)
    EU (Ireland)
    $0.0252 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    EU (Frankfurt)
    $0.027 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    EU (London)
    $0.0265 per Network Load Balancer-hour (or partial hour)
    $0.0063 per LCU-hour (or partial hour)
    Asia Pacific (Tokyo)
    $0.0243 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    Asia Pacific (Seoul)
    $0.0225 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    Asia Pacific (Singapore and Sydney)
    $0.0252 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)
    Asia Pacific (Mumbai)
    $0.0239 per Network Load Balancer-hour (or partial hour)
    $0.006 per LCU-hour (or partial hour)

    An LCU measures the dimensions on which the Network Load Balancer processes your traffic (averaged over an hour). The three dimensions measured are:

    • New connections or flows: Number of newly established connections per second. Many technologies (HTTP, WebSockets, etc.) reuse TCP connections for efficiency. The number of new connections is typically lower than your request or message count.
    • Active connections or flows: Number of active connections per minute.
    • Bandwidth: The amount of traffic processed by the load balancer in Mbps.

     

    You are charged only on one of the three dimensions that has the highest usage for the hour. An LCU for the Network Load Balancer (NLCU) contains:

    • 800 new non-SSL connections or flows per second.
    • 100,000 active connections or flows (sampled per minute)
    • 2.22 Mbps (which translates to 1GB per hour)

    Example 1

    Let’s assume your application receives 1 new connection per second, each lasting 2 minutes and consuming 300 KB in bandwidth. We calculate your monthly Network Load Balancer costs using pricing in the US-East-1 Region as follows:

    • New connections or flows: 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: 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 per minute, or 0.0012 NLCUs (120 active connections / 100,000 active connections);
    • Bandwidth: each NLCU provides 2.22 Mbps. Since on average, each client connection transfers 300 KB in bandwidth, this translates to 2.4 Mbps or 1.08NLCUs (2.4 Mbps / 2.22 Mbps) 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. In this example, the bandwidth 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.00648 per hour (1.08 NLCUs * $0.006 per NLCU) or $4.67 per month ($0.00648 * 24 hours * 30 days).

     

    Adding the hourly charge of $0.0225, the total Network Load Balancer costs are:

    • $0.0289 per hour ($0.0225 hourly charge + $0.00648 NLCU charge); or
    • $20.86 per month ($0.0289 * 24 hours * 30 days).

     

    Example 2

    Let’s assume that your mobile application receives 1000 new connections per second, each lasting 3 minutes and consuming 1,000 bytes in bandwidth. We calculate our monthly Network Load Balancer costs using pricing in the US-East Region as follows:

    • New connections/flows: each NLCU provides 800 connections per second. Since our mobile application uses 1000 new connections per second, this translates to 1.25 NLCUs (1000 connections per second / 800 connections per second);
    • Active connections/flows: each NLCU provides 100,000 active connections per minute. Since our mobile application receives 1000 new connections per second, each lasting 3 minutes, this translates to 180,000 maximum active connections per minute, or 1.8 NLCUs (180,000 active connections / 100,000 active connections);
    • Bandwidth: each NLCU provides 2.22 Mbps. Since on average our mobile application transfers 1,000 bytes in bandwidth for each client connection, this translates to 8 Mbps, or 3.60 NLCUs (8 Mbps / 2.22 Mbps) 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. In this example, the bandwidth (3.6 NLCUs) is greater than both the new connections (1.25 NLCUs) and active connections (1.8 NLCUs). Assuming this usage is consistent over 60 minutes, this results in a total charge of $0.0216 per hour (3.6 NLCUs * $0.006) or $15.55 per month ($0.0216 * 24 hours * 30 days).

     

    Adding the hourly charge of $0.0225, the total Network Load Balancer costs are:

    • $0.0441 per hour ($0.0225 hourly charge + $0.0216 NLCU charge); or
    • $31.75 per month ($0.044 * 24 hours * 30 days).
  • Classic Load Balancer

    US East (N. Virginia and Ohio) and US West (Oregon)
    $0.025 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    US West (N. California)
    $0.028 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer

    Canada (Central)

    $0.0275 per Classic Load Balancer-hour (or partial hour)
    $0.0088 per GB of data processed by a Classic Load Balancer
    South America (São Paulo)
    $0.034 per Classic Load Balancer-hour (or partial hour)
    $0.011 per GB of data processed by a Classic Load Balancer
    EU (Ireland)
    $0.028 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    EU (Frankfurt)
    $0.030 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    EU (London)
    $0.0294 per Classic Load Balancer-hour (or partial hour)
    $0.0084 per GB of data processed by a Classic Load Balancer
    Asia Pacific (Tokyo)
    $0.027 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    Asia Pacific (Seoul)
    $0.025 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    Asia Pacific (Singapore and Sydney)
    $0.028 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer
    Asia Pacific (Mumbai)
    $0.0266 per Classic Load Balancer-hour (or partial hour)
    $0.008 per GB of data processed by a Classic Load Balancer

    Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS is subject to Japanese Consumption Tax. Learn more.

    For more details on Elastic Load Balancing pricing in GovCloud, visit the GovCloud pricing page.

    Example 1

    A medium-sized website running on 10 Amazon EC2 instances in the US East (N. Virginia) 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 $18 (or $0.025 per hour x 24 hours per day x 30 days x 1 load balancer) for the load balancer hours and $0.80 (or $0.008 per GB x 100 GB) for the data transferred through the load balancer, for a total monthly charge of $18.80. Partial hours are billed as full hours. Regular Amazon EC2 service fees apply and are billed separately.