- Newest
- Most votes
- Most comments
When you create an elastic load balancer, a default level of capacity is allocated and configured. As Elastic Load Balancing sees changes in the traffic profile, it will scale up or down. The time required for Elastic Load Balancing to scale can range from 1 to 7 minutes, depending on the changes in the traffic profile. When Elastic Load Balancing scales, it updates the DNS record with the new list of IP addresses. To ensure that clients are taking advantage of the increased capacity, Elastic Load Balancing uses a TTL setting on the DNS record of 60 seconds. It is critical that you factor this changing DNS record into your tests. If you do not ensure that DNS is re-resolved or use multiple test clients to simulate increased load, the test may continue to hit a single IP address when Elastic Load Balancing has actually allocated many more IP addresses. Because your end users will not all be resolving to that single IP address, your test will not be a realistic sampling of real-world behavior.
Refer: https://aws.amazon.com/articles/best-practices-in-evaluating-elastic-load-balancing/
Relevant content
- asked 3 years ago
- asked a year ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
thank you. I understand how to update the IP address.
Do you know how the range of IP addresses to be updated is determined?
Thanks for your answer, it provide information for ELB scaling up. However, when the ELB scale down, what happens for revoked IP@ still in DNS cache ? Once they are no more resolved, do they still route to the ELB for some period longer than 60 sec ?