An Amazon EC2 Auto Scaling group (ASG) is registered with an Application Load Balancer (ALB). The ASG has a minimum size of 3, a desired capacity of 3, and a maximum size of 5. To troubleshoot a database connectivity issue, a SysOps administrator temporarily suspends the Launch process for the ASG. Shortly after, one of the three EC2 instances fails its ALB health check and is marked unhealthy.
What will happen to the unhealthy instance and the capacity of the Auto Scaling group?
- AThe Auto Scaling group will leave the unhealthy instance running and take no action until the Launch process is resumed.
- The Auto Scaling group will terminate the unhealthy instance, leaving the group with 2 running instances, and will not launch a replacement.Answer
- CThe Auto Scaling group will automatically resume the Launch process to maintain the minimum capacity of 3 and then replace the instance.
- DThe Auto Scaling group will wait for the scale-in cooldown period to expire before terminating the instance and launching a replacement.
Answer
The Auto Scaling group will terminate the unhealthy instance, leaving the group with 2 running instances, and will not launch a replacement.
The correct answer is that the Auto Scaling group will terminate the unhealthy instance, leaving the group with 2 running instances, and will not launch a replacement. When the Launch process is suspended, the ReplaceUnhealthy process is still allowed to terminate instances that fail health checks, but it cannot launch new ones to replace them. This can temporarily reduce the capacity of the Auto Scaling group below its minimum size limit.
Step-by-Step Solution
Key Concept
Auto Scaling Process Suspension Behavior
Estimated Time:1m 30s