Question

Difficulty: MediumCloudWatch Metrics and Alarms

A SysOps Administrator is designing an automated remediation workflow for a critical microservice running on Amazon EC2 instances. The microservice publishes a custom metric named QueueBacklog to Amazon CloudWatch every minute. The administrator needs to configure a CloudWatch metric alarm that triggers an AWS Systems Manager (SSM) Automation document to remediate the backlog when the metric exceeds 500 for three consecutive evaluation periods.

Which two configurations must the administrator perform to meet these requirements? (Select TWO.)

  1. Configure the CloudWatch metric alarm with a Period of 60 seconds and set the Evaluation Periods to 3.Answer
  2. Create an Amazon EventBridge rule that triggers when the CloudWatch alarm state changes to ALARM, and set the rule target to the Systems Manager Automation document.Answer
  3. C
    Enable detailed monitoring on the EC2 instances to allow custom metrics to be collected and processed at 1-minute intervals.
  4. D
    Configure the CloudWatch metric alarm action to publish directly to an Amazon Simple Queue Service (Amazon SQS) queue configured as the event source for the Systems Manager Automation document.
  5. E
    Configure the CloudWatch metric alarm with a Period of 300 seconds to align with the default standard monitoring interval of custom metrics.

Answer

Configure the CloudWatch metric alarm with a Period of 60 seconds and set the Evaluation Periods to 3, and create an Amazon EventBridge rule that triggers when the CloudWatch alarm state changes to ALARM, setting the rule target to the Systems Manager Automation document.
To evaluate a custom metric at 1-minute intervals for three consecutive periods, the CloudWatch alarm must be configured with a period of 60 seconds and an evaluation period of 3. Furthermore, CloudWatch alarms cannot directly initiate Systems Manager Automation documents as an alarm action. To achieve this, an Amazon EventBridge rule must be created to detect the alarm's state change to ALARM and target the Systems Manager Automation document.

Step-by-Step Solution

1
Set the alarm evaluation period and granularity.
The CloudWatch alarm is configured with a period of 60 seconds (1 minute) and evaluation periods set to 3.
This matches the 1-minute reporting interval of the custom metric and ensures the alarm triggers only after three consecutive 1-minute periods of exceeding the threshold.
2
Configure the remediation integration path.
An Amazon EventBridge rule is created to match CloudWatch alarm state change events.
Since CloudWatch alarms cannot natively target Systems Manager Automation documents directly as an action, EventBridge must be used to intercept the state change and route the event to the automation target.

Key Concept

CloudWatch Metric Alarms can monitor custom metrics at specific granularities (periods) and require Amazon EventBridge to trigger AWS Systems Manager Automation for automated remediation.
Rate this question