A company runs large-scale, ad-hoc data processing jobs using Amazon EMR. The run schedule and scale of these jobs vary greatly based on client data delivery, leading to highly variable but legitimate compute costs. A SysOps administrator needs to implement a solution that detects unexpected cost spikes due to configuration errors or orphaned resources, while minimizing false alarms caused by the variable EMR workloads. Which solution meets these requirements with the least operational overhead?
- AConfigure an AWS Budget with a daily cost limit set to the average historical spend of the EMR clusters, and set up an Amazon SNS notification when costs exceed 110% of the threshold.
- BEnable detailed monitoring in CloudWatch for the EMR cluster instances, and create an Amazon EventBridge rule that triggers an AWS Systems Manager Automation runbook to terminate instances when billing metrics spike.
- Create an AWS Cost Anomaly Detection monitor using the AWS services monitor type, and create an alert subscription with an alerting threshold to notify the administrator of anomalies.Cevap
- DEnable cost allocation tags for EMR clusters in the Billing console, and schedule a daily Cost Explorer report to be sent to the administrator to manually review untagged resource costs.
Cevap
Create an AWS Cost Anomaly Detection monitor using the AWS services monitor type, and create an alert subscription with an alerting threshold to notify the administrator of anomalies.
AWS Cost Anomaly Detection uses machine learning to dynamically baseline and monitor cost patterns for individual AWS services. This approach accommodates the highly variable and ad-hoc nature of workloads like Amazon EMR by adapting to historical spend trends, thereby minimizing false positives and alerting the administrator only when an actual anomaly is detected.
Adım Adım Çözüm
Anahtar Kavram
AWS Cost Anomaly Detection for variable workloads
Tahmini Süre:1m 30s