A company uses AWS Organizations to run workloads within multiple AWS accounts A tagging policy adds department tags to AWS resources when the company creates tags.
An accounting team needs to determine spending on Amazon EC2 consumption The accounting team must determine which departments are responsible for the costs regardless of AWS account The accounting team has access to AWS Cost Explorer for all AWS accounts within the organization and needs to access all reports from Cost Explorer.
Which solution meets these requirements in the MOST operationally efficient way'?
This solution meets the following requirements:
It is operationally efficient, as it only requires one activation of the cost allocation tag and one creation of the cost report from the management account, which has access to all the member accounts' data and billing pReference.
It is consistent, as it uses the AWS-defined cost allocation tag named department, which is automatically applied to resources when the company creates tags using the tagging policy enforced by AWS Organizations. This ensures that the tag name and value are the same across all the resources and accounts, and avoids any discrepancies or errors that might arise from user-defined tags.
It is informative, as it creates one cost report in Cost Explorer grouping by the tag name, and filters by EC2. This allows the accounting team to see the breakdown of EC2 consumption and costs by department, regardless of the AWS account. The team can also use other features of Cost Explorer, such as charts, filters, and forecasts, to analyze and optimize the spending.
Using AWS cost allocation tags - AWS Billing
Marjory
6 months agoQuentin
6 months agoLennie
6 months agoMarjory
6 months agoLennie
6 months agoMarjory
7 months agoHelene
8 months agoMattie
8 months agoLamonica
8 months agoIesha
7 months agoJulian
7 months agoHollis
8 months agoLucina
8 months agoJovita
8 months agoLindsey
8 months agoFelicia
8 months agoHershel
8 months ago