An Amazon EC2 Auto Scaling group (ASG) is experiencing delayed scaling responses during sudden spikes in application traffic. A SysOps administrator notices that it takes up to 5 minutes for the ASG to trigger a scale-out action based on the average CPU utilization metric. Which two configuration updates should the administrator perform to reduce this scaling delay? (Select TWO.)
- Enable detailed monitoring in the launch template used by the Auto Scaling group.Cevap
- Decrease the period of the CloudWatch alarm that triggers the scaling policy to 1 minute.Cevap
- CIncrease the default instance cooldown period in the Auto Scaling group configuration.
- DEnable Auto Scaling group group-level metrics collection with 1-minute granularity in the group settings.
- EAttach an IAM policy with the iam:PassRole permission to the Auto Scaling group's IAM role.
Cevap
To reduce the scaling delay, enable detailed monitoring in the launch template used by the Auto Scaling group and decrease the period of the CloudWatch alarm that triggers the scaling policy to 1 minute.
To resolve the 5-minute scaling delay, both the metric reporting frequency and the alarm evaluation window must be updated. Enabling detailed monitoring in the launch template changes the EC2 metric reporting interval from 5 minutes to 1 minute. Decreasing the CloudWatch alarm period to 1 minute ensures that the alarm evaluates these high-frequency metrics promptly to trigger the scale-out policy.
Adım Adım Çözüm
Anahtar Kavram
Auto Scaling responsiveness depends on both the metric reporting frequency (detailed monitoring) and the alarm evaluation period.