A company wants to identify specific Amazon EC2 instances that are underutilized and the estimated cost savings for each instance. How can this be done with MINIMAL effort?
A.
Use AWS Budgets to report on low utilization of EC2 instances.
B.
Run an AWS Systems Manager script to check for low memory utilization of EC2 instances.
C.
Run Cost Explorer to look for low utilization of EC2 instances.
D.
Use Amazon CloudWatch metrics to identify EC2 instances with low utilization.
The best way to identify underutilized Amazon EC2 instances and estimate cost savings with minimal effort is to use AWS Cost Explorer (Option C).
AWS Cost Explorer includes an EC2 Right Sizing report that identifies underutilized instances and provides recommendations for downsizing, based on CPU and memory utilization metrics over a specific period of time. This report also provides estimated cost savings for each instance.
While AWS Budgets (Option A), AWS Systems Manager (Option B), and Amazon CloudWatch (Option D) can provide useful information about your AWS resources, they do not directly provide the functionality to identify underutilized EC2 instances and the estimated cost savings for each instance. AWS Budgets is used for creating custom cost and usage budgets, AWS Systems Manager is used for managing and viewing operational data, and Amazon CloudWatch is used for monitoring and observability. None of these services provide the specific functionality described in the question with minimal effort.
So, the correct answer is C. Run Cost Explorer to look for low utilization of EC2 instances.
In summary, while AWS Cost Explorer is valuable for understanding cost trends and patterns, it is not the ideal choice for identifying underutilized EC2 instances and estimating cost savings. Amazon CloudWatch provides real-time and granular metrics that are better suited for this purpose, making option D the more appropriate and efficient option.
D
Enhancing your recommendations using CloudWatch metrics
We can examine your memory utilization if you enable your Amazon CloudWatch agent.
To identify all instances for all accounts in the consolidated billing family, rightsizing recommendations look at the usage for the last 14 days for each account. If the instance was stopped or terminated, we remove it from consideration. For all remaining instances, we call CloudWatch to get maximum CPU utilization data for the last 14 days. This is to produce conservative recommendations, not to recommend instance modifications that could be detrimental to application performance or that could unexpectedly impact your performance.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
MrDEVOPS
Highly Voted 3 years, 1 month agoe45af42
Most Recent 4 months, 3 weeks agoalbert_kuo
1 year, 3 months agoalbert_kuo
12 months agoaidenpearce01
2 years, 7 months agokr12
2 years, 10 months agoCyril_the_Squirl
2 years, 12 months agoalexsandroe
2 years, 12 months agoRicardoD
3 years agoabhishek_m_86
3 years agojackdryan
3 years agoweril
3 years agotifoz
3 years agovramchn
3 years agovramchn
3 years agomrbreeze
3 years ago