During a department transition, a SysOps Administrator in a member account of an AWS Organization is asked to categorize cloud expenses. The administrator tags all local Amazon EC2 and Amazon Aurora resources with the tag key `BillingGroup`. However, when the administrator tries to build a cost budget filtered by this key in the member account, the tag is missing from the Billing console. What must be done to resolve this issue?
- AThe member account administrator must enable the tag key under the Cost Explorer settings in their local console.
- The management account administrator must activate the `BillingGroup` tag key in the Billing console.Cevap
- CThe administrator must register the tag key in the AWS Resource Groups console to make it visible to AWS Budgets.
- DThe tag key will automatically become active in the member account once it has been applied to at least one resource for 48 hours.
Cevap
The management account administrator must activate the `BillingGroup` tag key in the Billing console.
In a consolidated billing setup under AWS Organizations, all billing and cost-tracking configurations—including the activation of cost allocation tags—must be managed from the management (payer) account. The member accounts apply the tags to their resources, but the management account administrator must log into the Billing console and activate the specific tag key (in this case, `BillingGroup`). Once activated, the tag becomes available for cost budgets and Cost Explorer filtering across all accounts in the organization.
Adım Adım Çözüm
Anahtar Kavram
Cost allocation tags must be manually activated in the Billing console of the management (payer) account in an AWS Organizations environment.
Tahmini Süre:2m 0s