What should the company do to meet these requirements?
Use a different EC2 instance type for each project.
Publish project-specific custom Amazon CloudWatch metrics for each application.
Deploy EC2 instances for each project in a separate AWS account.
Use cost allocation tags with values that are specific to each project.
Explanations:
Using different EC2 instance types does not inherently track costs by project. This approach may complicate management without providing clear cost separation.
Publishing project-specific CloudWatch metrics would help in monitoring application performance but would not directly assist in tracking infrastructure costs.
Deploying instances in separate AWS accounts would increase management overhead and complexity, and could incur additional costs related to account management.
Using cost allocation tags allows the company to assign specific tags to resources, enabling detailed cost tracking for each project without impacting the existing infrastructure or incurring extra costs.
I measure that the answer is:
Use cost allocation tags with values that are specific to each project.