CloudWatch alarms in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an AWS CloudWatch alarm?

An AWS CloudWatch alarm watches a specific metric and sends a notification or takes an action when the metric crosses a set threshold.

beginner

Which metric data can CloudWatch alarms monitor?

CloudWatch alarms can monitor metrics like CPU usage, disk reads/writes, network traffic, or custom metrics you send to CloudWatch.

intermediate

What happens when a CloudWatch alarm state changes to ALARM?

When the alarm state changes to ALARM, it can send notifications (like email or SMS) or trigger automated actions such as scaling resources.

beginner

How do you define the threshold for a CloudWatch alarm?

You set a threshold value and a comparison operator (like greater than or less than) that the metric must cross to trigger the alarm.

intermediate

Can CloudWatch alarms monitor multiple metrics at once?

No, each CloudWatch alarm monitors a single metric or a math expression based on metrics, but not multiple separate metrics directly.

What does a CloudWatch alarm do when a metric crosses its threshold?

A Deletes the resource

B Sends a notification or triggers an action

C Automatically fixes the issue

D Stops monitoring the metric

CloudWatch alarms notify or trigger actions when thresholds are crossed, but they do not delete resources or fix issues automatically.

Which of these can be used as a CloudWatch alarm action?

A Modify the metric data

B Change the AWS region

C Send an email notification

D Create a new AWS account

CloudWatch alarms can send notifications like emails or SMS, but cannot change regions, create accounts, or modify metric data.

What is required to create a CloudWatch alarm?

A A database instance

B An AWS IAM user only

C A CloudFormation template

D A metric and a threshold

To create a CloudWatch alarm, you need to specify a metric to watch and a threshold to trigger the alarm.

Can CloudWatch alarms monitor custom metrics?

A Yes, if you send custom metrics to CloudWatch

B No, only AWS default metrics

C Only metrics from EC2 instances

D Only metrics from S3 buckets

CloudWatch supports monitoring custom metrics that you send, not just default AWS metrics.

What state does a CloudWatch alarm enter when the metric is within normal range?

A OK

B ALARM

C INSUFFICIENT_DATA

D ERROR

When the metric is normal, the alarm state is OK. ALARM means threshold crossed, and INSUFFICIENT_DATA means not enough data.

Explain how a CloudWatch alarm works and what it can do when triggered.

Think about watching a number and reacting when it gets too high or low.

Describe the steps to create a CloudWatch alarm for monitoring CPU usage.

Imagine setting a speed limit and getting a warning if you go over.

Practice

1. What is the primary purpose of an AWS CloudWatch alarm?

easy

A. To store large amounts of log data

B. To monitor a specific metric and notify when it crosses a threshold

C. To create virtual servers in the cloud

D. To manage user permissions and roles

Solution

1. Step 1: Understand CloudWatch alarm function

   CloudWatch alarms watch metrics like CPU usage or disk space and alert you when values cross set limits.

2. Step 2: Identify the correct purpose

   Only To monitor a specific metric and notify when it crosses a threshold describes monitoring a metric and notifying on threshold crossing, which is the alarm's job.

3. Final Answer:

   To monitor a specific metric and notify when it crosses a threshold -> Option B

4. Quick Check:

   Alarm = Monitor + Notify [OK]

Hint: Alarms watch metrics and alert on changes [OK]

Common Mistakes:

• Confusing alarms with log storage
• Thinking alarms create servers
• Mixing alarms with user management

2. Which of the following is the correct way to specify a CloudWatch alarm threshold for CPU utilization above 80%?

easy

A. "Threshold": "<=80"

B. "Threshold": 80, "ComparisonOperator": "LessThanThreshold"

C. "Threshold": 80, "ComparisonOperator": "LessThanOrEqualToThreshold"

D. "Threshold": 80, "ComparisonOperator": "GreaterThanThreshold"

Solution

1. Step 1: Understand threshold syntax

   CloudWatch alarms use a numeric Threshold value and a separate ComparisonOperator like GreaterThanThreshold, LessThanThreshold.

2. Step 2: Choose operator for above 80%

   To alert when CPU is above 80%, use "Threshold": 80, "ComparisonOperator": "GreaterThanThreshold".

3. Final Answer:

   "Threshold": 80, "ComparisonOperator": "GreaterThanThreshold" -> Option D

4. Quick Check:

   Above 80% = GreaterThanThreshold(80) [OK]

Hint: Use GreaterThanThreshold for above threshold [OK]

Common Mistakes:

• Using < instead of > for above threshold
• Using = which triggers only at exact value
• Confusing <= with above threshold

3. Given this CloudWatch alarm configuration snippet:

{"MetricName": "CPUUtilization", "Namespace": "AWS/EC2", "Threshold": 70, "ComparisonOperator": "GreaterThanThreshold", "EvaluationPeriods": 3}

What happens if CPU utilization is 75% for 2 consecutive periods and then 65% for the third period?

medium

A. The alarm does not trigger because CPU was not above 70% for all 3 periods

B. The alarm triggers only if CPU is above 70% for 4 periods

C. The alarm triggers immediately when CPU hits 75% the first time

D. The alarm triggers because CPU was above 70% twice

Solution

1. Step 1: Understand EvaluationPeriods meaning

   The alarm triggers only if the metric breaches the threshold for the specified number of consecutive periods (3 here).

2. Step 2: Analyze given CPU values

   CPU was above 70% for 2 periods, then dropped below on the 3rd, so the alarm does not trigger.

3. Final Answer:

   The alarm does not trigger because CPU was not above 70% for all 3 periods -> Option A

4. Quick Check:

   3 periods breach needed, only 2 met [OK]

Hint: Alarm needs all evaluation periods breached [OK]

Common Mistakes:

• Thinking alarm triggers after any single breach
• Ignoring EvaluationPeriods count
• Assuming alarm triggers immediately

4. You created a CloudWatch alarm but it never enters ALARM state even when the metric crosses the threshold. What is a likely cause?

medium

A. The alarm's EvaluationPeriods is set higher than the number of metric data points

B. The alarm threshold is set too low

C. The alarm is configured to notify but not to monitor metrics

D. The SNS topic ARN configured in alarm actions is invalid

Solution

1. Step 1: Check EvaluationPeriods vs data points

   If EvaluationPeriods is more than available metric data points, alarm cannot evaluate properly.

2. Step 2: Confirm impact on alarm state

   Without enough data points, alarm never sees enough breaches to enter ALARM state.

3. Final Answer:

   The alarm's EvaluationPeriods is set higher than the number of metric data points -> Option A

4. Quick Check:

   EvaluationPeriods > data points = no alarm [OK]

Hint: Ensure enough data points for EvaluationPeriods [OK]

Common Mistakes:

• Assuming threshold too low prevents alarm
• Confusing notification with monitoring
• Thinking invalid SNS prevents alarm state

5. You want to create a CloudWatch alarm that triggers an auto-scaling action when average CPU utilization exceeds 60% for 5 minutes, but only if this happens during business hours (9 AM to 5 PM). Which approach best achieves this?

hard

A. Create a CloudWatch alarm with threshold 60% and EvaluationPeriods 1, then use EventBridge to trigger scaling only during business hours

B. Set the alarm threshold to 60% and EvaluationPeriods to 5, and configure the alarm to be active only during business hours

C. Create a CloudWatch alarm with threshold 60% and EvaluationPeriods 5, then use a Lambda function triggered by the alarm to check time and trigger scaling

D. Set the alarm threshold to 60% and EvaluationPeriods 5, and configure auto-scaling to ignore alarms outside business hours

Solution

1. Step 1: Understand alarm and time condition needs

   CloudWatch alarms alone cannot restrict triggering by time; external logic is needed.

2. Step 2: Evaluate options for time-based control

   Using a Lambda triggered by the alarm to check current time and decide on scaling is flexible and precise.

3. Step 3: Assess other options

   EventBridge can schedule events but not filter alarm triggers by time; auto-scaling ignores alarms is not a feature.

4. Final Answer:

   Create a CloudWatch alarm with threshold 60% and EvaluationPeriods 5, then use a Lambda function triggered by the alarm to check time and trigger scaling -> Option C

5. Quick Check:

   Alarm + Lambda time check = controlled scaling [OK]

Hint: Use Lambda to add time logic after alarm triggers [OK]

Common Mistakes:

• Expecting alarm to handle time filtering alone
• Assuming auto-scaling ignores alarms by time
• Using EventBridge without alarm integration