A company is tracking cloud spend by department and wants to monitor who is creating resources. A cloud engineer tags all Amazon EC2 instances and Amazon S3 buckets with a user-defined tag key of Department, and wants to use the AWS-generated tag key aws:createdBy. After one week, the finance team reports that neither tag key is appearing as a filter option in AWS Cost Explorer. Which of the following actions are required to resolve this issue and ensure department-specific costs are tracked going forward? (Select TWO.)
- Activate both the user-defined Department tag and the AWS-generated aws:createdBy tag in the Billing and Cost Management console.Cevap
- Acknowledge that cost allocation tags do not apply retroactively, meaning that cost data categorized by these tags will only appear from the time of activation forward.Cevap
- CApply an IAM policy to all IAM users that grants permission to publish tag values directly to AWS Cost Explorer.
- DCreate an AWS Resource Group containing the tagged resources to automatically force tag data sync with historical billing logs.
- EEnable resource indexing in AWS Resource Explorer for the region containing the S3 buckets and EC2 instances to expose the tags in billing.
Cevap
To resolve the issue, both the Department tag and the aws:createdBy tag must be activated in the Billing and Cost Management console, and the team must understand that cost allocation tags are not retroactive.
To use tags for cost allocation tracking, they must be explicitly activated in the Billing and Cost Management console. This applies to both user-defined tags (like Department) and AWS-generated tags (like aws:createdBy). Furthermore, cost allocation tags do not apply retroactively; billing data will only show these tagged resources from the activation date onward.
Adım Adım Çözüm
Anahtar Kavram
Cost allocation tags require manual activation in the AWS Billing and Cost Management console to appear on billing reports and do not apply retroactively.