A SysOps administrator is reviewing the AWS Trusted Advisor dashboard and notices a warning under the Cost Optimization category showing several unassociated Elastic IP addresses that are incurring hourly charges. The administrator needs to eliminate these charges immediately.
Which action should the SysOps administrator take to resolve this issue?
- Release the unassociated Elastic IP addresses using the Amazon EC2 console or the AWS CLI.Answer
- BEnable detailed monitoring on the Elastic IP addresses to track network activity and automatically stop billing charges.
- CCreate a static budget alert in AWS Budgets to automatically release any Elastic IP address that remains unassociated for more than 24 hours.
- DConfigure a CloudWatch Logs metric filter to monitor the connection logs of the Elastic IP addresses and set a retention period of 30 days to save costs.
Answer
Release the unassociated Elastic IP addresses using the Amazon EC2 console or the AWS CLI.
Releasing the unassociated Elastic IP addresses returns them to the AWS public IP pool and immediately stops the hourly charges associated with allocating but not using them. In AWS, you are not charged for Elastic IP addresses as long as they are associated with a running EC2 instance or an active Elastic Network Interface (ENI). However, if they are unassociated, AWS charges an hourly fee to prevent IP address hoarding.
Step-by-Step Solution
Key Concept
Releasing unassociated Elastic IP addresses to stop hourly allocation charges.
Estimated Time:1m 0s