A SysOps Administrator applied the tag key `CostCenter` to several Amazon EC2 instances and Amazon S3 buckets to track project expenditures. However, when analyzing costs, the `CostCenter` tag key does not appear as a filtering option in AWS Cost Explorer. Which two actions must the SysOps Administrator perform to resolve this issue and track costs by this tag? (Select TWO.)
- Activate the CostCenter tag in the AWS Billing and Cost Management console.Cevap
- Wait up to 24 hours after activation for the tag to appear in AWS Cost Explorer.Cevap
- CCreate an IAM policy that grants the Billing service permission to read resource tags on the S3 buckets and EC2 instances.
- DEnable resource tag synchronization in the AWS Cost Explorer settings.
- ERe-apply the tags in the AWS Organizations management account, because tags applied in member accounts cannot be used for cost allocation.
Cevap
Activate the CostCenter tag in the AWS Billing and Cost Management console, and wait up to 24 hours for the activated tag to appear in AWS Cost Explorer.
To track costs using a custom resource tag, the tag must be activated in the AWS Billing and Cost Management console. Once activated, it can take up to 24 hours for AWS to update the billing dashboard and display the tag as a filter in AWS Cost Explorer.
Adım Adım Çözüm
Anahtar Kavram
Standard resource tags applied to AWS resources do not automatically function as cost allocation tags. They must be explicitly activated within the AWS Billing and Cost Management console (typically in the management/payer account of an AWS Organization) before they can be used to filter or group costs in AWS Cost Explorer. Once activated, it can take up to 24 hours for the tags to be reflected in Cost Explorer.
Tahmini Süre:1m 30s