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 - Cost Anomaly detection does not allow to filter based on EC2 type only.
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/
Answer A
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.
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.
Answer: A https://aws.amazon.com/blogs/aws-cloud-financial-management/launch-daily-cost-and-usage-budgets/
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.
>|Choose "Cost budget" as the budget type. It should be "Usage budget"
In AWS Budget Console: Usage budget Monitor your usage of one or more specified usage types or usage type groups and receive alerts when your user-defined thresholds are met. Using usage budgets, the budgeted amount represents your expected usage. For example, you can use a usage budget to monitor the usage of certain services such as Amazon EC2 and Amazon S3.
In AWS Budget Console: Usage budget Monitor your usage of one or more specified usage types or usage type groups and receive alerts when your user-defined thresholds are met. Using usage budgets, the budgeted amount represents your expected usage. For example, you can use a usage budget to monitor the usage of certain services such as Amazon EC2 and Amazon S3.
In AWS Budget Console: Usage budget Monitor your usage of one or more specified usage types or usage type groups and receive alerts when your user-defined thresholds are met. Using usage budgets, the budgeted amount represents your expected usage. For example, you can use a usage budget to monitor the usage of certain services such as Amazon EC2 and Amazon S3.
>|Choose "Cost budget" as the budget type. It should be "Usage budget"
In AWS Budget Console: Usage budget Monitor your usage of one or more specified usage types or usage type groups and receive alerts when your user-defined thresholds are met. Using usage budgets, the budgeted amount represents your expected usage. For example, you can use a usage budget to monitor the usage of certain services such as Amazon EC2 and Amazon S3.
For those who think the correct answer is B: https://docs.aws.amazon.com/cost-management/latest/userguide/getting-started-ad.html "For Threshold, enter a number to configure the anomalies that you want to generate alerts for. There are two types of thresholds: absolute and percentage. Absolute thresholds trigger alerts when an anomaly's total COST impact exceeds your chosen threshold. Percentage thresholds trigger alerts when an anomaly's total impact percentage exceeds your chosen threshold. Total impact percentage is the percentage difference between the total expected SPEND and total actual SPEND."" AWS COST Anomaly Detection primarily focuses on COST anomalies rather than specific usage metrics.
Answer: B
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.
This questions is weird. The best soltuion should be AWS CloudWatch. No such answer to choose !
It has to be A. I have tried to do it in AWS Budget Console. Here's a step by step breakdown of what I have done: Step 1: Click on the "Create budget" button and choose the "Usage budget" type Step 2: Set the Usage type groups as `EC2 Running hours`, Set budget amount's baseline timerange as `Last 30 days` with a `daily` period Step 3: Configure alerts with 110% of budgeted amount
When setting the time range, even if the label says `Last 30 days`, but if you hover on it, it expands and says `last-30 day average` So really now AWS Budget can help us collect daily average using a 30-day sliding window. You can use this as baseline, and use 110% of baseline value to trigger the alert
I can not reproduce your steps. For usage type group, there are 3 types: fixed/planned/auto-adjusted. both of them are absolute number and don't support percentage setting.
Explanation: AWS Cost Anomaly Detection: This service can monitor your AWS usage and costs, identifying anomalies and deviations from normal usage patterns. By setting up a monitor for Amazon EC2 usage, you can detect if the usage is significantly higher than usual, such as exceeding 10% of the average usage over the past 30 days. Monitor Type: Choosing "AWS Service" as the monitor type allows you to focus specifically on EC2 usage. Alert Subscription: You can configure alerts to notify the architecture team when the detected usage anomaly exceeds the threshold, such as a 10% increase over the historical average.
AWS Budgets can be used to set custom budget based on your expected usage and notify you when a threshold is exceeded. AWS Cost Anomaly Detection uses advanced machine learning (ML) technologies to identify anomalous spend and root causes.
Option B: Configure AWS Cost Anomaly Detection in the organization's management account. Configure a monitor type of AWS Service. Apply a filter of Amazon EC2. Configure an alert subscription to notify the architecture team if the usage is 10% more than the average usage for the last 30 days. 🛠 Explanation: The company needs a solution that: Tracks EC2 usage over time. Calculates the average usage for the past 30 days. Alerts the architecture team if usage exceeds 10% of the average. ✅ AWS Cost Anomaly Detection is designed for this exact purpose. It: Monitors usage and cost metrics at the AWS service level (e.g., EC2). Uses machine learning to detect anomalies based on historical usage. Sends alerts when usage exceeds a defined threshold (in this case, 10% more than the last 30-day average).
A cannot be correct because AWS Budgets requires manual input of the threshold (e.g., 10% above the 30-day average). If the average changes daily, the budget amount would need constant manual updates, making it impractical.
A: Cost dedection is for cost, not for EC2 metrix
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.
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
A, for sure. Service Monitor tracks spend across all deployed services, but not for a specific service (like ec2)
AWS Cost Anomaly Detection is designed to automatically track usage trends and detect anomalies in EC2 usage patterns. You can set up a monitoring rule to compare daily EC2 usage against a 30-day average. If usage exceeds 10% over the historical average, it will trigger an alert. This solution is automated, scalable, and requires minimal operational overhead.