Budget Control
Budget control helps you monitor your spending and sends email notifications when predefined limits are exceeded.
To use budget control, you must first enable Stacktape cost allocation tags.
Budget control currently only tracks costs for AWS resources. It does not include costs for third-party provider resources, such as MongoDB Atlas Clusters or Upstash for Redis.
If you use custom-defined Cloudformation resources (in the cloudformationResources
section), their costs might not
be correctly attributed to your stack and, therefore, not included in the budget.
This is because Cloudformation does not propagate tags to all resources in a stack. All Stacktape-managed resources are correctly attributed.
How to use budget control
budgetControl:limit: 100 # USD
Notifications
You can configure notifications to be sent when your actual or forecasted spending exceeds a certain threshold.
- Notification sends email(s) to specified email recipients when the notification condition is met.
- Notifications are triggered:
- when the actual spend is over specified threshold.
- when the forecasted spend is forecasted to get over specified threshold.
- You can configure up to 5 notifications per stack.
Actual budget notifications
If you set budgetType
to ACTUAL
(or omit it), a notification is triggered when your actual spending exceeds the
budget limit.
budgetControl:limit: 100 # USDnotifications:- emails:- mail1@example.com- mail2@example.com
Forecasted budget notifications
If you set budgetType
to FORECASTED
, a notification is triggered when your forecasted spending exceeds the budget
limit.
budgetControl:limit: 100notifications:- budgetType: FORECASTEDthresholdPercentage: 80emails:- mail1@example.com
AWS requires approximately five weeks of usage data to generate budget forecasts. If you set a notification to trigger based on a forecasted amount, it will not be sent until you have enough historical usage data.
We recommend using forecasted notifications for long-running production stacks. For more information, refer to the AWS documentation.