What should the SysOps administrator do to meet this requirement?
Filter, map, and categorize resource groups in Tag Editor.
Ensure that the organization’s service control policies (SCPs) allow access to cost allocation tags.
Ensure that the IAM credentials that are used to access Cost Explorer have permissions to group cost by tags.
Activate the tag keys for cost allocation on the organization’s management account.
Explanations:
Filtering, mapping, and categorizing resource groups in Tag Editor does not provide a direct breakdown of charges by environment. Tag Editor is used for managing tags but does not generate cost reports.
Ensuring that service control policies (SCPs) allow access to cost allocation tags is important for permissions, but it does not directly generate a breakdown of charges by environment. It relates more to access control than reporting.
While ensuring that IAM credentials have permissions to group costs by tags is important, it alone does not fulfill the requirement of generating a cost report; it needs to be combined with other steps such as activating cost allocation tags.
Activating the tag keys for cost allocation on the organization’s management account allows AWS to include these tags in cost and usage reports. This is essential for generating a breakdown of charges by environment in Cost Explorer.
I suspect that the answer is:
Activate the tag keys for cost allocation on the organization’s management account.
From my point of view, the answer is:
Activate the tag keys for cost allocation on the organization’s management account.