Amazon Elastic Load Balancing Reviews

Application Load Balancer is required for redirecting two or more instances. We have got two EKS instances running. So, we have to connect in a round-robin fashion based on when a request needs to be sent to one EKS and when it needs to be sent to another EKS. For this purpose, we use Application Load Balancer.

It has very good features. It is very configurable. Security with TLS, et cetera is also very easy. 

It is good performance-wise, and the logging mechanism is also very good because we get the VPC log whenever a request comes. So, we can easily find out where the request is coming from.

One issue that we faced with ALB was that leaf-level certificate validation was not happening. It is not that user-friendly in that aspect. 

It is stable. I would rate it an eight out of ten in terms of stability.

We have more than 200 users, and we have 40 technical people.

I have never reached out to them.

Its initial setup is straightforward.

There is a yearly license.

I would recommend this solution. I would rate it an eight of ten.

We have a lot of customers who are currently not on Amazon; they are running on-premise data centers. When they ask us to migrate, we migrate their applications to Amazon. Load Balancing is often a component we use. We use HTTPS port 443, and we integrate the load balancer with the applications.

• Very easy to implement.
• Very well integrated into Amazon's services.

It would be good if we had a product that integrates well with third-party vendors. Some of our customers want a multi-cloud solution. They don't want to be tied up to or be in just one cloud. In that case, a third-party solution that could integrate with the cloud as well as with on-premise would be great.

Reporting would be a good feature as well.

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

So far it has not given us any problem. It's always running, 24/7.

The workload that we have put on it has not required surplus scalability. It has been able to handle our customers' loads. We have not come across a situation where massive scalability has been required, so far, and we have implemented it for large companies.

We have not reached out to support so far, for Amazon Elastic Load Balancing. 

We do have their API Gateway and we have had to reach out to support twice. The API gateway nodes went down and they had to restart the nodes. I consider API Gateway as also having some kind of internal load balancing.

The setup is straightforward. It took a couple of hours, with one person involved.

I have not seen other products so that I can compare them and tell you the Amazon solution needs improvement. So far, its functionality has been enough for the projects we have done.

We have not used the network load balancer so far in Amazon. We have only used the application load balancer. As far as an application load balancer is concerned, it doesn't require any additional features.

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.