AWS Elastic Load Balancing Reviews

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.

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.

SSL handling at the ELB level is great, and it’s very scalable. Routing to AWS EC2 instances is also efficient and quick.

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

We are a software development company, and we deploy projects that handle a large amount of incoming user traffic on AWS and ELB. This setup allows us to bifurcate traffic across multiple EC2 instances, which drastically reduces the chances of server crashes during periods of high user traffic.

It is really helpful to build scaleable distributed systems and manage resources . Especially handling falsh sales.

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.

It helps me manage flash sales and automatically scale resources to handle additional traffic. It also saves money by ensuring the right amount of resources are deployed at any given time.

The traffic management backbone our infrastructure couldn't live without

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.

AWS Elastic Load Balancing has become the cornerstone of our application's availability and scalability strategy. It automatically distributes incoming traffic across multiple targets, eliminating single points of failure and ensuring our services remain responsive even during peak demand or partial infrastructure outages. Before adopting ELB, handling traffic spikes required manual intervention and careful capacity planning — now the scaling happens transparently and reliably without any operational overhead. The deep integration with other AWS services like Auto Scaling, CloudWatch, and certificate management has streamlined our entire infrastructure stack, reduced operational complexity, and allowed our engineering team to focus on building features rather than managing traffic routing infrastructure.

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.

Troubleshooting and configuration (listeners, target groups, SSL, health checks) can sometimes be complex.

AWS elastic load balancing supports the custom routing logic which helped us during migrate the traffic from one platfrom to other.

AWS Cloud is the best cloud service provider for B2B companies and large B2C companies. My B2B company has five software (3 Business Software and 2 Management Software) deployed on AWS, and it provides us very smooth response. Before every business deal we always show our website to the client for more information about our company. In my 3+ years of experience in AWS our website never faced any bad server experience or security issue in AWS.

Currently I am using AWS and our website is uploaded to AWS using CI/CD GitHub Actions. The response is so good and smooth. so currently I'm not facing any problems using AWS, that's why I don't dislike the AWS cloud.

In my company there are total of five softwares (3 Business Software and 2 Management Software) are deployed on AWS Cloud. I have 3+ years of experience and I never faced any server outage or network failure problem. When I started working on AWS Cloud it provided me 750 hours of free usage which is awesome to experience AWS. I use products like S3 bucket, An EC2 instance and CodeDeploy with GitHub action for CI/CD on AWS, So that the website always have some developement, fixings and live 24/7. According to me AWS Cloud is great for B2B and large B2C companies because as we know in these companies we have to show our website or portal to the clients.

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.

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.

I use AWS Elastic Load Balancing to manage traffic by spreading it across instances and zones, solving bottlenecks and downtime. Its autoscaling and path-based routing boost operational efficiency by automatically adjusting to traffic and supporting multiple services behind a single load balancer.

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.

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.

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.

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.

The platform is robust and easy to use.

AWS is having web application platform and we can access the services from anywhere. Also, the AWS cloud services give us the options of multiple operating system types with multiple options of CPU and core or instance type.