An enterprise runs workloads across multiple AWS accounts linked via consolidated billing. To monitor project expenditures, a SysOps Administrator tags resources with the keys 'ProjectCode' and 'Owner'. Despite successfully applying these tags to Amazon EC2 instances and Amazon S3 buckets in the member accounts, the administrator cannot find them when attempting to filter or group costs in AWS Cost Explorer. Which two actions must the SysOps Administrator perform to resolve this issue? (Select two.)
- Activate the 'ProjectCode' and 'Owner' tags as cost allocation tags in the Billing and Cost Management console of the management account.Cevap
- Allow up to hours after tag activation for the data to populate and become available in AWS Cost Explorer.Cevap
- CActivate the 'ProjectCode' and 'Owner' tags in the Billing and Cost Management console of each individual member account.
- DConfigure an AWS Config rule to automatically promote the tags to active cost allocation status.
- EEnable the tags directly in AWS Cost Explorer, which automatically activates them in the Billing and Cost Management console.
Cevap
Activate the tags in the Billing and Cost Management console of the organization's management account, and allow up to hours for them to appear in AWS Cost Explorer.
For tags to be used for cost tracking in a consolidated billing environment, they must be manually activated as cost allocation tags in the Billing and Cost Management console of the organization's management account. Once activated, there is a propagation delay of up to hours before they populate and become usable in AWS Cost Explorer.
Adım Adım Çözüm
Anahtar Kavram
In a consolidated billing environment under AWS Organizations, custom resource tags must be manually activated as cost allocation tags in the Billing and Cost Management console of the management account, taking up to hours to propagate to AWS Cost Explorer.