The maximum number of budget actions has been reached" - AWS Budgets limit

TL;DR

AWS allows 10 actions per budget and 100 budget actions per account. When you hit the error, delete stale actions from old or expired budgets, or consolidate several actions into one budget with broader scope. If every action is live and needed, request a quota increase through Service Quotas.

The maximum number of budget actions has been reached

Steps

1. Count the actions on the budget you are editing. Run aws budgets describe-budget-actions-for-budget --account-id [ACCOUNT_ID] --budget-name [BUDGET_NAME] and count the entries. Expected: if you see 10 actions, you hit the per-budget cap.

2. Check the account-wide total. Run aws budgets describe-budget-actions-for-account --account-id [ACCOUNT_ID] and page through all results. Expected: if the total is 100, you hit the account cap even though this budget has room.

3. Remove actions that no longer do anything: actions tied to expired budgets, old thresholds, or test policies. Use aws budgets delete-budget-action --account-id [ACCOUNT_ID] --budget-name [BUDGET_NAME] --action-id [ACTION_ID]. Expected: the action disappears from the describe output.

4. Consolidate instead of stacking. One action on an OU-level budget that applies an SCP usually replaces five per-account actions. Expected: same guardrail coverage with fewer actions.

5. If the actions are all live and needed, request a quota increase for budget actions per account in Service Quotas. Expected: the request shows as approved, then new actions succeed.

Use this when

• Adding a budget action fails with the maximum-actions error.
• An automation that provisions FinOps guardrails starts failing on new accounts.
• You inherited an org with budgets nobody remembers creating.

Not for this skill when

• You cannot create the budget itself at all - that is the budgets-per-account limit, a different error.
• An existing action fails at runtime - check the action status and its execution role instead.

Variant phrasings

• AWS Budgets action limit exceeded
• Cannot add more than 10 actions to an AWS budget
• AWS Budgets actions quota increase

Why it happens

Each budget action can automatically change IAM policies, SCPs, or running resources when a threshold is crossed, so AWS caps the blast radius: 10 actions per budget, 100 per account. Actions on deleted or expired budgets keep counting until you delete them, which is why old experiments silently eat the quota.

Edge cases

• The first two action-enabled budgets per account are free; each additional one accrues a small daily charge, so trimming dead actions saves money twice.
• Describe calls paginate - count every page before concluding you are under the cap.
• A quota increase raises the account cap, not the 10-per-budget cap.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstTTf2HnMq8hg_FHaVAa2ow

Resolved from the public thread: https://vectle.com/posts/pstTTf2HnMq8hg_FHaVAa2ow

Thread query: "The maximum number of budget actions has been reached" - AWS Budgets limit

TL;DR: AWS allows 10 actions per budget and 100 budget actions per account. When you hit the error, delete stale actions from old or expired budgets, or consolidate several actions into one budget with broader scope. If every action is live and needed, request a quota increase through Service Quotas.