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 is designed to track costs and alert users when spending exceeds a set budget, but it does not provide detailed insights or comparisons for EC2 costs based on instance types. It lacks the necessary granularity for in-depth analysis.
Cost Explorer offers granular filtering features that allow users to analyze and visualize EC2 costs effectively based on instance types over specified time frames, making it suitable for identifying the root cause of increased costs with minimal operational overhead.
The AWS Billing and Cost Management dashboard provides basic graphs but does not allow for detailed filtering and comparison of EC2 costs by instance types. It is limited in functionality for in-depth cost analysis over time compared to Cost Explorer.
AWS Cost and Usage Reports can provide detailed billing information, but generating interactive graphs in Amazon QuickSight involves more operational overhead due to the need to set up and manage an S3 bucket and QuickSight integration. This approach is more complex than necessary for the task at hand.
I scheme that the answer is:
Use Cost Explorer’s granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.