An organization's AWS Trusted Advisor Cost Optimization report lists several Amazon Elastic Block Store (Amazon EBS) volumes in the 'available' state with a warning status, indicating they are underutilized. A SysOps administrator is tasked with optimizing costs by removing these volumes while ensuring that any existing data can be recovered if needed in the future.
Which action should the administrator take to meet these requirements?
- AApply a cost allocation tag to the available EBS volumes and activate it in the Billing Console, which will automatically stop the hourly charges for the volumes while they remain unattached.
- Create a snapshot of each available EBS volume for potential future recovery, and then delete the volumes.Cevap
- CEnable detailed CloudWatch monitoring on the EC2 instances associated with these volumes to verify if their combined network throughput is zero before deleting the volumes.
- DConfigure an Amazon CloudWatch Logs retention policy to archive the volume metrics to Amazon S3 Glacier, which automatically deletes the underlying EBS volumes after 30 days of inactivity.
Cevap
Create a snapshot of each available EBS volume for potential future recovery, and then delete the volumes.
The correct action is to create a snapshot of each available EBS volume and then delete the volumes. EBS volumes in the 'available' state are detached from EC2 instances but continue to incur charges. Creating a snapshot preserves the data at a lower cost, and deleting the volumes eliminates the ongoing active volume charges.
Adım Adım Çözüm
Anahtar Kavram
Safely cleaning up underutilized Amazon EBS volumes by creating snapshots for data retention before deleting the unattached volumes.