AWS ELB
Generated by GPT-5-miniExpansion Funnel Raw 1 → Dedup 0 → NER 0 → Enqueued 0
| AWS ELB | |
|---|---|
| Name | AWS ELB |
| Developer | Amazon Web Services |
| Initial release | 2009 |
| Written in | Proprietary |
| Platform | Amazon EC2, Amazon ECS, Amazon EKS |
AWS ELB
Amazon Web Services Elastic Load Balancing (commonly offered by Amazon Web Services) provides automated traffic distribution across compute resources in multiple availability zones to improve availability and scalability. It integrates with Amazon EC2, Amazon ECS, Amazon EKS and other Amazon services to support web applications, microservices and hybrid architectures. ELB offers several load balancer types for Layer 4 and Layer 7 traffic, enabling fault tolerance, session stickiness and TLS termination.
Overview
Elastic Load Balancing originated as a managed service from Amazon Web Services to distribute incoming application traffic across multiple Amazon EC2 instances and subsequently expanded to integrate with container and serverless offerings. ELB supports several load balancer models that map to use cases familiar from networking vendors and software proxies used in cloud-native deployments. It is commonly used alongside services from Amazon such as Amazon CloudWatch, Amazon Route 53 and AWS Identity and Access Management.
Features and Components
ELB provides multiple load balancer types tailored to protocol and feature sets: Classic load balancers for legacy use, Application Load Balancers for HTTP/HTTPS and WebSocket routing, Network Load Balancers for ultra-low-latency TCP/UDP handling, and Gateway Load Balancers for deploying virtual appliances. Key components include listeners that define port and protocol behavior, target groups that represent registered backends (such as Amazon EC2 instances, IP addresses, or Lambda functions), and health checks that determine target availability. ELB integrates with Amazon Certificate Manager for TLS certificates, AWS WAF for web application protection, and supports cross-zone load balancing across Amazon availability zones.
Configuration and Deployment
Deploying ELB typically involves defining listeners, creating target groups, registering targets and configuring health check criteria. Infrastructure as code tools like AWS CloudFormation, HashiCorp Terraform and AWS CDK are frequently used to provision ELB resources in repeatable pipelines that integrate with continuous delivery systems. Integration patterns include anchoring ELB endpoints behind Amazon Route 53 records, placing ELB in front of Amazon EC2 Auto Scaling groups, and hooking Application Load Balancers into Amazon ECS services using service discovery. Blue/green and canary deployments route traffic via ELB to enable staged rollouts alongside CI/CD tools such as Jenkins and GitLab CI.
Security and Compliance
ELB supports TLS termination and end-to-end encryption by integrating with Amazon Certificate Manager for certificate management, enabling strong cipher suites and forward secrecy configurations. It can be combined with AWS WAF for protection against injection and cross-site scripting attacks, and integrates with AWS Identity and Access Management policies to control who can modify load balancers and associated resources. ELB features logging to Amazon S3 and monitoring via Amazon CloudWatch Logs and enables access logging for audit trails required by standards such as PCI DSS and HIPAA when used within compliant AWS accounts.
Performance and Monitoring
Performance tuning for ELB includes configuring idle timeouts, optimizing connection draining, and selecting the appropriate load balancer type—for example, Network Load Balancers for high-throughput TCP workloads and Application Load Balancers for HTTP routing with host- and path-based rules. Monitoring relies on Amazon CloudWatch metrics for request counts, latency, HTTP 4xx/5xx rates, target connection errors and healthy host counts. Integration with AWS X-Ray assists distributed tracing for applications behind Application Load Balancers, while third-party observability platforms can ingest CloudWatch metrics and ELB access logs for dashboarding and alerting.
Pricing and Cost Management
ELB pricing models typically include hourly charges for load balancer capacity units or fixed hourly fees combined with data processing charges per gigabyte. Cost management strategies include consolidating listeners where safe, using Application Load Balancers for multiplexed HTTP/2 connections, and employing AWS Cost Explorer and billing alarms to track ELB-related spend. Right-sizing deployments by matching load balancer type to traffic patterns—using Network Load Balancers for predictable TCP/UDP throughput or Application Load Balancers for many small HTTP requests—reduces unnecessary data processing fees.
Limitations and Best Practices
Known limitations include per-region resource quotas, default connection limits on legacy models, and feature differences between load balancer types that may require architectural adjustments. Best practices include choosing the minimal-privilege IAM roles for ELB management, enabling access logs and health checks, designing stateless backends to allow horizontal scaling, and using multiple availability zones for resiliency. Use infrastructure as code for reproducibility, centralize TLS certificate management with Amazon Certificate Manager, and validate performance under realistic load with tools such as Apache JMeter or industry benchmarks.