A SysOps administrator is reviewing AWS Trusted Advisor cost optimization reports and identifies several underutilized resources, including stopped Amazon Elastic Block Store (Amazon EBS) volumes and unassociated Elastic IP addresses. The administrator wants to reduce account costs by cleaning up these resources without impacting active workloads.
Which of the following actions should the administrator take? (Select TWO.)
- Delete the unassociated Elastic IP addresses to stop incurring hourly charges for unused public IPv4 addresses.Answer
- Create Amazon EBS snapshots of the stopped EBS volumes for backup, and then delete the idle volumes to stop paying for volume storage.Answer
- CEnable detailed monitoring on all running EC2 instances to automatically terminate any instance whose CPU utilization falls below .
- DSet the retention period of all CloudWatch log groups to Never Expire to ensure metric logs for underutilized resources are retained indefinitely.
- EApply tags to the underutilized resources, as tags will automatically delete the resources once they reach a configured age.
Answer
The correct actions are to delete the unassociated Elastic IP addresses and to create Amazon EBS snapshots of the stopped EBS volumes before deleting the volumes.
Deleting unassociated Elastic IP addresses stops the hourly charges AWS applies to unused public IPv4 allocations. Creating EBS snapshots of stopped EBS volumes preserves their data cost-effectively in Amazon S3 before the active volumes are deleted, which eliminates active EBS storage charges.
Step-by-Step Solution
Key Concept
Cleaning up idle and underutilized resources, specifically unassociated Elastic IPs and stopped EBS volumes, is a primary AWS cost optimization practice.