A SysOps Administrator in a multi-account organization wants to organize monthly AWS spending by project using the tag key `ProjectName`. The administrator has successfully applied this tag to all Amazon EC2 instances within the member accounts. However, when generating a monthly cost report in AWS Cost Explorer from the management account, the administrator cannot find `ProjectName` in the tag filtering options. Which action must the administrator take to ensure the `ProjectName` tag is available in Cost Explorer?
- Activate the `ProjectName` tag as a cost allocation tag in the AWS Billing and Cost Management console of the management account.Answer
- BWait for the monthly billing cycle to complete, as user-defined tags are automatically activated and processed only at the end of each billing period.
- CEnable detailed monitoring on all EC2 instances to allow the Cost Explorer API to retrieve metadata tags.
- DAttach an IAM policy to the member accounts allowing the `aws:RequestTag` permission for the EC2 instances.
Answer
Activate the `ProjectName` tag as a cost allocation tag in the AWS Billing and Cost Management console of the management account.
The correct action is to activate the `ProjectName` tag as a cost allocation tag in the AWS Billing and Cost Management console of the management account. Applying a tag to resources only creates the metadata on the resource; to use it for tracking costs and filtering in AWS Cost Explorer, it must be explicitly activated. In an AWS Organizations setup, cost allocation tags must be activated from the management account.
Step-by-Step Solution
Key Concept
Activation of User-Defined Cost Allocation Tags
Estimated Time:50s