Which solution will meet these requirements?
Use Cost Explorer to troubleshoot the reason for the additional costs. Set up an AWS Lambda function to monitor the company’s AWS bill by each AWS account in an OU. Store the threshold amount set by the Finance team in the AWS Systems Manager Parameter Store. Write the custom rules in the Lambda function to verify any hidden costs for the AWS accounts. Trigger a notification from the Lambda function to an Amazon SNS topic when a budget threshold is breached.
Use AWS Trusted Advisor to troubleshoot the reason for the additional costs. Set up an AWS Lambda function to monitor the company’s AWS bill by each AWS account in an OU. Store the threshold amount set by the Finance team in the AWS Systems Manager Parameter Store. Write custom rules in the Lambda function to verify any hidden costs for the AWS accounts. Trigger an email to the required teams from the Lambda function using Amazon SNS when a budget threshold is breached.
Use Cost Explorer to troubleshoot the reason for the additional costs. Create a budget using AWS Budgets with the monetary amount set by the Finance team for each OU by grouping the linked accounts. Configure an Amazon SNS notification to the required teams in the budget.
Use AWS Trusted Advisor to troubleshoot the reason for the additional costs. Create a budget using AWS Budgets with the monetary amount set by the Finance team for each OU by grouping the linked accounts. Add the Amazon EC2 instance types to be used in the company as a budget filter. Configure an Amazon SNS topic with a subscription for the Finance team email address to receive budget notifications.
Explanations:
While this option suggests using AWS Lambda to monitor costs and trigger notifications, it relies on custom rules in the Lambda function to verify hidden costs, which adds unnecessary complexity. It also does not utilize AWS Budgets, which is specifically designed for tracking and alerting based on spending thresholds.
Similar to Option A, this approach uses AWS Lambda for monitoring but fails to leverage AWS Budgets for predefined thresholds. Instead of managing budgets effectively, it creates custom rules, complicating the implementation. Trusted Advisor is also not the right tool for tracking spending thresholds directly.
This option utilizes AWS Cost Explorer for troubleshooting and sets up AWS Budgets to track costs per organizational unit (OU), aligning perfectly with the requirement to bill business units. Configuring Amazon SNS for budget notifications allows the Finance team to receive alerts when spending exceeds the defined threshold, making it a streamlined and effective solution.
Although this option also suggests creating a budget with AWS Budgets, it relies on AWS Trusted Advisor for troubleshooting costs, which is not as effective for this purpose. Additionally, filtering by Amazon EC2 instance types is unnecessary and does not directly relate to tracking overall budget breaches. The approach does not fully meet the requirement to monitor costs by each business unit effectively.
If I’m correct, the answer is:
Use Cost Explorer to troubleshoot the reason for the additional costs. Create a budget using AWS Budgets with the monetary amount set by the Finance team for each OU by grouping the linked accounts. Configure an Amazon SNS notification to the required teams in the budget.