An Auto Scaling group (ASG) uses a step scaling policy based on the `CPUUtilization` metric. The EC2 instances in the ASG require approximately minutes to run bootstrapping scripts and start processing tasks. During traffic spikes, the SysOps administrator observes that the ASG launches additional instances every minutes before the previously launched instances can finish bootstrapping, resulting in over-provisioning. Additionally, the ASG is slow to trigger scaling actions when traffic initially spikes because the CPU utilization data points are evaluated at -minute intervals. Which actions should the SysOps administrator take to resolve these issues? (Select TWO.)
- Enable detailed monitoring in the launch template used by the Auto Scaling group.Answer
- Increase the estimated instance warmup time in the step scaling policy to seconds.Answer
- CIncrease the default cooldown period of the Auto Scaling group to seconds.
- DConfigure standard monitoring and reduce the CloudWatch alarm evaluation period to minute.
- EAttach an IAM policy with `iam:PassRole` permissions to the EC2 instances' instance profile.
Answer
Enable detailed monitoring in the launch template used by the Auto Scaling group, and increase the estimated instance warmup time in the step scaling policy to seconds.
The correct solution involves enabling detailed monitoring to get -minute EC2 metrics, which allows the CloudWatch alarms to react faster, and increasing the estimated instance warmup time to seconds ( minutes) so that the step scaling policy allows newly launched instances to complete bootstrapping before initiating further scaling actions.
Step-by-Step Solution
Key Concept
Auto Scaling step scaling policies utilize estimated instance warmup to manage scaling frequency during instance bootstrapping, and detailed monitoring enables -minute metric granularity to improve scaling responsiveness.