Which solution will meet these requirements?
Use AWS Budgets for each department. Use Tag Editor to apply tags to appropriate resources. Purchase EC2 Instance Savings Plans.
Configure AWS Organizations to use consolidated billing. Implement a tagging strategy that identifies departments. Use SCPs to apply tags to appropriate resources. Purchase EC2 Instance Savings Plans.
Configure AWS Organizations to use consolidated billing. Implement a tagging strategy that identifies departments. Use Tag Editor to apply tags to appropriate resources. Purchase Compute Savings Plans.
Use AWS Budgets for each department. Use SCPs to apply tags to appropriate resources. Purchase Compute Savings Plans.
Explanations:
AWS Budgets and Tag Editor help track and manage costs but don’t directly reduce compute costs. EC2 Instance Savings Plans offer cost savings but lack visibility by department and don’t fully align with the company’s goals to improve cost visibility and flexibility.
While consolidated billing and SCPs can improve management and cost visibility, using SCPs to apply tags is not feasible. SCPs are for policy control and don’t handle resource tagging. Additionally, EC2 Instance Savings Plans are tied to specific instance families and regions, reducing flexibility.
Consolidated billing improves overall billing visibility, and a tagging strategy allows visibility by department. Tag Editor helps apply the tags consistently. Compute Savings Plans provide cost savings while maintaining operational flexibility across instance types and regions. This solution meets all the requirements.
AWS Budgets help with cost tracking, but SCPs cannot be used to apply tags. Additionally, Compute Savings Plans are appropriate, but using SCPs for tags does not align with the requirement of applying tags for cost management.