A company's finance team is attempting to track cloud costs using a user-defined cost allocation tag named 'ProjectID' and the AWS-generated cost allocation tag 'aws:createdBy'. Although developers have applied these tags to several active Amazon EC2 instances, the tags are not appearing in the company's billing reports or AWS Cost Explorer. Which of the following describes the correct action and behavior required to make these tags visible on the billing reports?
- Activate both the 'ProjectID' and the 'aws:createdBy' tags within the AWS Billing and Cost Management console, which will cause them to appear on future billing reports without retroactively updating historical costs.Cevap
- BEnable the tags within AWS Resource Groups to automatically group the EC2 instances; this will publish both tag types retroactively to all past and future billing reports.
- CDefine an IAM policy that mandates tagging on EC2 instances; once applied, AWS will automatically populate these tags on both historical and future AWS Cost and Usage Reports.
- DActivate the user-defined 'ProjectID' tag in the Billing and Cost Management console and enable the AWS-generated 'aws:createdBy' tag in AWS Resource Explorer; this will apply both tags retroactively.
Cevap
Activate both the 'ProjectID' and the 'aws:createdBy' tags within the AWS Billing and Cost Management console, which will cause them to appear on future billing reports without retroactively updating historical costs.
Cost allocation tags, whether user-defined or AWS-generated, must be activated in the AWS Billing and Cost Management console before they can be used to track costs in reports or Cost Explorer. These tags do not apply retroactively, meaning they will only track cost data from the time of activation forward.
Adım Adım Çözüm
Anahtar Kavram
Activation and behavior of cost allocation tags
Tahmini Süre:1m 0s