What should the SysOps administrator do to meet these requirements in the MOST operationally efficient way?
Create a CloudWatch dashboard. Use activity notifications from the Auto Scaling group to invoke a custom AWS Lambda function. Use the Lambda function to update the CloudWatch dashboard to monitor the CPUUtilization metric for the new instance IDs.
Create a CloudWatch dashboard. Run a custom script on each EC2 instance to stream the CPU utilization to the dashboard.
Use CloudWatch metrics explorer to filter by the aws:autoscaling:groupName tag and to create a visualization for the CPUUtilization metric. Add the visualization to a CloudWatch dashboard.
Use CloudWatch metrics explorer to filter by instance state and to create a visualization for the CPUUtilization metric. Add the visualization to a CloudWatch dashboard.
Explanations:
This option involves a custom AWS Lambda function triggered by Auto Scaling activity notifications. While this could update the dashboard, it introduces unnecessary complexity and is less operationally efficient than using built-in CloudWatch features.
This option requires running a custom script on each EC2 instance to stream CPU utilization to the dashboard. This introduces additional management overhead and is not necessary for monitoring EC2 metrics in CloudWatch.
This option uses CloudWatch Metrics Explorer to filter by theaws:autoscaling:groupNametag, which automatically includes all EC2 instances in the Auto Scaling group. This is the most operationally efficient method, as it does not require additional configuration or scripts.
Filtering by instance state is not directly relevant to monitoring CPU utilization for EC2 instances in an Auto Scaling group. The correct filter would be by the Auto Scaling group name (aws:autoscaling:groupName) rather than instance state.
I deduce that the answer is:
Use CloudWatch metrics explorer to filter by the aws:autoscaling:groupName tag and to create a visualization for the CPUUtilization metric. Add the visualization to a CloudWatch dashboard.
I calculate that the answer is:
Use CloudWatch metrics explorer to filter by the aws:autoscaling:groupName tag and to create a visualization for the CPUUtilization metric. Add the visualization to a CloudWatch dashboard.