AWS Cost Sensor
The sensor monitors the estimated cost of services in the AWS cloud and the progress of expenses within AWS Budgets.
The sensor calculates the estimated costs for the current month's billing period. You can define an alert when the current cost exceeds a certain value. Alerts can also be defined for costs generated by selected AWS services. As an option, the sensor can read AWS Budgets associated with the selected account. You can define alerting rules for any budget spending progress. Current cost and budget status can be represented with Object Status Widgets.
Requirements
The sensor needs user Access Key ID and Secret Access Key to AWS Cloud authorization. This sensor requires sufficient rights to query data from the AWS Cost Explorer API and AWS Budgets API. In IAM (Identity and Access Management), you need to create a policy with the statement (JSON format):
{ "Sid": "Stmt1613653218000", "Effect": "Allow", "Action": [ "ce:GetCostAndUsage", "ce:GetCostForecast", "ce:getDimensionValues", "budgets:ViewBudget" ], "Resource": [ "*" ] }
Options
By default, the sensor is run once a day. Reading the AWS Budgets information is optional. You need to select the AWS account associated with a budget.
This sensor uses AWS Cost Explorer API and AWS Budgets API. According to the AWS Cost Management Pricing document, each request will incur a cost. This sensor performs two API queries plus one per each defined alert for AWS service cost. Additional one more request, if fetching information about budgets is enabled.
Alerts
- Alert on budget spend progress
- Alert on the total cost
- Alert on AWS service cost