Which solution will meet these requirements?
Turn on billing alerts. Use AWS Cost Explorer to determine the costs for the past month. Create an Amazon CloudWatch alarm for total estimated charges. Specify a cost threshold that is higher than the costs that Cost Explorer determined. Add a notification to alert the operations team if the alarm threshold is breached.
Turn on billing alerts. Use AWS Cost Explorer to determine the average monthly costs for the past 3 months. Create an Amazon CloudWatch alarm for total estimated charges. Specify a cost threshold that is higher than the costs that Cost Explorer determined. Add a notification to alert the operations team if the alarm threshold is breached.
Use AWS Cost Anomaly Detection to create a cost monitor that has a monitor type of Linked account. Create a subscription to send daily AWS cost summaries to the operations team. Specify a threshold for cost variance.
Use AWS Cost Anomaly Detection to create a cost monitor that has a monitor type of AWS services. Create a subscription to send daily AWS cost summaries to the operations team. Specify a threshold for cost variance.
Explanations:
Billing alerts and CloudWatch alarms are useful, but they are based on total charges, not identifying specific unused resources. AWS Cost Explorer is useful for analysis but does not automate resource identification.
Similar to Option A, this option uses billing alerts and CloudWatch, but it only helps track costs without focusing on specific unused resources. AWS Cost Explorer provides cost analysis but no automated notifications for unused resources.
AWS Cost Anomaly Detection can help detect unexpected cost spikes, but it monitors linked accounts rather than specific resources. It won’t directly help identify unused resources causing cost increases.
AWS Cost Anomaly Detection monitors AWS service-level cost fluctuations and can be used to detect unexpected cost increases caused by unused resources. This solution automatically sends notifications and helps identify cost anomalies efficiently.
In my opinion, the answer is:
Use AWS Cost Anomaly Detection to create a cost monitor that has a monitor type of AWS services. Create a subscription to send daily AWS cost summaries to the operations team. Specify a threshold for cost variance.