A SysOps Administrator is setting up a CloudWatch billing alarm to monitor estimated monthly charges and send an email notification via Amazon SNS if they exceed a target budget. The administrator logs into the AWS Management Console, navigates to Amazon CloudWatch in the us-east-1 (US East - N. Virginia) region, but discovers that the EstimatedCharges metric is missing from the Billing namespace. What configuration change is required to make the EstimatedCharges metric visible in CloudWatch?
- ACreate an Amazon EventBridge rule to route EstimatedCharges events from the Billing Dashboard to a CloudWatch log group as the primary event destination.
- Enable the option to receive billing alerts in the Billing Preferences section of the AWS Billing and Cost Management console.Answer
- CEnable detailed monitoring with a 1-minute interval for billing metrics within the AWS Billing and Cost Management console.
- DConfigure a static alert in AWS Budgets, which automatically enables and publishes the EstimatedCharges metric to CloudWatch.
Answer
Enable the option to receive billing alerts in the Billing Preferences section of the AWS Billing and Cost Management console.
The EstimatedCharges metric in the CloudWatch Billing namespace is only generated and populated after the user enables billing alerts in the Billing Preferences page of the AWS Billing and Cost Management console. Once this option is turned on, Billing data is published to CloudWatch, allowing the administrator to configure the alarm.
Step-by-Step Solution
Key Concept
Enabling and monitoring EstimatedCharges metrics in CloudWatch for billing alarms.
Estimated Time:1m 0s