How should the solutions architect generate the information with the LEAST operational overhead?
Use AWS Budgets to create a budget report and compare EC2 costs based on instance types.
Use Cost Explorer’s granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.
Use graphs from the AWS Billing and Cost Management dashboard to compare EC2 costs based on instance types for the last 2 months.
Use AWS Cost and Usage Reports to create a report and send it to an Amazon S3 bucket. Use Amazon QuickSight with Amazon S3 as a source to generate an interactive graph based on instance types.
Explanations:
AWS Budgets are primarily for tracking spending against predefined budgets but do not provide detailed analysis of costs based on instance types.
Cost Explorer offers granular filtering options that allow detailed analysis of EC2 costs by instance types, making it the most effective tool for identifying root causes with minimal overhead.
The AWS Billing and Cost Management dashboard provides general cost information but lacks the detailed filtering needed for an in-depth analysis of EC2 costs by instance types.
While AWS Cost and Usage Reports can provide detailed data, setting up Amazon QuickSight involves more operational overhead compared to using Cost Explorer directly.
If memory serves me right, the answer is:
Use Cost Explorer’s granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.
I think the answer is:
Use Cost Explorer’s granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.