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. 

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. 

In my company, we use it to post, you know, a variety of business applications, like ERP, finance applications, and legal applications, which we post using EC2 instances.

The most valuable feature of the solution is its pay-as-you-go model. You don't pay when you shut down the instances.

The product's stability is an area with a slight shortcoming, which can be improved.

I have been using Amazon Elastic Load Balancing for six years. I use the solution's latest version. I am a customer of the solution.

Stability-wise, I rate the solution a nine out of ten.

It is a very scalable solution in which you can add more servers instantly. I rate the scalability of the product a nine out of ten.

The solution can handle a lot of load, and you don't need to do anything since it will just scale up and down as and when the load increases or decreases, respectively.

There are thousands of users of various applications, and whoever wants to use an application has to use a load balancer.

The initial setup phase is very easy.

The solution can be deployed in a few minutes.

The licensing cost cannot be considered as expensive since I feel it is a reasonably priced product. You need to pay no licensing fee, but you need to pay based on the amount of traffic handled by the load balancer. The licensing fees are based on the number of connections one uses. It is a free tool for a certain amount of connections, which runs into thousands, and after that, there is a certain amount to be paid to Amazon. The product prepares a bill for you based on the number of hours and the amount of data processed.

One should use it if one wants their application to be resilient, highly available, and scalable.

I rate the overall solution a nine out of ten.

I use Amazon Elastic Load Balancing with EC2 instances to distribute traffic. I also incorporate Lambda for serverless technology and disaster recovery for backup across multiple availability zones. 

Additionally, AWS Backup is utilized for regular backups, and VPC is used for network configuration and traffic management.

The most valuable feature is the Lambda function due to its utility with serverless technology. It allows deployment of code without a server and facilitates connection between multiple services. This automatic functionality is highly beneficial for serverless technology. 

Additionally, Amazon Elastic Load Balancing is excellent for traffic management and security.

Clients sometimes face issues with Amazon Elastic Load Balancing, and it can take a long time to detect these issues. Although Amazon Elastic Load Balancing is effective for managing traffic and security bases, the delay in issue detection is an area for improvement.

I have been using Amazon Elastic Load Balancing for around one year.

I have not faced any stability issues with Amazon Elastic Load Balancing. I know how to use it effectively, which helps in avoiding problems.

The scalability of Amazon Elastic Load Balancing is straightforward. It allows for easy scaling up or down of data.

The support team at Amazon is excellent. In my experience of generating more tickets with AWS support, they were very supportive and understanding, solving issues swiftly within one or two days.

Positive

I would recommend Amazon Elastic Load Balancing because it is very useful for companies that have a heavy server load. It is beneficial for managing traffic and ensuring security. 

I rate Amazon Elastic Load Balancing as eight out of ten. While it is excellent in its core functionalities, it sometimes takes a long time to detect client issues, which affects its perfect rating.

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.

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.

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.

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. 

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.

We use the solution in our application deployment by configuring the server with the customer's specific port.

Amazon Elastic Load Balancing transfers the data securely from servers to users and splits the traffic based on peak times.

I have been using Amazon Elastic Load Balancing for two years and eight months.

I rate the solution a nine out of ten for stability.

Amazon Elastic Load Balancing is a scalable solution.

I rate the solution a nine out of ten for scalability.

The solution’s technical support is good.

The solution’s initial setup is easy.

It takes around five to ten minutes to deploy the solution.

The solution's pricing is $30 per month.

Once, the external network load balancer was not working because of the server-side change. The server had changed the certificate to a TLS version. We were unable to edit the security policy as a TLS version with the network load balancer. So, I created the classic load balancer instead of the network load balancer, and we're able to edit the security policy as the TLS version.

I would recommend Amazon Elastic Load Balancing to other users.

Overall, I rate the solution a nine out of ten.

I am using the solution to manage the front end of the application. I have a service where multiple clients log in for usage. The solution helps in load balancing by distributing the traffic to the application.

The solution's most valuable feature is the ease of use. It is more convenient to use compared to self-hosted load balancers.

They should improve the solution's pricing.

I have been using the solution for ten months.

It is a stable solution.

I rate the solution's scalability as a nine. It helps me manage around 100 end users of my application service.

The solution's support team is helpful.

Positive

The services offered by the solution and its competitors are almost similar. But Amazon is much more stable than them. Although, I don't have any quantifiable evidence.

The solution itself has simple functionality. It is straightforward to deploy and doesn't require maintenance.

The solution is expensive. I rate its pricing as a three.

I rate the solution as an eight.