AWS Cloud Solutions Architect Trainee at Tuwaiq Academy
Real User
Top 20
2024-10-31T15:17:06Z
Oct 31, 2024
Improvement is needed in the integration with Terraform, especially in writing scripts for creating load balancers and target groups. The process could be made more user-friendly.
IT Manager at a tech services company with 1,001-5,000 employees
Real User
Top 20
2024-08-16T03:05:38Z
Aug 16, 2024
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.
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.
Find out what your peers are saying about Amazon Web Services (AWS), Microsoft, NetScaler and others in Application Delivery Controllers (ADC). Updated: November 2024.
The reporting could be simplified so that the client sees a report of what they cached at the end of the month and the number of hits. It should have metrics above and beyond their Google analytics, etc. You can't do that with the solutions from AWS. You have to build sophisticated cloud trails, reports, dashboards, etc. The setup is significant, and it's hard to manage. You'll need to hire someone or pay a consultant on a regular basis to manage it, and it's not for the faint of heart.
Director at AM Equipment & Services Private Limited
Real User
Top 5
2022-08-03T17:10:00Z
Aug 3, 2022
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.
Director at AM Equipment & Services Private Limited
Real User
Top 5
2020-04-12T07:27:00Z
Apr 12, 2020
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.
What is an application delivery controller (ADC)? An application delivery controller (ADC) is a network component that is primarily used to optimize and manage traffic flow as well as client connections to both web and application servers. ADCs also help with application acceleration and assist with application security. They are typically housed in a data center and their capabilities can be implemented using a hardware or software device. Because they can be installed via hardware or...
Improvement is needed in the integration with Terraform, especially in writing scripts for creating load balancers and target groups. The process could be made more user-friendly.
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.
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.
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.
The product's stability is an area with a slight shortcoming, which can be improved.
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.
They should improve the solution's pricing.
The reporting could be simplified so that the client sees a report of what they cached at the end of the month and the number of hits. It should have metrics above and beyond their Google analytics, etc. You can't do that with the solutions from AWS. You have to build sophisticated cloud trails, reports, dashboards, etc. The setup is significant, and it's hard to manage. You'll need to hire someone or pay a consultant on a regular basis to manage it, and it's not for the faint of heart.
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.
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 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.