A financial company is auditing its cloud expenditures across several member accounts within an AWS Organization. To track costs associated with a new data analysis project, a SysOps Administrator has written a Python script using AWS Systems Manager to apply a tag with the key `ProjectAnalysis` and value `DataLake` to all active Amazon EBS volumes. However, when the administrator logs into AWS Cost Explorer in the management account, the `ProjectAnalysis` tag is not available as a filtering option. Which action should the SysOps Administrator take to ensure the tag can be used to filter costs?
- Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.Answer
- BLog into each member account individually, access the AWS Billing and Cost Management console, and activate the `ProjectAnalysis` tag within each account.
- CCreate an AWS Organizations Tag Policy with compliance rules for the `ProjectAnalysis` key, which automatically registers the tag for cost allocation.
- DModify the Python script to include the `aws:TagKeys` condition inside an IAM Service Control Policy (SCP) to force automatic activation of the tag.
Answer
Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.
The correct answer is to access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate. In AWS Organizations with consolidated billing, user-defined cost allocation tags must be centrally activated by the management (payer) account. Once activated, AWS begins to track costs associated with these tags, allowing them to appear as filters in AWS Cost Explorer.
Step-by-Step Solution
Key Concept
Activation of Cost Allocation Tags in AWS Organizations