Amazon Elastic Load Balancing Reviews

We use the solution for internet-exposed websites and internal load-balancing purposes.

The tool could enhance the internal load balancer with better health monitoring. The external load balancer needs more security parameters to protect it from the internet, as it currently lacks protection. It's okay for basic load balancing and those looking for basic functionality in an application load balancer. However, if someone is going to onboard a critical application, like in the banking sector, I wouldn't suggest Amazon Elastic Load Balancer because of security issues. There are no firewall restrictions.

If I compare it to Azure Load Balancer, Azure has two types: the application gateway and load balancing. With Azure's application load balancer, I can have multiple features: app features, data features, and more. It's more compatible than AWS Elastic Load Balancer.

I have been using the product for three years. 

I rate Amazon Elastic Load Balancing's stability a nine out of ten. 

I'd rate the tool seven out of ten for scalability, as it's a bit complex to scale.

The solution's response time is good. 

Positive

The tool's deployment process is simple.

The solution's pricing is low and I rate it a nine out of ten. 

The health check capabilities are basic, running on digital ports, and not advanced load-based health monitoring. However, it does help improve application uptime. I recommend it for small businesses and, in some cases, medium-sized companies.

I would rate the overall solution a seven out of ten. 

The primary use case is for learning purposes. A load balancer is used to redirect sites. It is used for managing traffic in cloud infrastructure, utilizing the traffic of multiple cloud servers or a website uploaded on AWS, and matching traffic in simple terms.

It can help manage traffic. That is our biggest benefit in Windows and in VNet both. Also, it can increase the response time because manually attaching some volumes and storage can take more time, but in load balancing, it takes less time.

The overall EC2 instance is best for learning purposes. I have used the application load balancer because it has an easy-to-understand interface, which is beneficial for traffic management. Elastic Load Balancer can distribute traffic easily through various gateways.

I am not aware of any features not available because I have less experience using Elastic Load Balancer, focusing more on Application Load Balancer.

I have hands-on experience with load balancer for around one month.

I find it stable, and I do not face any performance issues currently.

I find it scalable. I can scale the EC2 instance where I can create an instance of approximately twenty GB and attach the S3 bucket and volume to increase its storage.

I have not required any technical support because I am using the free tier of AWS. However, I understand that if we face issues and pay for AWS, they provide technical support in three steps, with varying levels of service depending on payment.

Neutral

I do not work with any other products for load balancing. I primarily use AWS and application and Elastic Load Balancer.

The initial setup was easy due to the user-friendly AWS interface. You first need to create the instance because, without an instance, the load balancing is useless. Then, you create the target group and attach the target group to the load balancer.

I use the free tier of AWS, so I do not have much experience with setup costs or licensing.

I would recommend Amazon Elastic Load Balancing because it is easy to understand. The UI is very understandable, and AWS is more stable than GCP and Microsoft Azure.

Elastic Load Balancer is used to maintain requests and distribute traffic on target groups. The target could be any type of instances, IPs, or Lambda functions. Most of the time, the target group is an instance.

I appreciate the checks that Elastic Load Balancer performs with the instances to ensure they are running properly. 

Additionally, the Grid feature is impactful as it checks that instances are properly configured and running.

Sometimes the target group takes too much time to configure or to be seen on the internet, especially when configuring through ISV tools.

I have been working with Amazon Elastic Load Balancing for more than one year.

I find Amazon Elastic Load Balancing to be stable.

Amazon Elastic Load Balancing is scalable.

Neither I nor my team have needed to escalate to tech support for now.

Positive

I worked with Azure Load Balancer previously. AWS is very user-friendly compared to Azure, which requires many steps to configure a simple load balancer.

The initial setup is sometimes complex, however, after working on it for one or two months, it becomes very easy.

I create a separate security group for Elastic Load Balancer, then proceed with the target group or listener rules.

Amazon Elastic Load Balancing has shown great performance and efficiency, especially in high-traffic e-commerce applications during sales times.

I have experience with Azure Load Balancer.

I recommend Amazon Elastic Load Balancing for high-traffic web applications because it performs great.

I'd rate the solution ten out of ten.

Amazon Elastic Load Balancing is used to automatically scale up and down the number of server nodes we have. For example, if we wanted to provision an EC2 machine as our website server, this one machine might not be able to handle an increase in traffic.

If the traffic increases, AWS will automatically add one more machine, which is an exact copy of the other machine, and that will take the additional node. With Amazon Elastic Load Balancing, you set the minimum and maximum limits. For example, at minimum, you should have two servers; at maximum, you can have four servers. So the number of servers can oscillate between two and four depending on the traffic.

The most valuable feature of Amazon Elastic Load Balancing is scaling. We just have to enable the load balancer, set the minimal and maximum limits, and it will handle everything by itself.

We faced a problem once. The different machines created by Amazon Elastic Load Balancing have separate IP addresses. These machines, in turn, connect to our MongoDB Service. Since MongoDB has an IP address-based firewall in the middle, it will only allow IP addresses you have whitelisted.

So whenever the solution creates a new machine, we have to add the IP address to our MongoDB whitelist. Whenever it deletes and recreates, the old IP address becomes invalid. This causes our connections to break, and our customers don't get the data. The machines created by Amazon Elastic Load Balancing have different IP addresses, which we are not able to whitelist or predict.

My organization has been using Amazon Elastic Load Balancing for more than one year.

Two people are using the solution in our organization.

Amazon Elastic Load Balancing’s initial setup is very easy.

We use the solution on-cloud. A load balancer's auto-scaling service is always needed when we set up a dedicated server because we cannot do the scaling manually. We used a load balance for our server-based approaches, but we don't need a load balancer for our serverless approaches.

Overall, I rate Amazon Elastic Load Balancing nine out of ten.

We use the tool for load balancing.

The tool integrates well with Amazon native services. Its valuable feature is integrations.

The product should be made as an alternative to Amazon services. It would be easier for us if you got one service that is available everywhere.

I rate Amazon Elastic Load Balancing's scalability an eight out of ten. 

The tool's deployment is simple. Follow the instructions from AWS, and it can be completed in a day.

I have no issues with the tool's pricing. 

I rate the tool an eight out of ten and recommend it to others.

Our company is an AWS partner that sets up, integrates, and supports the solution for our customers. We use the solution's load balancing and auto-scaling features. 

Forty-two current staff members use the solution and one of our banking customers exceeds one million end users on the customer-facing application. 

The solution offers good load balancing. 

The solution needs to guarantee stability because multiple loads behind a load balancer can cause service unavailability.

I am not sure if this service currently exists, but it would be beneficial to customers to offer a network load balancer from IoT devices.

I have been using the solution for three years. 

The solution is generally stable but there were two issues that shut down service. I rate the stability a nine out of ten. 

The solution is easy to scale but my customers don't use that feature. 

When multiple loads behind a load balancer caused service unavailability, we completed a support ticket. We knew the exact load with issues and requested a restart to restore service. We knew this was the proper resolution based on past experience with the same issue. 

Support was not ready to agree that the load had actually gone down which delayed a restart to restore service. Our experience would have been better had support acted immediately on the service ticket rather than taking time to investigate. Support response was fast but the resolution was not and as a result, our customers were not happy. 

Positive

The initial setup was easy with no issues. 

The solution is priced well and I rate it a ten out of ten. 

Our customer required the use of this solution so we did not evaluate other options. 

I rate this solution a nine out of ten. 

We have a public-based application where we are using Elastic Load Balancing. It supports our AI-driven applications, though currently, I am not using it for that purpose.

The only thing that could be improved is their technical support. The first level contact needs to be more quick.

I have been working with Amazon Elastic Load Balancing for five years.

Customer support is good. However, the first level contact requires a more quick response. They charge for technical support depending on the support model required.

Neutral

I have not worked with similar products before Amazon Elastic Load Balancing.

Amazon Elastic Load Balancing is cheaper when compared to other major public load balancers like Azure and GCP. Each Amazon service has its own charges, and additional technical support incurs extra costs based on the support model selected.

Everyone uses load balancers when the application is public-facing as there are no other choices.

I'd rate the solution eight out of ten.

We use the tool to move the target location from one location to another.

The product automatically distributes our incoming traffic to multiple targets like EC2 instances, containers, and IP addresses in one or more availability zones. If one instance fails, the product automatically creates another instance. Security and monitoring for high-performance applications are some of the top features. We can perform health checks using the target keyword in ALB.

We faced some issues with the health check. I had to check the EC2 instances and ELB. It worked properly after that. Auto Scaling must be improved.

I have used the solution in the past year.

We use Auto Scaling. If an instance goes down, it creates a new instance.

The initial setup is easy.

The product is not cheap. It is a pay-as-you-go model. It costs us $30 per month.

I work mostly on DevOps tools. I like to work on AWS. I will recommend the tool to others. Overall, I rate the solution an eight out of ten.