Skip to main content
TrustRadius
Elastic Load Balancing

Elastic Load Balancing

Overview

What is Elastic Load Balancing?

Amazon's Elastic Load Balancing automatically distributes incoming application traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can handle the varying load of your application traffic in a single Availability Zone or across…

Read more
Recent Reviews
Read all reviews
Return to navigation

Pricing

View all pricing

Gateway

$0.0125

Cloud
Partial Hour

Application

$0.0225

Cloud
Partial Hour

Network

$0.025

Cloud
Partial Hour

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is Elastic Load Balancing?

Elastic Load Balancing Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(14)

Attribute Ratings

Reviews

(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
At the moment we are looking at using the elastic load balancer provided by Amazon web services in a trial fashion. Our company has been migrating more and more of our in-house developed applications from on-site platforms to the AWS web platform. Part of this involves routing traffic across the newly deployed microservices and we are looking into using the elastic load balancer to help with this. So far it seems promising although our scale is admittedly low. We have not yet decided to migrate everything over to elb from our previous setup however results are promising as with anything else on the AWS suite the more we use it the more we like it. As far as business problems being addressed it's simply a matter of the security of being the host of the cloud versus having to maintain everything on site and as such the more options we use provided by Amazon web services the less we have to do ourselves.
  • Most obviously it works great for routing traffic between components hosted on Amazon web services
  • The ability to dynamically spin up connections is fantastic.
  • In general the ease of use and configuration is a selling point.
  • So far our experience has been limited with the ability for elb to handle transactions when only part of the platform is on Amazon web services.
It really is a straight-up situation. From my current experience if you have two or more services hosted on Amazon web services that need transactions between each other with a variable flow of traffic then elb is a fantastic method for routing that traffic and making sure that no one back and component gets overloaded with requests while other existing components are just standing there idle waiting for some traffic. As noted earlier in my review we are still doing a trial run with the service as not all of our components are hosted on AWS yet and we aren't having as great luck with transactions between hosted and non-hosted but that could also simply be a learning curve on our part.
  • Dynamically spitting off new connections as back end or front end services are spun up
  • Ease of integration within the AWS platform
  • The pay as you need the mentality of AWS in general and in specific with the elb is a wonderful benefit
  • Currently it is too soon to say for sure what kind of impact this will have.
  • The ideal goal is that this will be cheaper than having to host our own routing on site.
Again as noted we're still in the trial process seeing if we want to migrate over but the biggest benefit of elb is its interconnectivity with other Amazon web services hosted applications that our company is using and the in-house support from AWS. This is very attractive when routing traffic across various applications hosted in the cloud.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We are using Amazon Elastic Load Balancing for our digital learning platform, as part of our suite of AWS products, in order to keep abreast of the stress on our various network targets and make sure the loads between them remain balanced. We also use it to troubleshoot slowdowns or bottlenecks in the network by running the diagnostics that Amazon Elastic Load Balancing provides.
  • I like being able to check the status of the load on any of our targets, in real time
  • It is helpful to be able to run diagnostics when we have slowdowns in the network
  • Amazon Elastic Load Balancing integrates well with the other AWS products we are using
  • Occasionally we have a huge number of users using our network at once, and Amazon ELB isn't quite fast enough to scale effectively when that occurs. But this doesn't happen very often as our usage is usually quite stable
  • If we want to add another application to our learning suite, we would have to add another load balancer, which would incur additional cost
  • The setup was not easy and could really only be handled by one person on our team with the technical background to do so
Amazon Elastic Load Balancing is great if you are already using a lot of other Amazon Web Services applications. It is built to integrate well with those, so your implementation will go a lot smoother. If you're already using other cloud computing services from different companies, you will have a much slower and more difficult time with integrating Amazon Elastic Load Balancing into your suite of applications.
  • Integration with other AWS applications
  • Ability to run diagnostics on network slowdowns or bottlenecks
  • Customization of notifications so we can tell when the network is having issues based on our own benchmarks
  • Allows us to troubleshoot and address network issues, which improves our end user experience
  • Provides an integrated way to balance our network load without having to deal with other suites besides AWS, saving time and effort
  • Allows us to see the effects that different code changes have on our network performance, which means more efficient development on the back end
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use the Amazon Elastic Load Balancing as a single entry point for end-clients or end-users of the EC2 instances to distribute incoming traffic across all machines available in the different availability zones to receive requests. We use it across all applications we deploy to the different environments. It fits well with the security groups and auto-scaling settings.
  • Fair price for a all-featured load balancing solution
  • High availability and elasticity. It is secured by Amazon.
  • Integrates well with Amazon WAF
  • There are not a lot of cons but we can mention the need to always check the quotas for the ELB
We use Amazon Elastic Load Balancers to serve mobile applications and websites. It works really well. We have not had any problems until now. Last year we integrated the AWS ELB with the EC2 Auto Scaling and now we have a fully working elastic solution. We increase/decrease EC2s instances based on traffic over our load balancers.
  • Cost effective
  • Single integration with different apps (websites, mobile app, etc)
  • Improved security
  • Allow to create different load balancers based: ALB, CLB, NLB
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon Elastic Load Balancing] integrates great with those.
Amazon EC2 Auto Scaling, Amazon S3 (Simple Storage Service), Amazon Elastic Compute Cloud (EC2)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We decided to use Amazon Elastic Load Balancing in conjunction with Amazon EC2 Auto Scaling to host our websites. We have websites that have peak traffic on some periods of the year, so we needed an elastic infrastructure that helps us to serve our websites with no downtimes and good performance. And that's what we get using this platform. So, we now have more reliable websites.
  • Good price for a complete load balancing solution
  • Very useful rules editor on listener
  • Working in conjuction with AWS WAF, is a good option to protect your applications
  • Unsing certificates from Amazon Certficate Manager don't work well
  • On high traffic websites can be pricey
  • HTTP/2 implementation creates problems from time to time on Apple devices / Safari
We use AWS Elastic Load Balancers to serve websites. And for this purpose, works extremely well. In the past we used physical load balancers and that was very costly, and not to mention hard to work with on the server content replication side. Now, with AWS Elastic Load Balancers and EC2 Auto Scaling, we have a complete elastic solution, that works as it's supposed to be.
  • Cost effective solution: we now have more websites, that work better and we pay same as before migrating to AWS
  • Help us on improved security, allowing us to use AWS WAF
  • Rules on listeners allow us to do complicated stuff by ourselves
In the past we use physical Load Balancers. That solution works, but it had several negative points. The first, it was not elastic. It requires a physical server setup in order to work. Also a technician works for one or more days to set up the solution. And then, we had the servers, that weed to be replicated. That was very costly and requires several hours to process changes on the load balancer.

AWS ELB is a huge step and seriously, after trying it, can't go back to physical servers to serve websites.
Amazon Relational Database Service (RDS), AWS Firewall Manager, Adobe PhotoShop
AWS gives you several support plans. On the free plan, you basicaly need to google for help, but the good news is that AWS Elastic Load Balancing works. We has more than 15 load balancers and we never run into a problem that require support.

But you mght consider a support plan if you are going to do something more complex or critical
AWS Elastic Load Balancing has this trick. First, you need to know how it works. ELB is not the only piece here. ELB has a very close relation with AWS Target Groups. You create or select a target group every time you create a Load balancer. Target groups allow you to connect the load balancer to EC2 autoscaling groups, Lambda functions, or even a single EC2 instance.

While this sounds complex, it becomes easy, once you know his tricks. Thanks to the user interface, managing a ELB is an easy task. The rules editor is really useful, although it will need a bit of improvement to some interface items.
Return to navigation