Which steps should the SysOps Administrator take to prevent this from happening in the future?
Configure Amazon CloudWatch Events to filter and forward AWS Health events for disk space utilization to an Amazon SNS topic to notify the Administrator.
Create an AWS Lambda function to describe the volume status for each EC2 instance. Post a notification to an Amazon SNS topic when a volume status is impaired.
Enable detailed monitoring for the EC2 instances. Create an Amazon CloudWatch alarm to notify the Administrator when disk space is running low.
Use the Amazon CloudWatch agent on the EC2 instances to collect disk metrics. Create a CloudWatch alarm to notify the Administrator when disk space is running low.
Explanations:
CloudWatch Events for AWS Health events are not designed to monitor disk space utilization on EC2 instances. AWS Health events provide information on service issues, not specific EC2 resource metrics like disk space.
This solution does not directly monitor disk space usage. Describing volume status will only alert for impaired status (e.g., hardware failure), not for when disk space is low, which is the issue in this case.
Enabling detailed monitoring for EC2 instances provides additional metrics but does not directly address disk space monitoring. CloudWatch alarms can help with CPU, memory, and network metrics, but not specifically with disk space unless the CloudWatch agent is used.
The Amazon CloudWatch agent can be installed on EC2 instances to collect detailed disk metrics. Creating a CloudWatch alarm based on these metrics allows the Administrator to be notified when disk space is running low, directly addressing the issue of a full disk.
I strategize that the answer is:
Use the Amazon CloudWatch agent on the EC2 instances to collect disk metrics. Create a CloudWatch alarm to notify the Administrator when disk space is running low.