Elastic Load Balancer Cost Calculator
Split an Elastic Load Balancing bill into fixed hourly charges and capacity-unit charges, with every rate editable.
Inputs
LCU for an Application Load Balancer, NLCU for a Network Load Balancer.
Estimated Monthly Cost
$102.93
Fixed Hourly Charges
$32.85
Capacity Unit Charges
$70.08
Capacity Unit Share of the Bill
68.1%
Cost per Load Balancer
$51.47
Step by step
Values used
Load balancers running = 2 balancers; Price per load-balancer-hour = 0.0225 USD; Price per capacity-unit-hour = 0.0080 USD; Average capacity units consumed per hour = 6 units; Billable hours per month = 730 hours
Elastic Load Balancer Cost
cost = balancers × hours × hourly rate + balancers × hours × average capacity units × capacity-unit rate.
Estimated Monthly Cost
= 102.93
Fixed Hourly Charges
= 32.85
Capacity Unit Charges
= 70.08
Capacity Unit Share of the Bill
= 68.1
Cost per Load Balancer
= 51.47
How it works
Every Elastic Load Balancer has two components: a fixed hourly charge that applies even to an idle balancer, and a usage charge measured in capacity units. The capacity unit is not an average of your traffic — AWS evaluates several dimensions each hour and bills only the highest one, so a load balancer can be busy on bandwidth and idle on connections and still be charged as though it were fully loaded on bandwidth. Idle-but-provisioned load balancers in dev and test accounts are a classic source of waste, because the fixed hourly charge runs whether or not a single request arrives.
Formula
Elastic Load Balancer Cost
cost = balancers × hours × hourly rate + balancers × hours × average capacity units × capacity-unit rate.
- hourly rate
- Fixed price for each hour a load balancer exists
- capacity units
- LCUs or NLCUs consumed, billed on the highest dimension each hour
- capacity-unit rate
- Price per LCU-hour or NLCU-hour
Frequently Asked Questions
How is Elastic Load Balancer Cost calculated?
cost = balancers × hours × hourly rate + balancers × hours × average capacity units × capacity-unit rate. Every Elastic Load Balancer has two components: a fixed hourly charge that applies even to an idle balancer, and a usage charge measured in capacity units. The capacity unit is not an average of your traffic — AWS evaluates several dimensions each hour and bills only the highest one, so a load balancer can be busy on bandwidth and idle on connections and still be charged as though it were fully loaded on bandwidth.
Why does Elastic Load Balancer Cost matter?
Idle-but-provisioned load balancers in dev and test accounts are a classic source of waste, because the fixed hourly charge runs whether or not a single request arrives.
What values do I need to enter?
This calculator takes 5 inputs: Load balancers running, Price per load-balancer-hour, Price per capacity-unit-hour, Average capacity units consumed per hour, Billable hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Are these rates current?
The defaults are illustrative us-east-1 list prices — an Application Load Balancer bills per LCU-hour and a Network Load Balancer per NLCU-hour at a different rate, and both vary by region. Check the Elastic Load Balancing pricing page and replace the rate fields before budgeting.
How do I find my actual capacity unit usage?
CloudWatch publishes ConsumedLCUs for an Application Load Balancer and ConsumedLCUs for a Network Load Balancer. Take the average over a representative month rather than a peak hour, since the charge is computed hour by hour.
You might also need
- CloudFront Cost CalculatorCommonly used together
- Gateway Load Balancer CalculatorCommonly used together
- Application Load Balancer Capacity CalculatorCommonly used together
- Network Load Balancer Capacity CalculatorCommonly used together
- NAT Gateway Cost CalculatorAlso in AWS Networking
- VPC CIDR CalculatorAlso in AWS Networking