Elastic Load Balancing Pricing Calculator
Estimate load balancer hourly fees plus ALB/NLB/GWLB capacity units or Classic processed GB before traffic scales. us-east-1 list pricing.
- No signup
- Instant results
- ~2 min
Rates reviewed
Load balancer type
us-east-1 list rates, pricing as of 2026-06-17. Source: AWS public pricing .
us-east-1 rates (2026-06-14). Modern workloads usually use ALB or NLB; GWLB targets security appliances; CLB is legacy.
Cloud cost optimization · EKS calculator
Who This Tool Is For
Network architects, platform teams, and FinOps analysts forecasting Elastic Load Balancing for EKS Ingress, ECS, or EC2 fleets. A handful of ALBs at 730 hours each plus LCUs can exceed compute if traffic is chatty.
Why We Built This Tool
ELB bills combine a fixed hourly per load balancer and usage-based LCUs (or GB processed for Classic). We use a simplified max-dimension LCU model aligned with AWS documentation — us-east-1 pricing as of 2026-06-14.
What Problem It Solves
- Four LB types. ALB, NLB, GWLB, and CLB rate cards in one wizard.
- LCU visibility. See which dimension (connections, GB, rules) drives capacity units.
- Multi-LB scale. Multiply hourly and LCU costs by load balancer count.
- Budget defensibility. Monthly and annual totals for architecture reviews.
Pair with cloud cost optimization, the EKS calculator, or NAT Gateway calculator for full ingress/egress.
Frequently Asked Questions
Where do these prices come from?
Elastic Load Balancing us-east-1 list prices as of 2026-06-14: ALB $0.0225/hr + $0.008/LCU-hr, NLB $0.0225/hr + $0.006/NLCU-hr, GWLB $0.0125/hr + $0.004/GLCU-hr, CLB $0.025/hr + $0.008/GB processed. Confirm in the AWS Pricing Calculator.
How is LCU calculated here?
For ALB we use max(newConn/25, activeConn/3000, gbPerHr/1, rules/1000) per hour (simplified AWS LCU dimensions). NLB and GWLB use the connection and GB dimensions without the rules term.
Are data transfer charges included?
No — inter-AZ and internet egress data transfer bills separately. This covers ELB hourly and LCU/GB processing only.
Does this include WAF?
AWS WAF attached to ALB bills WAF capacity units separately — not included here.
What about cross-zone load balancing?
Cross-zone traffic can add data transfer charges between AZs. LCUs still accrue on processed bytes and connections as modeled.
How accurate is this estimate?
Arithmetic matches published rates and the simplified LCU formula. Peak-hour LCUs above your averages will increase the bill.