All providers

AWS Budget actions: what they stop and what they miss

Last checked 2026-10-23 (ET). Tick each step as you go. Progress stays in your browser. Sign in if you want it saved to your account.

A plain AWS budget only sends alerts. A budget action goes one step further. AWS says you can use AWS Budgets "to run an action on your behalf when a budget exceeds a certain cost or usage threshold." That makes it a partial brake, not a hard cap on your whole bill. Back to the main AWS checklist.

Official doc: Configuring budget actions

What a budget action can do

AWS lists three kinds of action:

• Apply an IAM policy. AWS gives the example of a custom Deny policy "that restricts the ability for a user, group, or role to provision additional Amazon EC2 resources."
• Apply a service control policy (SCP). Only a management account can apply SCPs, and from the management account you can apply one to another account.
• Target specific Amazon EC2 or Amazon RDS instances in your account. You can't target instances in another account.

Each action runs either automatically or after you approve it. You can attach more than one action to the same alert, for example at 90 percent of your forecasted monthly cost.

What it does not do

• It does not cap the whole bill. An action only does what you set it to do, such as blocking new resources or stopping the instances you picked.
• It is not instant. AWS says "AWS Budgets information is updated up to three times a day," with updates typically 8 to 12 hours apart.
• AWS also warns: "You might incur additional costs or usage that exceed your budget notification threshold before AWS Budgets can notify you."
• Auto Scaling can undo it. AWS says that if an action stops an EC2 instance in an Auto Scaling group, Auto Scaling "restarts the instance, or launches new instances to replace the stopped instance." AWS suggests a second action that removes permissions on the role used by the group's launch configuration.

Sources: Managing your costs with AWS Budgets and Best practices for AWS Budgets

What it costs

From the AWS Budgets pricing page: "You can monitor and receive notifications on your budgets free of charge." For actions, "Your first two action-enabled budgets are free (regardless of the number of actions you configure per budget) per month. Afterwards each subsequent action-enabled budget will incur a $0.10 daily cost."

Source: AWS Budgets pricing

Before you start

AWS Budgets needs a service role to act for you. AWS says "To use budget actions, you must create a service role for AWS Budgets." AWS offers a managed policy for this role, or example policies you can copy. Without the right permissions, AWS Budgets can't run your actions.

Source: Setting up a role for AWS Budgets to run budget actions

Set up a budget action

1. Open the Billing and Cost Management console and choose Budgets.
2. Create a cost or usage budget, or edit an existing one, and go to the Configure alerts step.
3. Choose Add an alert threshold. Enter the threshold as an absolute amount or a percentage of the budget.
4. Choose Actual for spend that has happened or Forecasted for spend AWS expects.
5. Optional: add up to 10 email recipients, an Amazon SNS topic, or chat alerts. Then choose Next.
6. Under Attach actions - Optional, choose Add Action.
7. Select the IAM role that lets AWS Budgets act for you.
8. Pick the action type: an IAM policy, an SCP, or specific EC2 or RDS instances. Fill in the fields for that action.
9. Choose whether to run it automatically. If you choose No, you run it by hand from the Alert details page.
10. Choose how you want to hear when the action runs, then choose Next, review, and choose Create budget or Save.

The Actions column on the AWS Budgets page then shows how many actions you set up, any that say Requires approval, and any that ran.

Source: Configuring a budget action

Is there a real cap on AWS?

Some accounts can now set a spend limit, which AWS describes this way: if usage reaches the limit, "AWS pauses your project and stops all resources. Your data is preserved." It is part of AWS's new experience, and AWS says "We're currently releasing our new experience to a limited number of customers. You might not be able to access this experience yet." AWS also warns that if you take no action within 90 days of a pause, it permanently deletes the project data. Steps are in the main AWS checklist.

Source: Create a spend limit in AWS Settings

Where CapBrake helps

Most AWS accounts still rely on budgets, alerts and actions. Use the free CapBrake AWS checklist to tick off each step. Progress stays in your browser. Sign in if you want it saved to your account. CapBrake never asks for your credentials.

CapBrake also has an alert relay for AWS, Google Cloud, Firebase and Cloudflare. The relay is free in early access. You add a private relay address as an email recipient on your budget alert, the same alert that runs your action, and CapBrake sends each alert to your browser or Slack. The planned price for the relay is $5/month. We are not charging anything yet, and there are no card fields anywhere on this site.