Which solution will meet these requirements?
Create an AWS Cost and Usage Report for the organization. Define tags and cost categories in the report. Create a table in Amazon Athena. Create an Amazon QuickSight dataset based on the Athena table. Share the dataset with the finance team.
Create an AWS Cost and Usage Report for the organization. Define tags and cost categories in the report. Create a specialized template in AWS Cost Explorer that the finance department will use to build reports.
Create an Amazon QuickSight dataset that receives spending information from the AWS Price List Query API. Share the dataset with the finance team.
Use the AWS Price List Query API to collect account spending information. Create a specialized template in AWS Cost Explorer that the finance department will use to build reports.
Explanations:
This option involves creating an AWS Cost and Usage Report (CUR) for the entire organization, which aggregates the billing data. By defining tags and cost categories, the report can categorize costs meaningfully for the finance team. Using Amazon Athena to query the data allows for complex reporting, and Amazon QuickSight provides a way to visualize and share the data effectively. This approach meets the requirement for a self-managed solution that provides meaningful cost reporting.
While creating an AWS Cost and Usage Report and defining tags and cost categories is correct, this option suggests using AWS Cost Explorer to build reports. Cost Explorer is primarily a tool for exploring and visualizing costs but does not provide the level of customization and detail available through Athena and QuickSight for comprehensive reporting. Therefore, it does not fully meet the needs for a self-managed application.
This option suggests using the AWS Price List Query API to collect spending information and creating a QuickSight dataset. However, the Price List Query API provides pricing information rather than actual cost data incurred by the AWS accounts. Without the cost data from the Cost and Usage Report, the finance team would not have a meaningful basis for reporting, making this option inadequate for their needs.
This option also uses the AWS Price List Query API to collect account spending information, which does not provide actual cost data. While creating a template in AWS Cost Explorer is valid, it does not utilize a comprehensive reporting method like the Cost and Usage Report combined with Athena and QuickSight, which are necessary for generating detailed and meaningful cost reports for the finance team.
I opine that the answer is:
Create an AWS Cost and Usage Report for the organization. Define tags and cost categories in the report. Create a table in Amazon Athena. Create an Amazon QuickSight dataset based on the Athena table. Share the dataset with the finance team.