CapBrake

All providers

How to cap AWS spending with spend limits and AWS Budgets

0 of 12 steps done

Last checked 2026-10-20 (ET). Tick each step as you go. Your progress is saved in this browser only.

AWS now has two different tools, and which one you can use depends on your account. See all 9 providers.

Option 1: Spend limits (if your account has the new experience)

Official doc: Create a spend limit in AWS Settings

Requirements: you must be on a Paid Plan and be a project owner. Spend limits are set per project, and you can apply them to up to 10 projects.

What it does:

What it does not do:

Option 2: AWS Budgets (every account)

Official docs: Using a budget template and Configuring budget actions

Create a monthly budget:

Add a brake with a budget action (optional): AWS Budgets can run an action when a threshold is crossed, either automatically or after you approve it. Actions can apply an IAM policy or a service control policy, or target specific EC2 or RDS instances. That can block new resources or stop chosen instances. It is a partial brake, not a cap on all spend.

Email recipients: you can add up to 10 per notification. New addresses must be verified, and AWS says "The recipient must be signed in to the AWS account that added the email address to complete verification." (source) You can also send budget alerts to an Amazon SNS topic (source).

How AWS budget alerts work

Official docs: Managing your costs with AWS Budgets and Using a budget template

Also on Google Cloud? Set a spend cap budget there.

Where CapBrake helps

Most AWS accounts cannot set one hard cap on the whole bill yet, so alerts still matter. Use the free CapBrake checklist to tick off each step above. Your progress is saved in your browser. No account and no credentials.

CapBrake also has an alert relay for providers like AWS. It is free in early access. You put a private relay address on your budget alerts, and CapBrake sends each alert to your browser or Slack. CapBrake will never ask for your AWS credentials.