A retail company is launching a seasonal marketing campaign and has deployed several AWS resources, including Amazon EC2 instances and Amazon S3 buckets. To organize their billing reports, they applied a user-defined tag with the key CampaignID to all resources, and they want to use the AWS-generated aws:createdBy tag to track resource creators. However, they notice that neither tag key is available for filtering or grouping in AWS Cost Explorer. Which of the following actions must the company take to resolve this issue and track their campaign costs? (Select TWO.)
- Activate both the CampaignID tag and the aws:createdBy tag in the Billing and Cost Management console.Answer
- Allow new billing data to generate, as cost allocation tags only apply to cost data from the time of activation forward.Answer
- CConfigure an IAM policy that grants the AWS Billing service permissions to read tags from the resources.
- DCreate a resource query in AWS Resource Explorer to index the tags globally across all AWS Regions.
- EUse AWS Resource Groups to group the tagged resources, which automatically publishes the tags to the AWS Billing dashboard.
Answer
To resolve the issue, the company must activate both the CampaignID tag and the aws:createdBy tag in the Billing and Cost Management console, and allow new billing data to generate, as tags do not apply retroactively.
Cost allocation tags must be activated in the Billing and Cost Management console before they can be used for grouping and filtering in AWS Cost Explorer or appearing on billing reports. Additionally, cost allocation tags are not retroactive; they only track costs from the point of activation onward.
Step-by-Step Solution
Key Concept
Activation and temporal rules of user-defined and AWS-generated cost allocation tags.
Estimated Time:1m 30s