Which solution will meet these requirements?
In the organization’s management account, create a cost allocation tag that is named BusinessUnit. Also in the management account, create an Amazon S3 bucket and an AWS Cost and Usage Report (AWS CUR). Configure the S3 bucket as the destination for the AWS CUR. From the management account, query the AWS CUR data by using Amazon Athena. Use Amazon QuickSight for visualization.
In each member account, create a cost allocation tag that is named BusinessUnit. In the organization’s management account, create an Amazon S3 bucket and an AWS Cost and Usage Report (AWS CUR). Configure the S3 bucket as the destination for the AWS CUR. Create an Amazon CloudWatch dashboard for visualization.
In the organization’s management account, create a cost allocation tag that is named BusinessUnit. In each member account, create an Amazon S3 bucket and an AWS Cost and Usage Report (AWS CUR). Configure each S3 bucket as the destination for its respective AWS CUR. In the management account, create an Amazon CloudWatch dashboard for visualization.
In each member account, create a cost allocation tag that is named BusinessUnit. Also in each member account, create an Amazon S3 bucket and an AWS Cost and Usage Report (AWS CUR). Configure each S3 bucket as the destination for its respective AWS CUR. From the management account, query the AWS CUR data by using Amazon Athena. Use Amazon QuickSight for visualization.
Explanations:
In the organization’s management account, creating a cost allocation tag named BusinessUnit allows for proper tagging of resources across accounts. The AWS Cost and Usage Report (CUR) can be directed to an S3 bucket in the management account, and querying this data using Amazon Athena enables cost analysis per business unit. Finally, using Amazon QuickSight provides robust visualization capabilities. This setup meets the requirements for allocating and visualizing cloud costs effectively.
Creating a cost allocation tag in each member account does not help centralize cost tracking effectively; cost allocation tags should be managed in the management account for uniformity. While an S3 bucket and AWS CUR can be set up, using an Amazon CloudWatch dashboard does not provide the same level of visualization capabilities as QuickSight, which is necessary for detailed analysis and reporting.
While creating a cost allocation tag in the management account is a good step, creating individual S3 buckets in each member account for AWS CUR data complicates the aggregation of costs and does not provide a streamlined method for visualizing data across business units. Additionally, the use of CloudWatch for visualization lacks the depth needed for effective cost analysis.
Similar to option B, creating cost allocation tags in each member account undermines centralized management of tags. The separate S3 buckets for each member account also complicate data aggregation. Although using Athena for querying is beneficial, visualizing with QuickSight is not implemented here, which limits the ability to effectively analyze costs per business unit.
Based on what I know, the answer is:
In the organization’s management account, create a cost allocation tag that is named BusinessUnit. Also in the management account, create an Amazon S3 bucket and an AWS Cost and Usage Report (AWS CUR). Configure the S3 bucket as the destination for the AWS CUR. From the management account, query the AWS CUR data by using Amazon Athena. Use Amazon QuickSight for visualization.