AWS Elastic Load Balancing
aws.amazon.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What AWS Elastic Load Balancing is
AWS Elastic Load Balancing distributes application traffic across targets and virtual appliances in one or more Availability Zones. Its Application, Network, Gateway and Classic Load Balancers adjust request-handling capacity as traffic changes and can run configurable target health checks. Application Load Balancers support HTTP header-based routing, redirects, fixed responses, HTTP/2 and gRPC. Network Load Balancers support static Elastic IP addresses and AWS PrivateLink for TCP and TLS listeners. ELB also provides SSL/TLS termination, certificate management and client certificate authentication, with CloudWatch metrics and logging for all four types. One load balancer can handle traffic across AWS and on-premises resources. Kubernetes support includes direct-to-pod routing for Application Load Balancers and fully private EKS clusters with Application and Network Load Balancers. AWS gives guidance on choosing a type based on workload and protocol. Charges are usage based and vary by region; standard data transfer and public IPv4 address charges may also apply. New AWS customers receive a Free Tier for six months after account creation, with specified hourly and data-processing allowances.
Who it suits
ELB suits teams distributing application traffic across multiple targets, including workloads spanning AWS and on-premises resources. Kubernetes users and teams needing different routing options can choose among its four load balancer types.
Good to know, and what to watch
- Offers Application, Network, Gateway and Classic load balancers.
- Scales request handling as application traffic changes.
- Includes configurable target health checks.
- CloudWatch metrics and logging cover all four types.
- Can load balance across AWS and on-premises resources.
- Usage charges vary by region.
- Data transfer and public IPv4 charges may be additional.
- Application Load Balancers require a different API set from Classic.
Plans
Every plan and pricePay-as-you-go — Application Load Balancer
Pay-as-you-go — Classic Load Balancer
Pay-as-you-go — Gateway Load Balancer
Pay-as-you-go — Network Load Balancer
Getting started
- Open the Elastic Load Balancing website
- Select Application, Network, Gateway, or Classic Load Balancer
- Choose the type that matches your traffic or appliance
- Configure target health checks and routing
- Enable CloudWatch metrics and logging
- Use the AWS Free Tier if you are a new AWS customer
Limits to check
The AWS Free Tier lasts six months after account creation and gives new customers 750 shared hours per month for Classic and Application Load Balancers, plus specified data-processing allowances and up to $200 in credits. Usage beyond those allowances is charged under the applicable pay-as-you-go model, with possible data-transfer and public IPv4 fees.
The Club's review
Overview
AWS Elastic Load Balancing (ELB) is a managed service that distributes application traffic across targets and virtual appliances in Availability Zones. It suits teams running workloads on AWS that want load balancing to scale with demand and need a choice of routing models. Its main trade-off is a usage-based bill whose total can include data transfer and public IPv4 charges.
Key features
ELB offers Application, Network, Gateway, and Classic Load Balancers, each aimed at a distinct workload. Capacity scales with traffic, and configurable health checks help route requests to suitable targets. Classic, Application, and Network Load Balancers carry a stated monthly availability guarantee of at least 99.99%.
Application Load Balancer is the fit for HTTP applications: it supports header-based routing, redirects, fixed responses, HTTP/2, and gRPC. Network Load Balancer targets transport protocols and workloads where low latency or extreme performance is the priority; static Elastic IP addresses and AWS PrivateLink are supported for TCP and TLS listeners. Gateway Load Balancer is intended for third-party virtual appliances, while Classic is for applications built in EC2-Classic.
SSL/TLS termination, certificate management, and client certificate authentication cover common traffic-security needs. CloudWatch metrics and logging apply across all four types. Kubernetes Controller support includes direct-to-pod routing for Application Load Balancers and private EKS cluster support for Application and Network Load Balancers. ELB can also balance traffic across AWS and on-premises resources through one load balancer, which is useful for hybrid deployments.
One migration constraint matters: Application Load Balancers use a different API set from Classic Load Balancers. Existing tooling or integrations built for Classic may need adjustment before a move.
Pricing
ELB is paid, with usage-based charges; rates vary by region. In addition to load balancer charges, standard AWS data transfer and public IPv4 address charges may apply. Compare the complete expected usage rather than treating the hourly component as the whole bill.
- AWS Free Tier: free (billed). New AWS customers receive 750 hours per month shared between Classic and Application Load Balancers, plus 15 GB of Classic data processing or 15 LCUs for Application Load Balancers. The free plan lasts 6 months after account creation and includes up to $200 in credits. The shared hours and type-specific allowances make this useful for trying eligible workloads, but it is not an unlimited ongoing tier.
- Pay-as-you-go — Application Load Balancer: custom pricing. Billed per hour or partial hour running, plus Load Balancer Capacity Units used per minute. Additional data transfer and public IPv4 charges may apply. This suits HTTP workloads that need its application-layer routing, but costs depend on usage and region.
- Pay-as-you-go — Network Load Balancer: custom pricing. Billed per hour or partial hour running, plus Network Load Balancer Capacity Units used per minute. Data transfer and public IPv4 charges may also apply. Choose it for transport-protocol workloads where its performance and low-latency focus fit.
- Pay-as-you-go — Gateway Load Balancer: custom pricing. Billed per hour or partial hour running, plus Gateway Load Balancer Capacity Units used per minute. Gateway Load Balancer Endpoints are priced and billed separately; data transfer and public IPv4 charges may also apply. The separate endpoint charge is important when estimating appliance deployments.
- Pay-as-you-go — Classic Load Balancer: custom pricing. Billed per hour or partial hour running and for each GB transferred, with possible additional data transfer and public IPv4 charges. It is the legacy-oriented fit for EC2-Classic applications, but teams should account for its transfer-based billing and API differences when assessing it.
Platforms
ELB is available through API and web platforms. Its managed-service model is a strong fit for AWS-centered operations; readers seeking a self-hosted or Linux deployment model should consider alternatives instead.
Who it's for
ELB is best for teams operating applications on AWS that need managed traffic distribution, automatic capacity scaling, health checks, or workload-specific routing. HTTP services, low-latency transport traffic, third-party appliances, and EC2-Classic applications each have a corresponding load balancer type. Hybrid teams can use it across AWS and on-premises resources. It is less compelling for organizations whose primary requirement is self-hosted infrastructure, or for teams that need predictable total costs without modeling usage and related charges.
Pros and cons
- Pros: Four load balancer types let teams match routing to HTTP, transport, appliance, or EC2-Classic needs rather than use a single model.
- Pros: Automatic capacity scaling, configurable health checks, and CloudWatch metrics and logging support ongoing operations across all four types.
- Pros: Kubernetes Controller capabilities, private EKS support, and AWS-to-on-premises balancing address Kubernetes and hybrid deployments.
- Cons: Usage-based charges can include capacity-unit or data-processing costs alongside hourly runtime, with transfer and public IPv4 charges potentially added.
- Cons: Application and Classic Load Balancers use different API sets, creating migration work for Classic-based tooling.
- Cons: The Free Tier's shared hours, processing or LCU allowances, and six-month duration limit its usefulness for sustained production traffic.
Alternatives
For a broader comparison, see Load Balancing Software.
- F5 BIG-IP APM is another paid option, with a free trial and perpetual-license options across virtual, hardware, or hybrid environments.
- VMware Workstation Pro is a free Windows or Linux-hosted option for readers seeking workstation virtualization rather than managed cloud load balancing.
- A10 Thunder ADC is a paid alternative with a free trial and API, Linux, and self-hosted platforms.
- Loadbalancer.org Enterprise may suit buyers considering a perpetual or subscription self-hosted enterprise appliance; its Enterprise VA Basic perpetual plan is $2,360, paid once and includes 400Mbps throughput, 400 SSL TPS, and unlimited servers.
- Progress Kemp LoadMaster offers a 30-day temporary trial license for the VLM-MAX model with Enterprise Plus Support, including ESP, WAF, and GEO.
- HAProxy Community Edition is a free Linux, self-hosted load balancer with TCP and HTTP proxying.
- Linux Virtual Server is a free, GPL-licensed option that runs on Linux.
- MetalLB is a free open-source project for Kubernetes load balancing, a narrower fit for readers focused on Kubernetes.
Verdict
Choose AWS Elastic Load Balancing if you run applications on AWS and want managed scaling, health checks, and load balancer types tailored to different traffic. Its broad coverage and AWS integrations are the strongest reasons to choose it. Look elsewhere if self-hosting or predictable pricing is more important, and model usage, transfer, and public IPv4 charges before committing.
The verdict
ELB offers several load balancer types for different traffic and deployment needs, with scaling, health checks and monitoring features. Costs are usage based, and some related data transfer or public IPv4 charges may be additional.
Questions people ask
Is there a free plan?
Yes. New AWS customers can use the AWS Free Tier for six months after account creation, with up to $200 in credits.
Is there a free trial?
No free trial is listed.
How is ELB priced?
Charges are usage based. Rates vary by region, and data transfer or public IPv4 address charges may also apply.
Which load balancer handles HTTP requests?
AWS recommends Application Load Balancer for HTTP requests.
Does ELB support Kubernetes?
Yes. Listed support includes direct-to-pod routing for Application Load Balancers and fully private EKS cluster support for Application and Network Load Balancers.
Can one load balancer connect AWS and on-premises resources?
Yes. ELB can load balance across AWS and on-premises resources using a single load balancer.
What the maker publishes
- API and SDKs
- ELB can be managed through the AWS console, AWS CLI, language-specific SDKs or low-level HTTPS Query APIs. source
- API compatibility
- Application Load Balancers require a different API set from Classic Load Balancers. source
- Application routing
- Application Load Balancer supports HTTP header based routing, redirects, fixed responses, HTTP/2, and gRPC. source
- Application routing
- Application Load Balancers handle HTTP and HTTPS traffic and route requests according to request content. source
- Automatic scaling
- ELB automatically adjusts load-balancer capacity as incoming traffic changes. source
- Availability and scaling
- ELB automatically scales request handling capacity in response to application traffic and runs configurable health checks on targets. source
- Company founding
- Gartner lists Amazon Web Services as founded in 2006. source
- Company headquarters and size
- Gartner lists AWS headquarters in Seattle, United States, with more than 10,001 employees. source
- Company legal name
- Crunchbase identifies the maker's parent company legal name as Amazon.com, Inc. source
- Compliance
- AWS directs customers to its compliance-program scope documentation to determine which compliance programs cover ELB. source
- Controller project status
- The Kubernetes controller repository is public, has about 4.3k stars and 1.7k forks, and includes Helm, API, documentation and security files. source
- Documentation depth
- AWS publishes user guides for ALB, NLB, GWLB and Classic Load Balancer plus CLI references and API references. source
- Free tier
- New AWS customers receive 750 shared monthly hours for Classic and Application Load Balancers, 15 GB Classic processing and 15 ALB LCUs; newer accounts can also receive up to $200 credits. source
- Gateway appliances
- Gateway Load Balancers deploy, scale and manage virtual appliances such as firewalls. source
- Health checks
- Load balancers monitor registered-target health and send traffic only to targets that pass health checks. source
- HTTP/2 and gRPC
- ALB supports end-to-end HTTP/2 and gRPC targets, including gRPC health checks, content routing, metrics and TLS termination. source
- Hybrid use
- ELB can load balance across AWS and on-premises resources using a single load balancer. source
- Integrations
- ELB features CloudWatch metrics and logging for all four load balancer types. source
- Integrations
- Documented integrations include EC2, EC2 Auto Scaling, ACM, CloudWatch, ECS, Global Accelerator, Route 53 and AWS WAF. source
- Kubernetes
- The features page lists Kubernetes Controller support, including direct-to-pod routing for Application Load Balancers and fully private EKS cluster support for Application and Network Load Balancers. source
- Kubernetes extensibility
- The open-source AWS Load Balancer Controller provisions ALBs for Kubernetes Ingress, NLBs for Services and ALBs or NLBs for Gateway resources. source
- Licence
- ELB is a proprietary managed AWS service; AWS grants only a limited service-use intellectual-property licence during the agreement term. source
- Limit: complexity
- G2 and Gartner reviewers report that listener, target-group, SSL and health-check configuration and troubleshooting can be difficult. source
- Limit: cost
- Gartner reviewers describe ELB as expensive for smaller applications, while G2 notes that usage-based pricing can be confusing with unpredictable traffic. source
Checked against the maker's pages on 15 Oct 2026.