- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I could be wrong here, but I thought pre-warming ELB's is no longer required. Can you cite any AWS documentation?
Yes, that is correct. Any official reference stating that with ALB pre-warming "Elastic Load Balancing scales your load balancer as traffic changes over time."? Scales out up to what max instances?
As ALB is a managed service, the exact way in which it scales behind the scenes is an implementation detail that AWS managers on your behalf.
This does not affect EC2 instances behind the ALB in an autoscaling group, as an example.
ELB will scale out - will send a request to ASG to add instance? How can the ALB add instances? Doesn't it make the ASG irrelevant, if the ALB add instances in this case?
ALB pre-warming scales the ALB, not the ASG or anything the ALB sends traffic to. If you're going to need ALB pre-warming, you also need to manage the ASG behind that ALB to make sure it can handle the traffic volume you're expecting.
What does it do in addition to allowing 10x or more traffic? Any impact on the back-end like ASG?
Can you help me understand your use case for ALB pre-warming? As an example, are you expecting a flash of traffic at a certain time (such as may be experienced when launching a brand new product at a marquee event that you believe will drive significantly more traffic than your site currently handles with very little ramp up). Elastic Load Balancing scales your load balancer as traffic changes over time. For the vast majority of workloads, the scaling offered by ALBs can handle increases in traffic.
What will be the correct answer for this question?
Your application currently leverages AWS Auto Scaling to grow and shrink as load Increases/ decreases and has been performing well. Your marketing team expects a steady ramp up in traffic to follow an upcoming campaign that will result in a 20x growth in traffic over 4 weeks. Your forecast for the approximate number of Amazon EC2 instances necessary to meet the peak demand is 175. What should you do to avoid potential service disruptions during the ramp up in traffic?
A. Ensure that you have pre-allocated 175 Elastic IP addresses so that each server will be able to obtain one as it launches
B. Check the service limits in Trusted Advisor and adjust as necessary so the forecasted count remains within limits.
C. Change your Auto Scaling configuration to set a desired capacity of 175 prior to the launch of the marketing campaign
D. Pre-warm your Elastic Load Balancer to match the requests per second anticipated during peak demand prior to the marketing campaign
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
What will be the correct answer for this question?
Your application currently leverages AWS Auto Scaling to grow and shrink as load Increases/ decreases and has been performing well. Your marketing team expects a steady ramp up in traffic to follow an upcoming campaign that will result in a 20x growth in traffic over 4 weeks. Your forecast for the approximate number of Amazon EC2 instances necessary to meet the peak demand is 175. What should you do to avoid potential service disruptions during the ramp up in traffic?