A company has AWS accounts that are in an organization in AWS Organizations. The company wants to track Amazon EC2 usage as a metric. The company’s architecture team must receive a daily alert if the EC2 usage is more than 10% higher the average EC2 usage from the last 30 days.
Which solution will meet these requirements?
To meet the requirement of tracking Amazon EC2 usage and receiving a daily alert if usage exceeds the average from the last 30 days by more than 10%, the best solution would be to configure AWS Budgets. AWS Budgets allows for detailed tracking and alerting based on both cost and usage metrics, including specific usage types like EC2 running hours. By specifying the usage type and setting the budget amount based on the average usage from the last 30 days, one can set an alert to notify the architecture team when the usage exceeds the defined threshold. Other options, such as AWS Cost Anomaly Detection, are more focused on cost anomalies rather than specific usage metrics. Therefore, AWS Budgets is the appropriate tool for this scenario.
Answer A. C cannot be correct because Cost Anomaly detection is for a surprise cost exceeds. A is a perfect use case for this scenario.
"A" describe perfectly the process to create this kind of control. Besides Cost Anomaly is very focused on "Cost", while the question ask to control the "usage" (ex:hours), not exactly $ cost. I suggest doing a demo. "A" for sure
Option A - Maybe I am the problem here, I don't why people are selecting option "B", when the the first line in AWS Cost Management documentation Under AWS Budget states - "You can use AWS Budgets to track and take action on your AWS costs and usage. You can use AWS Budgets to monitor your aggregate utilization and coverage metrics for your Reserved Instances (RIs) or Savings Plans." https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-managing-costs.html AWS Blog - https://aws.amazon.com/blogs/mt/manage-cost-overruns-part-1/
Option A - Cost Anomaly detection does not allow to filter based on EC2 type only.
I recommend doing a demo. For sure it is A. It describe perfectly the process.
steps to set up an AWS Budget to track EC2 usage and receive an alert if it's more than 10% higher than the average usage from the last 30 days: Go to the AWS Management Console |Open the "Budgets" service |Create a New Budget:|Choose "Cost budget" as the budget type.|Choose the time period for the budget (e.g., Monthly).|Set the start and end dates for the budget. Configure Cost and Usage Details:|Choose the "Cost and usage" option.|Specify the "Service" as "Amazon EC2" to focus on EC2 costs.|Choose the "Usage type" as "Usage Quantity."|Set Budgeted Amount:|Set the budgeted amount to be 110% of the average EC2 usage from the last 30 days. Configure Alerts:|Enable the alert threshold.|Set the alert threshold to be "Actual > Forecasted" and "More than 0%" to be alerted when the actual usage exceeds the forecast.
Answer: A https://aws.amazon.com/blogs/aws-cloud-financial-management/launch-daily-cost-and-usage-budgets/
B. Configure o AWS Cost Anomaly Detection na conta de gerenciamento da organização. Configure um tipo de monitor de serviço AWS. Aplique um filtro do Amazon EC2. Configure uma assinatura de alerta para notificar a equipe de arquitetura se o uso for 10% maior que o uso médio dos últimos 30 dias.
Option B is incorrect because AWS Cost Anomaly Detection is not designed to track EC2 usage as a metric. It is used to detect anomalies in your AWS costs and usage patterns.
AWS Cost Anomaly Detection for EC2
Option B is incorrect because AWS Cost Anomaly Detection is not designed to track EC2 usage as a metric. It is used to detect anomalies in your AWS costs and usage patterns.
Answer A
This questions is weird. The best soltuion should be AWS CloudWatch. No such answer to choose !
B is the answer, AWS Cost Anomaly Detection is specifically designed to monitor AWS service usage, identify anomalies based on historical patterns, and can be configured to send alerts when the usage exceeds a certain threshold compared to the average of the last 30 days. This aligns well with the requirement to receive daily alerts if EC2 usage is more than 10% higher than the average usage from the past 30 days.
You're right on most, but on this one, it is A.
Answer: B
A, for sure. Service Monitor tracks spend across all deployed services, but not for a specific service (like ec2)
It should be D as AWS Cost Anomaly Detection is a service that monitors your cost and usage data to detect anomalies based on machine learning models. It can identify unusual spending patterns and notify you when anomalies are detected based on historical usage patterns
I mean B
It's B. Cost Anomaly detection _can_ do this kind of thing. AWS Budgets is for overall costs and is a less sharp tool here.
A: Cost dedection is for cost, not for EC2 metrix