What I like most about AWS Elastic Load Balancing (ELB) is how it automatically distributes incoming traffic across multiple targets, which improves application availability, scalability, and fault tolerance. It also integrates smoothly with Auto Scaling, ECS, EKS, EC2, and Lambda, so applications can handle traffic spikes without needing manual intervention.

I also appreciate the flexibility it offers through support for Application Load Balancer (ALB), Network Load Balancer (NLB), Gateway Load Balancer (GWLB), and Classic Load Balancer, making it easier to choose the right option for different workloads. Review collected by and hosted on G2.com.

While ELB is straightforward to configure for standard deployments, advanced routing rules, SSL certificate management, and more complex networking scenarios still require a solid understanding of AWS networking. Monitoring and troubleshooting application-level issues can also be challenging and may require additional observability tools to get the visibility you need. Review collected by and hosted on G2.com.

AWS Elastic Load Balancer has been an essential part of our cloud infrastructure for distributing incoming traffic across multiple EC2 instances.

The Application Load Balancer (ALB) provided advanced routing capabilities based on URL paths and host headers which helped us efficiently manage our microservices architecture.

The seamless integration with AWS Auto Scaling ensured that our application could automatically handle traffic spikes without any manual intervention. Review collected by and hosted on G2.com.

The pricing can be confusing as you are charged separately for Load Balancer Capacity Units (LCUs) which makes it difficult to estimate costs accurately upfront.

The initial configuration of listener rules and target groups can be complex for new users. Review collected by and hosted on G2.com.

SSL handling at the ELB level is great, and it’s very scalable. Routing to AWS EC2 instances is also efficient and quick. Review collected by and hosted on G2.com.

It has fixed monthly cost which can be killer for startup projects. Setting it up for simple projects is a waste of time, moreover debugging can be improved Review collected by and hosted on G2.com.

It is really helpful to build scaleable distributed systems and manage resources . Especially handling falsh sales. Review collected by and hosted on G2.com.

The task startup times are a bit slow, which adds latency. If we pre-start tasks to avoid that delay, we end up wasting money by keeping resources running that we aren’t actually using. Review collected by and hosted on G2.com.

The traffic management backbone our infrastructure couldn't live without Review collected by and hosted on G2.com.

The pricing model can be difficult to predict, especially when dealing with fluctuating traffic patterns — costs can add up quickly if not monitored carefully. The configuration options, while powerful, have a steep learning curve for teams new to AWS. Debugging connectivity or routing issues can be frustrating due to limited visibility into internal load balancer behavior without setting up additional logging and monitoring tools. Also, some advanced features like fine-grained routing rules are only available on specific load balancer types, which forces architectural decisions early in the setup process. Review collected by and hosted on G2.com.

I like AWS Elastic Load Balancing for its automatic scaling and high availability, which provide hands-off elasticity by allowing the load balancer to scale with traffic. I enjoy its native integration with the AWS stack, working seamlessly with EC2s within ECS and EKS. I also appreciate the health checks and graceful draining features, along with the ALB host and path-based routing, which allow multiple services to live behind a single load balancer. The centralized TLS termination and enhanced security features are also valuable to me. Review collected by and hosted on G2.com.

I think AWS Elastic Load Balancing could use better cost visibility. A cost dashboard as part of the AWS console for ALB would be helpful. Review collected by and hosted on G2.com.

What I appreciate most about AWS Elastic Load Balancing is its seamless integration with other AWS services, which ensures high availability, fault tolerance, and scalability—all without the need for manual infrastructure management.

From an engineering standpoint, I find it especially valuable that ELB can automatically scale in response to incoming traffic, conduct intelligent health checks, and direct requests exclusively to healthy targets. This applies whether the targets are EC2 instances, containers running in ECS or EKS, or even specific IP addresses.

The Application Load Balancer’s ability to support both path-based and host-based routing, along with its native integration with ACM for SSL termination, makes it particularly well-suited for modern microservice architectures. In summary, ELB enables me to concentrate on deployment and application performance, while AWS efficiently manages the complexities of load balancing in the background. Review collected by and hosted on G2.com.

One limitation I’ve observed with AWS Elastic Load Balancing is that it can sometimes feel restrictive when it comes to customization and visibility. For instance, troubleshooting connection issues can be challenging because the detailed connection logs are not always straightforward to interpret, and the available metrics may be more limited than what you might get with a custom load balancer setup.

Additionally, the pricing can become significant in high-traffic scenarios, as ELB charges separately for usage hours, data processed, and LCU consumption. In certain situations, making adjustments to timeouts or implementing advanced routing logic may require additional configuration steps or even the use of external solutions.

Nevertheless, these compromises are understandable given that it is a fully managed and highly available service. Review collected by and hosted on G2.com.

AWS elastic load balancing automatically distributes traffic to keep application highly available and reliable. It also easly integrate with EC2/EKS & ASG , making scaling and failover easy. Review collected by and hosted on G2.com.

Troubleshooting and configuration (listeners, target groups, SSL, health checks) can sometimes be complex. Review collected by and hosted on G2.com.

AWS ELB takes away huge chunk of manual work by automatically distributing incoming traffic across multiple targets like EC2 instances, containers and IPs.

The integration with auto scaling is fantastic.

Its incredibly reliable, stable under high load, and fits perfectly within the AWS ecosystem.

The monitoring with Cloudwatch is also a big plus for real-time visibility. Review collected by and hosted on G2.com.

The pricing model can get slightly confusing, especially when handling unpredictable traffic patterns. Also, configuration of advanced routing rule like path-based or host based could be more intuitive in the UI, Sometimes you need to reply on CLI or CLoudFormation for precision. Review collected by and hosted on G2.com.

I really like AWS Elastic Load Balancing because it automatically distributes incoming traffic across multiple servers, ensuring that no single server gets overloaded. It helps applications stay reliable and available, even if one server goes down. What’s great is that it automatically scales up or down based on demand, so your application performs well during both high and low traffic periods. It also includes built-in health checks that monitor servers and route traffic only to healthy ones. ELB works seamlessly with other AWS services like EC2, ECS, and Auto Scaling, making it easy to manage and secure your applications. Plus, it supports different types of load balancers for various use cases, offers strong security features like SSL/TLS encryption, and is cost-effective since you pay only for what you use. Review collected by and hosted on G2.com.

One area where AWS Elastic Load Balancing can improve is in simplifying its configuration and monitoring. Sometimes, setting up advanced routing rules or integrating with multiple services can feel a bit complex for new users. The monitoring and logging options, though powerful, could also be made more user-friendly with clearer insights and easier troubleshooting tools. Additionally, reducing latency in cross-region load balancing and offering more cost transparency would make it even better for businesses that manage large-scale or global applications. Review collected by and hosted on G2.com.