What should the company do to meet this requirement?
Use cost allocation tags.
Use AWS Identity and Access Management (IAM).
Use AWS Organizations.
Use the AWS Cost Management coverage report.
Explanations:
Cost allocation tags are specifically designed to help categorize and track costs associated with AWS resources. By applying these tags, a company can gain insights into its spending across different departments, projects, or teams. These tags can be used in AWS Cost Explorer and other billing reports to analyze costs effectively.
AWS Identity and Access Management (IAM) is primarily used for managing access to AWS services and resources. While IAM can enforce permissions based on user roles, it does not directly assist in tracking or categorizing costs associated with AWS resources.
AWS Organizations allows you to manage multiple AWS accounts, enabling consolidated billing and account management. However, it does not provide a direct mechanism for tagging or categorizing resources for cost tracking within a single account or across accounts.
The AWS Cost Management coverage report provides insights into the coverage of AWS services used but does not help in categorizing or tagging resources for cost tracking. It focuses more on usage and service adoption rather than cost attribution based on resource tags.
I estimate that the answer is:
Use cost allocation tags.