A SysOps Administrator is managing a multi-account AWS environment under a single organization in AWS Organizations. To track department spending, the administrator deploys a Tag Policy at the organization root that enforces the CostCenter tag on all Amazon EC2 instances. Several member accounts deploy new EC2 instances successfully, compliant with the policy. However, when the administrator runs a query in AWS Cost Explorer in the management account grouping by the CostCenter tag, all costs are grouped under the 'No tag key' category. What should the administrator do to ensure the cost data is properly categorized by the tag key in Cost Explorer?
- Log in to the Billing and Cost Management console of the management account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.Cevap
- BLog in to the Billing and Cost Management console of each member account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.
- CModify the Tag Policy at the organization root to set the 'CostAllocation' parameter to true for the CostCenter tag key.
- DCreate an AWS Budgets rule in the management account targeting the CostCenter tag to trigger Cost Explorer to index the resource tags.
Cevap
Log in to the Billing and Cost Management console of the management account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.
The correct answer is to activate the tag in the management account. In AWS Organizations, billing features are consolidated under the management account. Newly created tags do not automatically become active for cost allocation; they must be manually activated in the Billing and Cost Management console of the management account before they appear in Cost Explorer.
Adım Adım Çözüm
Anahtar Kavram
Activation of user-defined cost allocation tags in the management account of AWS Organizations is required before those tags are recognized and grouped in Cost Explorer.
Tahmini Süre:3m 0s