Menu
Amazon CloudWatch
User Guide

Create Alarms That Stop, Terminate, Reboot, or Recover an Instance

Using Amazon CloudWatch alarm actions, you can create alarms that automatically stop, terminate, reboot, or recover your Amazon Elastic Compute Cloud (Amazon EC2) instances. You can use the stop or terminate actions to help you save money when you no longer need an instance to be running. You can use the reboot and recover actions to automatically reboot those instances or recover them onto new hardware if a system impairment occurs.

Every alarm action you create uses alarm action ARNs. One set of ARNs is more secure because it requires you to have the EC2ActionsAccess IAM role in your account. This IAM role enables you to perform stop, terminate, or reboot actions--previously you could not execute an action if you were using an IAM role. Existing alarms that use the previous alarm action ARNs do not require this IAM role, however it is recommended that you change the ARN and add the role when you edit an existing alarm that uses these ARNs.

The EC2ActionsAccess IAM role enables AWS to perform alarm actions on your behalf. When you create an alarm action for the first time using the Amazon EC2 or Amazon CloudWatch consoles, AWS automatically creates this role for you.

There are a number of scenarios in which you might want to automatically stop or terminate your instance. For example, you might have instances dedicated to batch payroll processing jobs or scientific computing tasks that run for a period of time and then complete their work. Rather than letting those instances sit idle (and accrue charges), you can stop or terminate them which can help you to save money. The main difference between using the stop and the terminate alarm actions is that you can easily restart a stopped instance if you need to run it again later, and you can keep the same instance ID and root volume. However, you cannot restart a terminated instance. Instead, you must launch a new instance.

You can add the stop, terminate, reboot, or recover actions to any alarm that is set on an Amazon EC2 per-instance metric, including basic and detailed monitoring metrics provided by Amazon CloudWatch (in the AWS/EC2 namespace), as well as any custom metrics that include the "InstanceId=" dimension, as long as the InstanceId value refers to a valid running Amazon EC2 instance.

Permissions

If you are using an AWS Identity and Access Management (IAM) account to create or modify an alarm, you must have the following permissions:

  • ec2:DescribeInstanceStatus and ec2:DescribeInstances — For all alarms on Amazon EC2 instance status metrics

  • ec2:StopInstances — For alarms with stop actions

  • ec2:TerminateInstances — For alarms with terminate actions

  • ec2:DescribeInstanceRecoveryAttribute and ec2:RecoverInstances — For alarms with recover actions

If you have read/write permissions for Amazon CloudWatch but not for Amazon EC2, you can still create an alarm but the stop or terminate actions won't be performed on the instance. However, if you are later granted permission to use the associated Amazon EC2 APIs, the alarm actions you created earlier will be performed. For more information, see see Permissions and Policies in the IAM User Guide.

If you want to use an IAM role to stop, terminate, or reboot an instance using an alarm action, you can only use the EC2ActionsAccess role. Other IAM roles are not supported. If you are using another IAM role, you cannot stop, terminate, or reboot the instance. However, you can still see the alarm state and perform any other actions such as Amazon SNS notifications or Auto Scaling policies.

If you are using temporary security credentials granted using the AWS Security Token Service (AWS STS), you cannot recover an Amazon EC2 instance using alarm actions.

Adding Stop Actions to Amazon CloudWatch Alarms

You can configure the stop alarm action using the Amazon EC2 console or the Amazon CloudWatch console. You can create an alarm that stops an Amazon EC2 instance when a certain threshold has been met. For example, you may run development or test instances and occasionally forget to shut them off. You can create an alarm that is triggered when the average CPU utilization percentage has been lower than 10 percent for 24 hours, signaling that it is idle and no longer in use. You can adjust the threshold, duration, and period to suit your needs, plus you can add an Amazon Simple Notification Service (Amazon SNS) notification, so that you will receive an email when the alarm is triggered.

Amazon EC2 instances that use an Amazon Elastic Block Store volume as the root device can be stopped or terminated, whereas instances that use the instance store as the root device can only be terminated.

To create an alarm to stop an idle instance using the Amazon EC2 console

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, under INSTANCES, click Instances.

  4. In the contents pane, right-click an instance, select CloudWatch Monitoring, and then click Add/Edit Alarms.

    Or, you can also select the instance, and then in the lower pane on the Monitoring tab, click Create Alarm.

  5. In the Alarm Details for dialog box, click Create Alarm.

  6. If you want to receive an email when the alarm is triggered, in the Create Alarm for dialog box, in the Send a notification to box, select an existing Amazon SNS topic, or click Create Topic to create a new one.

    If you create a new topic, in the Send a notification to box type a name for the topic, and then in the With these recipients box, type the email addresses of the recipients (separated by commas). Later, after you create the alarm, you will receive a subscription confirmation email that you must accept before you will get email for this topic.

  7. Select the Take the action check box, and then choose the Stop this instance radio button.

  8. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  9. In the Whenever boxes, choose the statistic you want to use and then select the metric. In this example, choose Average and CPU Utilization.

  10. In the Is boxes, define the metric threshold. In this example, enter 10 percent.

  11. In the For at least box, choose the sampling period for the alarm. In this example, enter 24 consecutive periods of one hour.

  12. To change the name of the alarm, in the Name this alarm box, type a new name.

    If you don't type a name for the alarm, Amazon CloudWatch will automatically create one for you.

    Note

    You can adjust the alarm configuration based on your own requirements before creating the alarm, or you can edit them later. This includes the metric, threshold, duration, action, and notification settings. However, after you create an alarm, you cannot edit its name later.

  13. Click Create Alarm.

To create an alarm to stop an idle instance using the Amazon CloudWatch console

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, click Alarms.

  4. Click Create Alarm, and then in CloudWatch Metrics by Category, under EC2 Metrics, select Per-Instance Metrics.

  5. In the list of metrics, select the instance and metric you want to create an alarm for. You can also type an instance ID in the search box to go the instance that you want.

  6. Select Average from the Statistic drop-down list.

  7. Select a period from the Period drop-down list, for example: 1 Day.

  8. Click Next, and then under Alarm Threshold, in the Name field, enter a unique name for the alarm, for example: Stop EC2 instance.

  9. In the Description field, enter a description of the alarm, for example: Stop EC2 instance when CPU is idle for too long.

  10. In the is drop-down list, select <.

  11. In the box next to the is drop-down list, enter 10 and in the for field, enter 1440.

    A graphical representation of the threshold is shown under Alarm Preview.

  12. Under Actions, click EC2 Action.

  13. In the Whenever this alarm drop-down list, select State is ALARM.

  14. In the Take this action drop-down list, select Stop this instance.

  15. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  16. Click Notification, and then in the Send notification to drop-down list, select an existing Amazon SNS topic or create a new one.

  17. To create a new Amazon SNS topic, select New list.

    In the Send notification to field, enter a name for the new Amazon SNS topic for example: Stop_EC2_Instance, and in the Email list field, enter a comma-separated list of email addresses to be notified when the alarm changes to the ALARM state.

    Important

    If you are creating a new topic or adding email addresses to an existing topic, each email address that you add will be sent a topic subscription confirmation email. You must confirm the subscription by clicking the included link before notifications will be sent to a new email address.

  18. In the navigation pane, click Create Alarm to complete the alarm creation process.

Adding Terminate Actions to Amazon CloudWatch Alarms

You can configure the terminate alarm action using the Amazon EC2 console or the Amazon CloudWatch console. You can create an alarm that terminates an EC2 instance automatically when a certain threshold has been met (as long as termination protection is not enabled for the instance). For example, you might want to terminate an instance when it has completed its work, and you don't need the instance again. If you might want to use the instance later, you should stop the instance instead of terminating it. For information about enabling and disabling termination protection for an instance, see Enabling Termination Protection for an Instance in the Amazon EC2 User Guide for Linux Instances.

To create an alarm to terminate an idle instance using the Amazon EC2 console

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, under INSTANCES, click Instances.

  4. In the upper pane, right-click an instance, select CloudWatch Monitoring, and then click Add/Edit Alarms.

    Or, select the instance and then in the lower pane, on the Monitoring tab, click Create Alarm.

  5. In the Alarm Details for dialog box, click Create Alarm.

  6. If you want to receive an email when the alarm is triggered, in the Create Alarm for dialog box, in the Send a notification to box, select an existing Amazon SNS topic, or click Create Topic to create a new one.

    If you create a new topic, in the Send a notification to box type a name for the topic, and then in the With these recipients box, type the email addresses of the recipients (separated by commas). Later, after you create the alarm, you will receive a subscription confirmation email that you must accept before you will get email for this topic.

  7. Select the Take the action check box, and then choose the Terminate this instance radio button.

  8. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  9. In the Whenever boxes, choose the statistic you want to use and then select the metric. In this example, choose Average and CPU Utilization.

  10. In the Is boxes, define the metric threshold. In this example, enter 10 percent.

  11. In the For at least box, choose the sampling period for the alarm. In this example, enter 24 consecutive periods of one hour.

  12. To change the name of the alarm, in the Name this alarm box, type a new name.

    If you don't type a name for the alarm, Amazon CloudWatch will automatically create one for you.

    Note

    You can adjust the alarm configuration based on your own requirements before creating the alarm, or you can edit them later. This includes the metric, threshold, duration, action, and notification settings. However, after you create an alarm, you cannot edit its name later.

  13. Click Create Alarm.

To create an alarm to terminate an idle instance using the Amazon CloudWatch console

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, click Alarms.

  4. Click Create Alarm, and then in CloudWatch Metrics by Category, under EC2 Metrics, select Per-Instance Metrics.

  5. In the list of metrics, select the instance and metric you want to create an alarm for. You can also type an instance ID in the search box to go the instance that you want.

  6. Select Average from the Statistic drop-down list.

  7. Select a period from the Period drop-down list, for example: 1 Day.

  8. Click Next, and then under Alarm Threshold, in the Name field, enter a unique name for the alarm, for example: Terminate EC2 instance.

  9. In the Description field, enter a description of the alarm, for example: Terminate EC2 instance when CPU is idle for too long.

  10. In the is drop-down list, select <.

  11. In the box next to the is drop-down list, enter 10 and in the for field, enter 1440.

    A graphical representation of the threshold is shown under Alarm Preview.

  12. Under Actions, click EC2 Action.

  13. In the Whenever this alarm drop-down list, select State is ALARM.

  14. In the Take this action drop-down list, select Terminate this instance.

  15. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  16. Click Notification, and then in the Send notification to drop-down list, select an existing Amazon SNS topic or create a new one.

  17. To create a new Amazon SNS topic, select New list.

    In the Send notification to field, enter a name for the new Amazon SNS topic for example: Terminate_EC2_Instance, and in the Email list field, enter a comma-separated list of email addresses to be notified when the alarm changes to the ALARM state.

    Important

    If you are creating a new topic or adding email addresses to an existing topic, each email address that you add will be sent a topic subscription confirmation email. You must confirm the subscription by clicking the included link before notifications will be sent to a new email address.

  18. In the navigation pane, click Create Alarm to complete the alarm creation process.

Adding Reboot Actions to Amazon CloudWatch Alarms

You can create an Amazon CloudWatch alarm that monitors an Amazon EC2 instance and automatically reboots the instance. The reboot alarm action is recommended for Instance Health Check failures (as opposed to the recover alarm action, which is suited for System Health Check failures). An instance reboot is equivalent to an operating system reboot. In most cases, it takes only a few minutes to reboot your instance. When you reboot an instance, it remains on the same physical host, so your instance keeps its public DNS name, private IP address, and any data on its instance store volumes.

Rebooting an instance doesn't start a new instance billing hour, unlike stopping and restarting your instance. For more information about rebooting an instance, see Reboot Your Instance in the Amazon EC2 User Guide for Linux Instances.

Important

To avoid a race condition between the reboot and recover actions, we recommend that you set the alarm threshold to 3 for 1 minute when creating alarms that reboot an Amazon EC2 instance.

To create an alarm to reboot an instance using the Amazon EC2 console

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, under INSTANCES, click Instances.

  4. In the upper pane, right-click an instance, select CloudWatch Monitoring, and then click Add/Edit Alarms.

    Or, select the instance and then in the lower pane, on the Monitoring tab, click Create Alarm.

  5. In the Alarm Details for dialog box, click Create Alarm.

  6. If you want to receive an email when the alarm is triggered, in the Create Alarm for dialog box, in the Send a notification to box, select an existing Amazon SNS topic, or click Create Topic to create a new one.

    If you create a new topic, in the Send a notification to box type a name for the topic, and then in the With these recipients box, type the email addresses of the recipients (separated by commas). Later, after you create the alarm, you will receive a subscription confirmation email that you must accept before you will get email for this topic.

  7. Select the Take the action check box, and then choose the Reboot this instance radio button.

  8. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  9. In the Whenever box, choose Status Check Failed (Instance).

  10. In the For at least field, enter 3.

  11. In the consecutive period(s) of box, select 1 minute.

  12. To change the name of the alarm, in the Name of alarm box, type a new name.

    If you don't type a name for the alarm, Amazon CloudWatch will automatically create one for you.

  13. Click Create Alarm.

To create an alarm to reboot an instance using the Amazon CloudWatch console

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, click Alarms.

  4. Click Create Alarm, and then in CloudWatch Metrics by Category, under EC2 Metrics, select Per-Instance Metrics.

  5. In the list of metrics, select the instance and StatusCheckFailed_Instance metric you want to create an alarm for. You can also type an instance ID in the search box to go the instance that you want.

  6. Select Minimum from the Statistic drop-down list.

    Note

    This is the only statistic that is currently supported.

  7. Select a period from the Period drop-down list, for example: 1 Minute.

  8. Click Next, and then under Alarm Threshold, in the Name field, enter a unique name for the alarm, for example: Reboot EC2 instance.

  9. In the Description field, enter a description of the alarm, for example: Reboot EC2 instance when health checks fail.

  10. In the is drop-down list, select >.

  11. In the box next to the is drop-down list, enter 0 and in the for field, enter 3.

    A graphical representation of the threshold is shown under Alarm Preview.

  12. Under Actions, click EC2 Action.

  13. In the Whenever this alarm drop-down list, select State is ALARM.

  14. In the Take this action drop-down list, select Reboot this instance.

  15. Click Notification, and then in the Send notification to drop-down list, select an existing Amazon SNS topic or create a new one.

  16. To create a new Amazon SNS topic, select New list.

    In the Send notification to field, enter a name for the new Amazon SNS topic for example: Reboot_EC2_Instance, and in the Email list field, enter a comma-separated list of email addresses to be notified when the alarm changes to the ALARM state.

    Important

    If you are creating a new topic or adding email addresses to an existing topic, each email address that you add will be sent a topic subscription confirmation email. You must confirm the subscription by clicking the included link before notifications will be sent to a new email address.

  17. In the navigation pane, click Create Alarm to complete the alarm creation process.

Adding Recover Actions to Amazon CloudWatch Alarms

You can create an Amazon CloudWatch alarm that monitors an Amazon EC2 instance and automatically recovers the instance if it becomes impaired due to an underlying hardware failure or a problem that requires AWS involvement to repair. Terminated instances cannot be recovered. A recovered instance is identical to the original instance, including the instance ID, private IP addresses, Elastic IP addresses, and all instance metadata.

When the StatusCheckFailed_System alarm is triggered, and the recover action is initiated, you will be notified by the Amazon SNS topic that you selected when you created the alarm and associated the recover action. During instance recovery, the instance is migrated during an instance reboot, and any data that is in-memory is lost. When the process is complete, information is published to the SNS topic you've configured for the alarm. Anyone who is subscribed to this SNS topic will receive an email notification that includes the status of the recovery attempt and any further instructions. You will notice an instance reboot on the recovered instance.

Examples of problems that cause system status checks to fail include:

  • Loss of network connectivity

  • Loss of system power

  • Software issues on the physical host

  • Hardware issues on the physical host

The recover action is only supported on:

  • The C3, C4, M3, M4, R3, T2, and X1 instance types

  • Instances in a VPC

  • Instances with shared tenancy (the tenancy attribute is set to default)

  • Instances that use Amazon EBS storage exclusively

If your instance has a public IP address, it will retain the same public IP address after recovery.

Important

To avoid a race condition between the reboot and recover actions, we recommend that you set the alarm threshold to 2 for 1 minute when creating alarms that recover an Amazon EC2 instance.

To create an alarm to recover an instance using the Amazon EC2 console

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, under INSTANCES, click Instances.

  4. In the upper pane, right-click an instance, select CloudWatch Monitoring, and then click Add/Edit Alarms.

    Or, select the instance and then in the lower pane, on the Monitoring tab, click Create Alarm.

  5. In the Alarm Details for dialog box, click Create Alarm.

  6. If you want to receive an email when the alarm is triggered, in the Create Alarm for dialog box, in the Send a notification to box, select an existing Amazon SNS topic, or click Create Topic to create a new one.

    If you create a new topic, in the Send a notification to box type a name for the topic, and then in the With these recipients box, type the email addresses of the recipients (separated by commas). Later, after you create the alarm, you will receive a subscription confirmation email that you must accept before you will get email for this topic.

  7. Select the Take the action check box, and then choose the Recover this instance radio button.

  8. If prompted, select the Create IAM role: EC2ActionsAccess check box to automatically create an IAM role so that AWS can automatically stop the instance on your behalf when the alarm is triggered.

  9. In the Whenever box, choose Status Check Failed (System).

  10. In the For at least field, enter 2.

  11. In the consecutive period(s) of box, select 1 minute.

  12. To change the name of the alarm, in the Name of alarm box, type a new name.

    If you don't type a name for the alarm, Amazon CloudWatch will automatically create one for you.

  13. Click Create Alarm.

To create an alarm to recover an instance using the Amazon CloudWatch console

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, click Alarms.

  4. Click Create Alarm, and then in CloudWatch Metrics by Category, under EC2 Metrics, select Per-Instance Metrics.

  5. In the list of metrics, select the instance and StatusCheckFailed_System metric you want to create an alarm for. You can also type an instance ID in the search box to go the instance that you want.

  6. Select Minimum from the Statistic drop-down list.

    Note

    This is the only statistic that is currently supported.

  7. Select a period from the Period drop-down list, for example: 1 Minute.

  8. Click Next, and then under Alarm Threshold, in the Name field, enter a unique name for the alarm, for example: Recover EC2 instance.

  9. In the Description field, enter a description of the alarm, for example: Recover EC2 instance when health checks fail.

  10. In the is drop-down list, select >.

  11. In the box next to the is drop-down list, enter 0 and in the for field, enter 2.

    A graphical representation of the threshold is shown under Alarm Preview.

  12. Under Actions, click EC2 Action.

  13. In the Whenever this alarm drop-down list, select State is ALARM.

  14. In the Take this action drop-down list, select Recover this instance.

  15. Click Notification, and then in the Send notification to drop-down list, select an existing Amazon SNS topic or create a new one.

  16. To create a new Amazon SNS topic, select New list.

    In the Send notification to field, enter a name for the new Amazon SNS topic for example: Recover_EC2_Instance, and in the Email list field, enter a comma-separated list of email addresses to be notified when the alarm changes to the ALARM state.

    Important

    If you are creating a new topic or adding email addresses to an existing topic, each email address that you add will be sent a topic subscription confirmation email. You must confirm the subscription by clicking the included link before notifications will be sent to a new email address.

  17. In the navigation pane, click Create Alarm to complete the alarm creation process.

Using the Amazon CloudWatch Console to View the History of Triggered Alarms and Actions

You can view alarm and action history in the Amazon CloudWatch console. Amazon CloudWatch keeps the last two weeks’ worth of alarm and action history.

To view the history of triggered alarms and actions

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. If necessary, change the region. From the navigation bar, select the region where your instance is running. For more information, see Regions and Endpoints.

  3. In the navigation pane, click Alarms.

  4. In the upper pane, select the alarm with the history that you want to view.

  5. In the lower pane, the Details tab shows the most recent state transition along with the time and metric values.

  6. Click the History tab to view the most recent history entries.

Amazon CloudWatch Alarm Action Scenarios

You can use the Amazon Elastic Compute Cloud (Amazon EC2) console to create alarm actions that stop or terminate an Amazon EC2 instance when certain conditions are met. In the following screen capture of the console page where you set the alarm actions, we’ve numbered the settings. We’ve also numbered the settings in the scenarios that follow, to help you create the appropriate actions.

Create Alarm for dialog box

Scenario 1: Stop Idle Development and Test Instances

Create an alarm that stops an instance used for software development or testing when it has been idle for at least an hour.

SettingValue

Stop

Maximum

CPUUtilization

<=

10%

60 minutes

1

Scenario 2: Stop Idle Instances

Create an alarm that stops an instance and sends an email when the instance has been idle for 24 hours.

SettingValue

Stop and email

Average

CPUUtilization

<=

5%

60 minutes

24

Scenario 3: Send Email About Web Servers with Unusually High Traffic

Create an alarm that sends email when an instance exceeds 10 GB of outbound network traffic per day.

SettingValue

Email

Sum

NetworkOut

>

10 GB

1 day

1

Scenario 4: Stop Web Servers with Unusually High Traffic

Create an alarm that stops an instance and send a text message (SMS) if outbound traffic exceeds 1 GB per hour.

SettingValue

Stop and send SMS

Sum

NetworkOut

>

1 GB

1 hour

1

Scenario 5: Stop an Instance Experiencing a Memory Leak

Create an alarm that stops an instance when memory utilization reaches or exceeds 90%, so that application logs can be retrieved for troubleshooting.

Note

The MemoryUtilization metric is a custom metric. In order to use the MemoryUtilization metric, you must install the Monitoring Memory and Disk Metrics for Amazon EC2 Linux Instances.

SettingValue

Stop

Maximum

MemoryUtilization

>=

90%

1 minute

1

Scenario 6: Stop an Impaired Instance

Create an alarm that stops an instance that fails three consecutive status checks (performed at 5-minute intervals).

SettingValue

Stop

Average

StatusCheckFailed_System

>=

1

15 minutes

1

Scenario 7: Terminate Instances When Batch Processing Jobs Are Complete

Create an alarm that terminates an instance that runs batch jobs when it is no longer sending results data.

SettingValue

Terminate

Maximum

NetworkOut

<=

100,000 bytes

5 minutes

1

Scenarios Using the Amazon CloudWatch Console

The previous scenarios can also be performed using the Amazon CloudWatch console. We’ve numbered the settings on the console to match the numbered settings in the Amazon EC2 console and the scenarios that we covered earlier, so you can make a comparison and create an alarm with the appropriate actions.

Alarm actions in the CloudWatch console