Posted On: Apr 2, 2021

You can now configure budgets actions to enforce budget limits for your AWS Budgets resources in your AWS CloudFormation templates, stacks, and StackSets. With budget actions, you can define the action you want to take in your account when a budget exceeds the threshold you defined (actual or forecasted amounts). This level of control will allow you to reduce unintentional overspending in your account. You can choose among three action types: Identity and Access Management (IAM) policy, Service Control policy (SCPs), or target running instances (EC2 or RDS). For example, you can choose to apply a custom “Deny EC2 Run Instances” IAM policy to a user, group, or role in your account, once your monthly budget for EC2 has been exceeded. With the same budget threshold, you can configure a second action that shuts down specific EC2 instances within a particular AWS Region.

Using AWS CloudFormation, you can now create, edit, and delete budgets actions as part of your CloudFormation templates to strengthen cost governance in your automated infrastructure deployments. For example, if you have a template that automates the provisioning of new AWS accounts, you can now add one or more budgets into that template and automatically create an action-enabled budget alongside each new AWS account you create.

To learn more about AWS Budgets Actions, refer to the AWS Budgets webpage or the Configuring AWS Budgets controls section of the Managing Your Costs With Budgets user guide.

To get started using AWS Budget Actions in AWS CloudFormation, visit the AWS CloudFormation console. Please refer to the AWS CloudFormation user guide for more information on using AWS Budgets Actions as a resource in your templates, stacks, and StackSets.