You just join a company as a DevOps engineer and you need to manage an AWS account. A big number of AWS resources are deployed in the account such as Auto Scaling groups, S3 buckets, etc. In order to better understand the cost spent in the account, every department starts to attach a user-defined tag CostCenter:xxxx to its AWS resources. You also configured the AWS Cost and Usage Reports and used an S3 bucket to save the reports. After several days, you check the reports in the S3 bucket and find that the reports do not use the CostCenter tag to organize the resources or track the AWS costs. Which of the following steps do you miss?

Answer options:

A.Activate the CostCenter tag in the Billing and Cost Management console then the usage and costs will be grouped by the tag.
B.Modify the S3 bucket policy to allow the AWS Cost Allocation Tags service to write objects in the S3 bucket.
C.AWS Cost and Usage Reports only support AWS-Generated Cost Allocation Tags. User-defined tags are not supported.
D.User-defined tags have specific formats in AWS Cost and Usage Reports. The tag keys must have a prefix of “aws:” otherwise the tags are not applied in the reports.

Correct Answer – A
In order to enable the user-defined cost allocation tags, you need to activate the tags first. Details can be found in https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html.
Option A is CORRECT: Because you need to activate the tags in the Billing and Cost Management console for the cost allocation tracking.
Option B is incorrect: The reports have already been put in the S3 bucket successfully, which means there is no problem for the S3 bucket policy permissions.
Option C is incorrect: Because both AWS-Generated Cost Allocation tags and user-defined tags are supported by the AWS Cost and Usage Reports.
Option D is incorrect: Because there is no such requirement to append the “aws:” prefix to the user-defined cost allocation tags.