Which action will ensure that the CloudWatch alarms function correctly?

By:
In: SOA-C02
Tagged:
With: 2 Comments
A SysOps administrator needs to create alerts that are based on the read and write metrics of Amazon Elastic Block Store (Amazon EBS) volumes that are attached to an Amazon EC2 instance.The SysOps administrator creates and enables Amazon CloudWatch alarms for the DiskReadBytes metric and the DiskWriteBytes metric.A custom monitoring tool that is installed on the EC2 instance with the same alarm configuration indicates that the volume metrics have exceeded the threshold.However, the CloudWatch alarms were not in ALARM state.

Which action will ensure that the CloudWatch alarms function correctly?

Install and configure the CloudWatch agent on the EC2 instance to capture the desired metrics.

Install and configure AWS Systems Manager Agent on the EC2 instance to capture the desired metrics.

Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EBS volumes.

Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EC2 instance.

Explanations:

The CloudWatch agent is used to monitor additional metrics on the instance, but the DiskReadBytes and DiskWriteBytes metrics are already provided by CloudWatch for EBS volumes. Installing the CloudWatch agent is not necessary.

The AWS Systems Manager Agent (SSM Agent) does not capture EBS volume-specific metrics like DiskReadBytes and DiskWriteBytes. It is used for managing EC2 instances and running automation tasks, not for capturing EBS metrics.

The correct metrics for EBS volumes are VolumeReadBytes and VolumeWriteBytes. The current alarms are using the wrong metrics (DiskReadBytes and DiskWriteBytes, which are for instance-level metrics). Reconfiguring the alarms to use the EBS-specific metrics will resolve the issue.

The VolumeReadBytes and VolumeWriteBytes metrics are associated with the EBS volumes, not the EC2 instance itself. Configuring alarms for the EC2 instance will not track the desired EBS volume metrics.

2026-04-02

2 Comments

  1. Gerald
    Author

    I gauge that the answer is:
    Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EBS volumes.

  2. Gabriel
    Author

    I arrange that the answer is:
    Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EBS volumes.

Leave a Reply to Gerald Cancel reply

Your email address will not be published. Required fields are marked *

five × 4 =