How many Nodes/Requested does Created/Manage by 1 ELB

0

I am new to ELB, Wanted to use Application load balancer. Total count of web users are near to 1k so How many ALB needed to manage these requests. How many nodes will be created by 1 ELB. How many EC2 can be configured to 1 ELB. Is it good to even go with 1 ELB to handle 4 EC2 or Go with 1 EC2 in which Apache load balancer install to handle these 4 EC2 since it is open source?

2 Answers
1
Accepted Answer

How many ALB needed to manage these requests?

I believe one ALB will work just fine. ALB will scale based on incoming traffic.

How many nodes will be created by 1 ELB?

At least one per availability zone. Additional nodes are added in case of scaling.

How many EC2 can be configured to 1 ELB?

You usually configure/create target groups in which you place targets. In your case EC2 instances. Per docs, there is a limit of 100 target groups per ALB and a limit of 1000 targets per ALB. Check this link: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-limits.html

Is it good to even go with 1 ELB to handle 4 EC2 or Go with 1 EC2 in which Apache load balancer install to handle these 4 EC2 since it is open source?

If you go with EC2 and apache then you will have to manage it on your own (ensure HA, scaling, patching). ALB is the better option here.

weex
answered 20 days ago
  • How many requests 1 ALB can handle?

  • There is no exact number or at least I could not find it in the docs. ALB will scale up aggressively as your traffic increases. In theory, it can handle an unlimited number of requests. In some cases, ALB may return 503 errors if it is not able to scale up fast enough. This can happen if your baseline traffic is low and you have sudden request spikes. In cases like that, there is an option to pre-warm ALB. You could hit ALB with requests in advance to force it to scale, but the best practice is to contact AWS support to do it for you. Anyway, you should test it with your expected traffic and see how it behaves for your use case. Reference: https://aws.amazon.com/articles/best-practices-in-evaluating-elastic-load-balancing/#pre-warming

0

In your query you have mentioned about Apache load balancer. ALB is almost similar in that functionality with 2 more benefits. 1. Managed by AWS so you don't take overhead of managing it. In Apache since you will be deploying it then it becomes your responsibility of managing. 2. Cloud Native service - That means it will fit and can be used by other AWS services. ALB is one of the ELB type. There are Network Load Balancing and Gateway Load Balancing. https://docs.aws.amazon.com/elasticloadbalancing/index.html

Now coming to choosing the number of EC2 in your ELB(specifically ALB) can be done in the following manner.

  1. Using target groups based on the request from client. Create listeners to check for connection requests from clients, and listener rules to route requests from clients to the targets in one or more target groups.
  2. Use auto scaling group in control the number of EC2 instances. It has min and max values. For the specific use case you have mentioned go ahead min as 1 and max as 3. To use Elastic Load Balancing with your Auto Scaling group, attach the load balancer to your Auto Scaling group. You can see further details here. https://docs.aws.amazon.com/autoscaling/ec2/userguide/autoscaling-load-balancer.html
Biswa
answered 19 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions