Which solution will meet this requirement?
Activate cost allocation tags. Add a project tag to the appropriate resources.
Configure consolidated billing. Create AWS Cost and Usage Reports.
Use AWS Budgets. Create AWS Budgets reports.
Use cost categories to define custom groups that are based on AWS cost and usage dimensions.
Explanations:
Activating cost allocation tags allows the organization to categorize and track costs associated with specific projects. By adding a project tag to the relevant resources, the financial department can filter and view the costs related to each project in Cost Explorer.
While configuring consolidated billing and creating AWS Cost and Usage Reports can provide detailed billing information, it does not directly facilitate the viewing of costs by individual projects without additional tagging or categorization. This option lacks the necessary granularity to filter costs by project.
AWS Budgets allow users to set budgets for cost management, but they do not inherently provide the capability to view costs by specific projects unless those projects are tagged accordingly. Budgets are more about managing and alerting on spending rather than categorizing costs for detailed analysis in Cost Explorer.
Using cost categories allows grouping of costs, but it is a higher-level abstraction compared to project-level cost visibility that tagging provides. Without proper tagging of resources, cost categories alone won’t allow detailed tracking of project costs in Cost Explorer.
I value that the answer is:
Activate cost allocation tags. Add a project tag to the appropriate resources.