[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4AHCGNK44ESRCX30CMBRC":3,"skill-same:01M7A4AHCGNK44ESRCX30CMBRC":140},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7A4AHCGNK44ESRCX30CMBRC","budgets-auditor",null,"Audits AWS Budgets for cost-overrun blind spots: accounts with zero budgets, budgets configured without notifications (decorative budgets), single- threshold alerts that leave no time to react, ACTUAL-only alerts with no FORECASTED warning, SNS topic policies that silently block delivery (missing budgets.amazonaws.com publish principal), breached or on-track-to- breach actual-vs-forecast spend, and missing zero-spend guardrails for new or sandbox accounts. Emits a deterministic verdict (NO_BUDGET | NO_ALERT | CONFIG_GAP | OK) per account with enumerated findings and specific CLI remediation. Use when reviewing cost budgets, checking budget alert thresholds, validating SNS notification wiring, auditing spend posture, or hardening cost controls before a billing review.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: budgets-auditor\ndescription: 'Audits AWS Budgets for cost-overrun blind spots: accounts with zero budgets, budgets configured without notifications (decorative budgets), single- threshold alerts that leave no time to react, ACTUAL-only alerts with no FORECASTED warning, SNS topic policies that silently block delivery (missing budgets.amazonaws.com publish principal), breached or on-track-to- breach actual-vs-forecast spend, and missing zero-spend guardrails for new or sandbox accounts. Emits a deterministic verdict (NO_BUDGET | NO_ALERT | CONFIG_GAP | OK) per account with enumerated findings and specific CLI remediation. Use when reviewing cost budgets, checking budget alert thresholds, validating SNS notification wiring, auditing spend posture, or hardening cost controls before a billing review.'\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline budget-document classification. Live-account audits use aws budgets describe-budget, aws budgets describe-budgets, aws budgets describe-notifications-for-budget, aws budgets describe-subscribers-for-notification, and aws sns get-topic-attributes (AWS CLI v2, SSO or key-based credentials).\nmetadata:\n  domain: aws-cloudops\n  complexity: medium\n  requires_llm: 'true'\n  phase: '2'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: FinOps\n  verdict_shape: NO_BUDGET | NO_ALERT | CONFIG_GAP | OK\n  when_to_use: Reviewing cost budgets before a billing review or production cutover, checking that budget alerts are wired to a real SNS topic, validating threshold coverage (early-warning vs over-budget), auditing actual-vs- forecast breach posture, or hardening spend controls for a new or sandbox account.\n  activation_triggers: audit my AWS budgets, check budget alerts, is my budget wired to SNS, budget notification threshold, zero-spend budget, cost overrun alert, budget forecast exceeded, spend posture audit, budget SNS policy, decorative budget\n  invocation_schema: 'Input: either (a) an account budget inventory (list of budgets, each with notifications, subscribers, SNS topic policies, and calculated spend), OR (b) an account-id for live-account audit. Output: deterministic BUDGET\u002FVERDICT\u002FREASON\u002FFINDINGS\u002FREMEDIATION block per budget plus an account-level aggregate verdict, where VERDICT is one of NO_BUDGET, NO_ALERT, CONFIG_GAP, OK.'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: AWS Budgets, cost budget, budget alert, notification threshold, FORECASTED, ACTUAL, SNS topic policy, budgets.amazonaws.com, zero-spend budget, cost overrun, FinOps, billing alarm, cost control, spend posture, budget action, RI coverage, Consolidated Billing, budget audit, threshold gap\n  tags: budgets, finops, cost-control, alerting, sns, spend, audit\n---\n\n# Budgets Auditor\n\n## Mindset\n\n**One-line takeaway:** a budget without a working notification is decorative —\nit tracks spend nobody watches. The verdict escalates through four blind-spot\ntiers, and three AWS Budgets behaviours are easy to misjudge: **cost-data lag**\n(actuals trail real spend by hours), **silent SNS delivery failure** (a missing\ntopic-policy statement produces zero console error), and **ACTUAL-vs-FORECASTED\nsemantics** (an ACTUAL alert at 100% fires after the money is spent).\n\nAWS Budgets is the first line of cost control, but the configuration is where\nalerting silently fails. Three failure modes dominate:\n\n- **No budgets at all** — the account has zero budgets. Spend runs completely\n  unbounded with no visibility. This is the default state for new accounts and\n  the most dangerous posture for a compromised credential or a runaway\n  resource.\n- **Decorative budget** — a budget exists but has zero notifications (or\n  notifications with no subscribers). It tracks spend in the console but never\n  alerts anyone. The operator believes they have cost control; they have a\n  dashboard.\n- **Wired-wrong alert** — notifications exist but the SNS topic policy omits\n  the `budgets.amazonaws.com` publish principal, OR there is a single 100%\n  ACTUAL threshold with no early warning and no forecast. The alert either\n  silently never delivers, or arrives too late to act on.\n\n## Quick reference — verdict thresholds\n\n| Condition | Verdict | Step |\n|---|---|---|\n| Account has zero budgets | **NO_BUDGET** | 1 |\n| Budget has zero notifications, or all notifications have zero subscribers | **NO_ALERT** | 2 |\n| SNS subscriber present but topic policy lacks `budgets.amazonaws.com` publish | **CONFIG_GAP** | 3 |\n| Only one threshold, or no threshold below 80% | **CONFIG_GAP** | 4 |\n| COST budget with ACTUAL notifications but zero FORECASTED notifications | **CONFIG_GAP** | 5 |\n| `ForecastedSpend > BudgetLimit` with no FORECASTED notification at the breached ratio | **CONFIG_GAP** | 6 |\n| `ActualSpend > BudgetLimit` (breached) with no ACTUAL notification fired | **CONFIG_GAP** | 6 |\n| New\u002Fsandbox account (flagged) with no zero-spend or low-spend budget | **CONFIG_GAP** | 7 |\n| All budgets: multi-threshold, ACTUAL+FORECASTED, SNS wired, not breached | **OK** | 8 |\n\nSteps apply in order — the first step that triggers sets the per-budget\nverdict. The account-level verdict is the **worst** per-budget verdict, where\nNO_BUDGET > NO_ALERT > CONFIG_GAP > OK. See the ordered classification below\nfor edge cases and additive findings.\n\n## Pre-flight: input and account-metadata gate\n\nBefore classification, validate the input structure and identify metadata that\nshort-circuits the audit.\n\n**Live-account sweep note (pagination):** moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before running a live-account budgets sweep.\n\n**Live-account pre-flight checks (skip if doing offline budget-doc audit):**\nFull pre-flight command list moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when auditing a live account (permissions, payer inventory, budget performance history).\n\n**If the budget inventory is malformed** (invalid JSON\u002FYAML, missing required\n`BudgetName` or `BudgetLimit` on a COST budget), output:\n\n```text\nBUDGET: \u003Cname or unknown>\nVERDICT: ERROR\nREASON: Budget configuration is not valid — cannot classify (missing BudgetName or BudgetLimit).\nREMEDIATION: Re-fetch with `aws budgets describe-budget --account-id \u003Cid> --budget-name \u003Cname> --region us-east-1` and re-audit.\n```\n\nDo not attempt classification on malformed input.\n\n## Process — Classification logic (apply in order, aggregate worst)\n\n### Step 0: Expert knowledge — non-obvious AWS Budgets behaviours\n\nAll Step 0 behaviours moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a verdict depends on a non-obvious Budgets behaviour (cost-data lag, silent SNS failure, RI\u002FSP types, auto-adjust, CostTypes).\n\n### Step 1: Budget existence gate (NO_BUDGET — highest priority)\n\nIf the account has **zero budgets** of any type (COST, RI_*, SP_*, USAGE),\nthe verdict is **NO_BUDGET**. This is the worst posture: no spend visibility,\nno alerting, no forecast. This is the default state for newly created\naccounts and the highest-risk configuration for credential compromise or\nrunaway resources.\n\nNO_BUDGET short-circuits all other steps — there is nothing to evaluate\nnotifications against. The remediation is to create at minimum a total-account\ncost budget and (for new\u002Fsandbox accounts) a zero-spend guardrail.\n\n### Step 2: Notification and subscriber gate (NO_ALERT)\n\nFor each budget, evaluate notification coverage:\n\n- **Zero notifications** on the budget → the budget is **decorative**. It\n  tracks spend in the console but never alerts anyone. Per-budget verdict:\n  **NO_ALERT**.\n- **Notifications exist but every notification has an empty subscriber list**\n  (`Subscribers: []`) → the notification has nowhere to deliver. Per-budget\n  verdict: **NO_ALERT**.\n\nA budget that triggers NO_ALERT is functionally equivalent to no budget for\nthe purpose of alerting — the spend may as well be unmonitored. The difference\nbetween NO_BUDGET and NO_ALERT is that NO_ALERT means \"the tracking exists but\nthe human-in-the-loop is severed,\" while NO_BUDGET means \"there is no tracking\nat all.\" Both are HIGH risk.\n\n### Step 3: SNS topic policy delivery check (CONFIG_GAP)\n\nFor each notification with an SNS subscriber (`SubscriptionType: SNS`), the\nnotification can only deliver if the SNS topic policy grants `sns:Publish` to\nthe `budgets.amazonaws.com` service principal. Retrieve the topic policy\n(`aws sns get-topic-attributes --topic-arn \u003Carn>`) and check for a statement\nmatching:\n\n```json\n{\n  \"Effect\": \"Allow\",\n  \"Principal\": { \"Service\": \"budgets.amazonaws.com\" },\n  \"Action\": \"SNS:Publish\",\n  \"Resource\": \"\u003Ctopic-arn>\"\n}\n```\n\n- **Statement absent** → the notification will silently fail to deliver.\n  Per-budget verdict: **CONFIG_GAP** (Finding: SNS_POLICY_GAP). This is the\n  most common reason budget alerts \"don't work\" and produces zero console\n  error.\n- **Statement present but scoped to a different region or account** →\n  CONFIG_GAP (the ARN mismatch causes rejection).\n- **EMAIL\u002FEMAIL-JSON subscribers do NOT require an SNS topic policy** —\n  Budgets delivers directly to the email address. Skip Step 3 for email-only\n  subscribers. (Note: email subscribers still require a confirmation click on\n  the AWS-sent subscription email; an unconfirmed email is a delivery gap but\n  is surfaced in the console, unlike the silent SNS policy failure.)\n\n### Step 4: Threshold coverage check (CONFIG_GAP)\n\nFor each COST budget with notifications, evaluate the threshold set:\n\n- **Single threshold** (only one notification on the budget) → **CONFIG_GAP**\n  (Finding: SINGLE_THRESHOLD). A single alert leaves no time to react —\n  regardless of where it sits, there is no early-warning tier.\n- **No threshold below 80%** → **CONFIG_GAP** (Finding: NO_EARLY_WARNING). If\n  the lowest threshold is at 80% or higher, the operator gets no awareness\n  signal before the budget is nearly exhausted. Best practice: at least one\n  threshold at 50% (awareness) and one at 80-90% (action).\n- **No threshold at or above 100%** → **CONFIG_GAP** (Finding: NO_BREACH_ALERT).\n  If no notification covers the actual breach point, the operator may never\n  learn they are over budget.\n\nA budget with thresholds at {50%, 80%, 100%} or {70%, 90%, 100%} passes this\nstep. A budget with only {100%} or only {90%} fails.\n\n### Step 5: FORECASTED coverage check (COST budgets only — CONFIG_GAP)\n\nFor each COST budget (BudgetType `COST` or `USAGE`), evaluate notification\ntypes:\n\n- **All notifications are `ACTUAL`, zero `FORECASTED`** → **CONFIG_GAP**\n  (Finding: NO_FORECAST). Without a FORECASTED notification, the operator has\n  no predictive signal. Combined with cost-data lag, an ACTUAL-only alert at\n  100% arrives after the budget is already breached by hours. A FORECASTED\n  notification at 80-100% projects month-end spend and gives lead time.\n\nThis check does NOT apply to RI\u002FSP budgets (their \"forecast\" is utilization\ntrajectory, handled differently) or to DAILY budgets where month-end\nprojection is meaningless.\n\n### Step 6: Actual-vs-forecast breach check (CONFIG_GAP)\n\nFor each COST budget, compare `CalculatedSpend` against `BudgetLimit`:\n\n- **`ForecastedSpend >= BudgetLimit`** and NO FORECASTED notification covers\n  the breached ratio → **CONFIG_GAP** (Finding: FORECAST_BREACH_UNALERTED).\n  The budget is on track to exceed by month-end but no forecast alert will\n  fire.\n- **`ActualSpend >= BudgetLimit`** (already breached) and NO ACTUAL\n  notification covers 100% → **CONFIG_GAP** (Finding: ACTUAL_BREACH_UNALERTED).\n  The budget has been exceeded but no actual alert will fire.\n\nNote: a breach with a matching alert that WILL fire is informational, not a\nCONFIG_GAP — the system is working as designed. Only flag when the breach is\nuncovered by the notification set.\n\n### Step 7: Zero-spend guardrail for new\u002Fsandbox accounts (CONFIG_GAP)\n\nIf the account is flagged as new, sandbox, or non-production (operator-provided\ncontext, or account name\u002Ftag convention), check for a zero-spend or low-spend\nguardrail:\n\n- **No COST budget with `BudgetLimit \u003C= $1.00` (or `\u003C= $0.01`) and a 100%\n  ACTUAL notification** → **CONFIG_GAP** (Finding: NO_ZERO_SPEND_GUARDRAIL).\n  A zero-spend budget catches ANY unauthorized spend immediately — the leading\n  signal for a compromised credential, a misconfigured free-tier resource, or\n  a stray workload. Without it, a new account can accumulate charges for days\n  before a normal budget trips.\n\nThis check is advisory-in-practice but Config_GAP-in-verdict because the\nabsence of a zero-spend guardrail on a new account is the single highest-leverage\nFinOps control. For established production accounts, skip this step.\n\n### Step 8: Aggregation — worst per-budget verdict wins\n\nThe account-level verdict is the **maximum severity** across all per-budget\nverdicts, where NO_BUDGET > NO_ALERT > CONFIG_GAP > OK:\n\n```text\naccount_verdict = max(all_budget_verdicts)\n```\n\nIf the account has budgets and all pass Steps 2-7 with no findings, the\naccount verdict is **OK**. NO_BUDGET is only reachable when the account has\nzero budgets (Step 1).\n\n**Severity\u002Frisk mapping (emitted per finding):**\n- NO_BUDGET → **HIGH** (total spend blind spot; default for new accounts)\n- NO_ALERT → **HIGH** (budget is decorative; spend tracked but never alerted)\n- CONFIG_GAP (SNS_POLICY_GAP) → **HIGH** (alerts silently fail to deliver)\n- CONFIG_GAP (SINGLE_THRESHOLD \u002F NO_EARLY_WARNING \u002F NO_FORECAST) → **MEDIUM**\n- CONFIG_GAP (NO_ZERO_SPEND_GUARDRAIL) → **MEDIUM** for new accounts\n- CONFIG_GAP (breach uncovered) → **MEDIUM** (the breach is real but alertable\n  with a fix)\n- OK → **LOW**\n\n## Output format (per account)\n\n```text\nACCOUNT: \u003Caccount-id>\nVERDICT: NO_BUDGET | NO_ALERT | CONFIG_GAP | OK\nREASON: \u003C1-2 sentences citing the triggering step and worst finding>\nFINDINGS:\n  - [HIGH] \u003Cbudget name>: \u003Cfinding description (Step N)>\n  - [MEDIUM] \u003Cbudget name>: \u003Cfinding description (Step N)>\n  - [OK] \u003Cbudget name>: \u003Cdimension that passed>\nREMEDIATION: \u003Cspecific action per finding, or \"None required\" if OK>\n```\n\n### Worked example — decorative budget with SNS policy gap\n\n```text\nACCOUNT: 111111111111\nVERDICT: CONFIG_GAP\nREASON: Budget \"monthly-total\" has a single 100% ACTUAL notification wired to\nan SNS topic whose policy omits the budgets.amazonaws.com publish principal —\nalerts silently fail to deliver (Step 3), and there is no FORECASTED\nnotification for lead time (Step 5).\nFINDINGS:\n  - [HIGH] monthly-total: SNS topic arn:aws:sns:us-east-1:111111111111:budget-alerts\n    policy lacks budgets.amazonaws.com sns:Publish — alerts dispatched but\n    rejected at delivery (Step 3)\n  - [MEDIUM] monthly-total: single threshold at 100% ACTUAL — no early warning\n    and no FORECASTED notification (Steps 4, 5)\n  - [OK] monthly-total: budget exists with BudgetLimit $10000, not breached\nREMEDIATION:\n  1. Add the budgets service principal to the SNS topic policy (see Step 3\n     remediation CLI).\n  2. Add a FORECASTED notification at 80% and an early-warning ACTUAL at 50%.\n```\n\n## Edge-case handling\n\nFull edge-case catalog moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when input hits an edge case (malformed budget, email-only subscriber, payer-covered member, DAILY budget, Budget Action).\n\n## Anti-Patterns — NEVER\n\n- NEVER classify an account with zero budgets as anything other than\n  NO_BUDGET. \"No budgets\" is a total spend blind spot — the highest-risk\n  FinOps posture. Do not soften it to CONFIG_GAP.\n\n- NEVER treat a budget with zero notifications as OK. A budget without\n  notifications is decorative — it tracks spend nobody watches. This is\n  NO_ALERT, not OK. The console showing a spend number is not alerting.\n\n- NEVER assume an SNS subscriber means alerts will deliver. The SNS topic\n  policy MUST explicitly grant `sns:Publish` to `budgets.amazonaws.com`. A\n  missing policy statement fails silently with zero console error — this is\n  the #1 reason budget alerts \"don't work.\" Always read the topic policy.\n\n- NEVER flag an RI_COVERAGE \u002F RI_UTILIZATION \u002F SP_COVERAGE \u002F SP_UTILIZATION\n  budget as cost-breached. These budget types measure reservation\n  effectiveness (a percentage), not spend. They have no dollar BudgetLimit.\n  Applying cost-breach logic to them is a false positive.\n\n- NEVER treat the absence of a Budget Action as a CONFIG_GAP. Budget Actions\n  (enforcement) are an opt-in tier separate from alerting. Most accounts use\n  alert-only budgets by design. Only flag a misconfigured Action if one is\n  present.\n\n- NEVER assume \"actual under limit\" means the budget is safe. Cost-data lag\n  trails real spend by 8-14 hours. A budget at 90% actual may already be over.\n  Always check the FORECASTED spend against the limit, not just actual.\n\n- NEVER recommend a single-threshold budget as adequate. A lone 100% ACTUAL\n  alert fires after the spend is incurred plus the data lag. A budget needs at\n  least an early-warning tier (50%) and an action tier (80-90%) below the\n  breach alert (100%).\n\n- NEVER treat a CloudWatch billing alarm as a substitute for a budget.\n  Billing alarms (`AWS\u002FBilling EstimatedCharges`) are account-total only,\n  update every ~6 hours, and have no FORECASTED projection or filtering. They\n  are legacy defense-in-depth, not a replacement for AWS Budgets.\n\n- NEVER skip pagination on `describe-budgets` or\n  `describe-notifications-for-budget`. The long tail of budgets (beyond page\n  one) is where stale, decorative, and breached budgets hide. Always drain\n  `NextToken` to completion.\n\n- NEVER conflate FORECASTED and ACTUAL notification types. FORECASTED projects\n  month-end spend; ACTUAL reports current calculated spend. They are not\n  interchangeable. A budget with only ACTUAL notifications is reactive; a\n  budget with FORECASTED notifications is predictive. Both belong in a mature\n  budget config.\n\n- NEVER assume a payer-wide budget covers a member account's alerting needs.\n  A payer budget with no `LinkedAccount` filter aggregates all member spend\n  but a runaway member account can hide inside an aggregate that is under\n  limit. For chargeback and isolation, member accounts need their own budgets\n  or the payer budget must be filtered per account.\n\n- NEVER propose more than 11 notifications on a single budget. The quota is\n  11 notifications per budget (hard limit). A remediation proposing a 12th\n  notification will fail with `LimitExceededException`. Count existing\n  notifications before adding.\n\n- NEVER ignore the `CostTypes` filter when assessing breach. A budget with\n  `IncludeTax: false` under-reports by the tax line. Two budgets with the same\n  limit and different `CostTypes` are not comparable. Confirm the filter\n  matches intent before flagging a breach.\n\n## Pre-flight safety checks (run before any remediation CLI)\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation\n  (CreateBudget, CreateNotification, CreateSubscriber, DeleteNotification,\n  SetTopicAttributes on an SNS policy, PutBudgetAction), the auditor MUST\n  emit: `CONFIRM: About to \u003Caction> on budget \u003Cname> in account \u003Caccount>.\n  This affects \u003Cconsequence>. Proceed? (yes\u002Fno)` Do NOT execute the CLI\n  command until the operator confirms. Budgets changes can suppress or\n  duplicate live alerting.\n- Confirm the caller identity has `budgets:Create*` and `sns:SetTopicAttributes`\n  if remediation is intended — most read-only auditor roles CANNOT, and\n  remediation commands will fail with `AccessDenied`. Surface this BEFORE the\n  operator approves.\n- Before modifying an SNS topic policy, capture the current policy for\n  rollback: `aws sns get-topic-attributes --topic-arn \u003Carn> --region us-east-1\n  > \u002Ftmp\u002F\u003Ctopic>-policy-backup-$(date +%s).json`. SNS topic policies are not\n  versioned — a bad policy statement can break ALL topic publishers, not just\n  Budgets.\n- Prefer additive changes (add a notification, add a topic-policy statement)\n  over destructive changes (delete a notification, replace a policy). Additive\n  changes are reversible and cannot break existing delivery.\n- Before creating a zero-spend budget on a new account, confirm the account\n  has no expected spend (a zero-spend budget with legitimate ongoing spend\n  generates constant false-positive alerts). For sandbox accounts with small\n  expected spend, use a $1 or $5 guardrail, not $0.01.\n\n## Remediation guidance\n\n**Ordering principle:** always prefer additive changes. Add a notification\nbefore deleting one; add a topic-policy statement before rewriting the policy.\nThis prevents a window where no alerting is in effect.\n\n### For NO_BUDGET — account has zero budgets\n\n1. Create a total-account MONTHLY cost budget at the operator's expected\n   monthly spend:\n   `aws budgets create-budget --account-id \u003Cid> --budget file:\u002F\u002Ftotal.json\n   --notifications-with-subscribers file:\u002F\u002Fsubs.json --region us-east-1`\n2. Add at minimum: ACTUAL 50%, FORECASTED 80%, ACTUAL 100% notifications wired\n   to an SNS topic (with the budgets principal in its policy) or an email.\n3. For new\u002Fsandbox accounts, additionally create a zero-spend guardrail\n   (Step 7).\n4. For Organizations\u002Fconsolidated-billing, create a payer-level budget AND per-\n   member budgets (or filtered payer budgets) for chargeback visibility.\n\n### For NO_ALERT — budget has zero functional notifications\n\n1. Create notifications: `aws budgets create-notification --account-id \u003Cid>\n   --budget-name \u003Cname> --notification \u003Cjson> --subscribers \u003Cjson>\n   --region us-east-1`.\n2. Minimum set for a MONTHLY COST budget: ACTUAL 50% (awareness), FORECASTED\n   80% (action), ACTUAL 100% (breach). Wire each to an SNS topic or email.\n3. Confirm the SNS topic policy grants `budgets.amazonaws.com` publish (see\n   CONFIG_GAP \u002F SNS policy remediation).\n\n### For CONFIG_GAP — SNS topic policy missing budgets principal (Step 3)\n\n1. Retrieve the current policy: `aws sns get-topic-attributes --topic-arn \u003Carn>\n   --region us-east-1 --query 'Attributes.Policy' --output text`.\n2. Add (do not replace) a statement granting the budgets principal publish:\n   ```bash\n   aws sns set-topic-attributes --topic-arn \u003Carn> --region us-east-1 \\\n     --attribute-name Policy --attribute-value '\u003Cupdated-policy-json-with-budgets-statement>'\n   ```\n3. Verify delivery by triggering a test budget notification or waiting for the\n   next threshold crossing and checking CloudTrail for a `Publish` event from\n   `budgets.amazonaws.com`.\n\n### For CONFIG_GAP — single threshold \u002F no early warning (Step 4)\n\n1. Add a 50% ACTUAL notification (awareness) and an 80-90% ACTUAL or\n   FORECASTED notification (action tier) via `create-notification`.\n2. Keep the existing 100% notification as the breach tier. Do NOT delete it.\n3. Confirm total notifications do not exceed 11 per budget.\n\n### For CONFIG_GAP — no FORECASTED notification (Step 5)\n\n1. Add a FORECASTED notification at 80% and\u002For 100% via\n   `create-notification --notification ... --notification-type FORECASTED`.\n2. This provides lead time that ACTUAL-only alerts cannot, given cost-data\n   lag.\n\n### For CONFIG_GAP — zero-spend guardrail missing (Step 7)\n\n1. Create a COST budget with `BudgetLimit.Amount: 0.01` (or `1.00` for sandbox\n   with tiny expected spend), `TimeUnit: MONTHLY`, and an ACTUAL 100%\n   notification wired to an SNS topic or email.\n2. Name it distinctly (e.g., `zero-spend-guardrail`) so it is recognizable in\n   audits.\n\n### For OK\n\n1. No remediation required for current posture.\n2. Recommend verifying the SNS topic policy quarterly — policy drift from\n   other tooling can silently remove the budgets principal.\n3. Recommend confirming email subscribers are still valid (personnel churn).\n4. For Organizations, verify member accounts have independent alerting, not\n   just payer-level coverage.\n\n## Deep reference: AWS Budgets internals\n\nInternals deep dive (notification delivery pipeline, cost data lag, quotas) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when explaining why a verdict fired or planning notification changes.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand to check 2024-2026 Budgets feature coverage.\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step 0 expert knowledge, edge-case catalog, Budgets internals deep dive, 2024-2026 features.\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pagination sweep and pre-flight permission\u002Fpayer\u002Fhistory checks.\n\n## Domain\n\nAWS CloudOps \u002F FinOps Cost Control & Spend Visibility.\n\n## AWS documentation\n\n- **AWS Budgets User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fbudgets-managing-costs.html\n- **Security in AWS Cost Management** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fsecurity.html\n- **AWS Budgets API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Faws-cost-management\u002Flatest\u002FAPIReference\u002FAPI_Operations_AWS_Budgets.html\n- **AWS Budgets CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fbudgets\u002F\n","# Budgets Auditor\n\n## Mindset\n\n**One-line takeaway:** a budget without a working notification is decorative —\nit tracks spend nobody watches. The verdict escalates through four blind-spot\ntiers, and three AWS Budgets behaviours are easy to misjudge: **cost-data lag**\n(actuals trail real spend by hours), **silent SNS delivery failure** (a missing\ntopic-policy statement produces zero console error), and **ACTUAL-vs-FORECASTED\nsemantics** (an ACTUAL alert at 100% fires after the money is spent).\n\nAWS Budgets is the first line of cost control, but the configuration is where\nalerting silently fails. Three failure modes dominate:\n\n- **No budgets at all** — the account has zero budgets. Spend runs completely\n  unbounded with no visibility. This is the default state for new accounts and\n  the most dangerous posture for a compromised credential or a runaway\n  resource.\n- **Decorative budget** — a budget exists but has zero notifications (or\n  notifications with no subscribers). It tracks spend in the console but never\n  alerts anyone. The operator believes they have cost control; they have a\n  dashboard.\n- **Wired-wrong alert** — notifications exist but the SNS topic policy omits\n  the `budgets.amazonaws.com` publish principal, OR there is a single 100%\n  ACTUAL threshold with no early warning and no forecast. The alert either\n  silently never delivers, or arrives too late to act on.\n\n## Quick reference — verdict thresholds\n\n| Condition | Verdict | Step |\n|---|---|---|\n| Account has zero budgets | **NO_BUDGET** | 1 |\n| Budget has zero notifications, or all notifications have zero subscribers | **NO_ALERT** | 2 |\n| SNS subscriber present but topic policy lacks `budgets.amazonaws.com` publish | **CONFIG_GAP** | 3 |\n| Only one threshold, or no threshold below 80% | **CONFIG_GAP** | 4 |\n| COST budget with ACTUAL notifications but zero FORECASTED notifications | **CONFIG_GAP** | 5 |\n| `ForecastedSpend > BudgetLimit` with no FORECASTED notification at the breached ratio | **CONFIG_GAP** | 6 |\n| `ActualSpend > BudgetLimit` (breached) with no ACTUAL notification fired | **CONFIG_GAP** | 6 |\n| New\u002Fsandbox account (flagged) with no zero-spend or low-spend budget | **CONFIG_GAP** | 7 |\n| All budgets: multi-threshold, ACTUAL+FORECASTED, SNS wired, not breached | **OK** | 8 |\n\nSteps apply in order — the first step that triggers sets the per-budget\nverdict. The account-level verdict is the **worst** per-budget verdict, where\nNO_BUDGET > NO_ALERT > CONFIG_GAP > OK. See the ordered classification below\nfor edge cases and additive findings.\n\n## Pre-flight: input and account-metadata gate\n\nBefore classification, validate the input structure and identify metadata that\nshort-circuits the audit.\n\n**Live-account sweep note (pagination):** moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before running a live-account budgets sweep.\n\n**Live-account pre-flight checks (skip if doing offline budget-doc audit):**\nFull pre-flight command list moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when auditing a live account (permissions, payer inventory, budget performance history).\n\n**If the budget inventory is malformed** (invalid JSON\u002FYAML, missing required\n`BudgetName` or `BudgetLimit` on a COST budget), output:\n\n```text\nBUDGET: \u003Cname or unknown>\nVERDICT: ERROR\nREASON: Budget configuration is not valid — cannot classify (missing BudgetName or BudgetLimit).\nREMEDIATION: Re-fetch with `aws budgets describe-budget --account-id \u003Cid> --budget-name \u003Cname> --region us-east-1` and re-audit.\n```\n\nDo not attempt classification on malformed input.\n\n## Process — Classification logic (apply in order, aggregate worst)\n\n### Step 0: Expert knowledge — non-obvious AWS Budgets behaviours\n\nAll Step 0 behaviours moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a verdict depends on a non-obvious Budgets behaviour (cost-data lag, silent SNS failure, RI\u002FSP types, auto-adjust, CostTypes).\n\n### Step 1: Budget existence gate (NO_BUDGET — highest priority)\n\nIf the account has **zero budgets** of any type (COST, RI_*, SP_*, USAGE),\nthe verdict is **NO_BUDGET**. This is the worst posture: no spend visibility,\nno alerting, no forecast. This is the default state for newly created\naccounts and the highest-risk configuration for credential compromise or\nrunaway resources.\n\nNO_BUDGET short-circuits all other steps — there is nothing to evaluate\nnotifications against. The remediation is to create at minimum a total-account\ncost budget and (for new\u002Fsandbox accounts) a zero-spend guardrail.\n\n### Step 2: Notification and subscriber gate (NO_ALERT)\n\nFor each budget, evaluate notification coverage:\n\n- **Zero notifications** on the budget → the budget is **decorative**. It\n  tracks spend in the console but never alerts anyone. Per-budget verdict:\n  **NO_ALERT**.\n- **Notifications exist but every notification has an empty subscriber list**\n  (`Subscribers: []`) → the notification has nowhere to deliver. Per-budget\n  verdict: **NO_ALERT**.\n\nA budget that triggers NO_ALERT is functionally equivalent to no budget for\nthe purpose of alerting — the spend may as well be unmonitored. The difference\nbetween NO_BUDGET and NO_ALERT is that NO_ALERT means \"the tracking exists but\nthe human-in-the-loop is severed,\" while NO_BUDGET means \"there is no tracking\nat all.\" Both are HIGH risk.\n\n### Step 3: SNS topic policy delivery check (CONFIG_GAP)\n\nFor each notification with an SNS subscriber (`SubscriptionType: SNS`), the\nnotification can only deliver if the SNS topic policy grants `sns:Publish` to\nthe `budgets.amazonaws.com` service principal. Retrieve the topic policy\n(`aws sns get-topic-attributes --topic-arn \u003Carn>`) and check for a statement\nmatching:\n\n```json\n{\n  \"Effect\": \"Allow\",\n  \"Principal\": { \"Service\": \"budgets.amazonaws.com\" },\n  \"Action\": \"SNS:Publish\",\n  \"Resource\": \"\u003Ctopic-arn>\"\n}\n```\n\n- **Statement absent** → the notification will silently fail to deliver.\n  Per-budget verdict: **CONFIG_GAP** (Finding: SNS_POLICY_GAP). This is the\n  most common reason budget alerts \"don't work\" and produces zero console\n  error.\n- **Statement present but scoped to a different region or account** →\n  CONFIG_GAP (the ARN mismatch causes rejection).\n- **EMAIL\u002FEMAIL-JSON subscribers do NOT require an SNS topic policy** —\n  Budgets delivers directly to the email address. Skip Step 3 for email-only\n  subscribers. (Note: email subscribers still require a confirmation click on\n  the AWS-sent subscription email; an unconfirmed email is a delivery gap but\n  is surfaced in the console, unlike the silent SNS policy failure.)\n\n### Step 4: Threshold coverage check (CONFIG_GAP)\n\nFor each COST budget with notifications, evaluate the threshold set:\n\n- **Single threshold** (only one notification on the budget) → **CONFIG_GAP**\n  (Finding: SINGLE_THRESHOLD). A single alert leaves no time to react —\n  regardless of where it sits, there is no early-warning tier.\n- **No threshold below 80%** → **CONFIG_GAP** (Finding: NO_EARLY_WARNING). If\n  the lowest threshold is at 80% or higher, the operator gets no awareness\n  signal before the budget is nearly exhausted. Best practice: at least one\n  threshold at 50% (awareness) and one at 80-90% (action).\n- **No threshold at or above 100%** → **CONFIG_GAP** (Finding: NO_BREACH_ALERT).\n  If no notification covers the actual breach point, the operator may never\n  learn they are over budget.\n\nA budget with thresholds at {50%, 80%, 100%} or {70%, 90%, 100%} passes this\nstep. A budget with only {100%} or only {90%} fails.\n\n### Step 5: FORECASTED coverage check (COST budgets only — CONFIG_GAP)\n\nFor each COST budget (BudgetType `COST` or `USAGE`), evaluate notification\ntypes:\n\n- **All notifications are `ACTUAL`, zero `FORECASTED`** → **CONFIG_GAP**\n  (Finding: NO_FORECAST). Without a FORECASTED notification, the operator has\n  no predictive signal. Combined with cost-data lag, an ACTUAL-only alert at\n  100% arrives after the budget is already breached by hours. A FORECASTED\n  notification at 80-100% projects month-end spend and gives lead time.\n\nThis check does NOT apply to RI\u002FSP budgets (their \"forecast\" is utilization\ntrajectory, handled differently) or to DAILY budgets where month-end\nprojection is meaningless.\n\n### Step 6: Actual-vs-forecast breach check (CONFIG_GAP)\n\nFor each COST budget, compare `CalculatedSpend` against `BudgetLimit`:\n\n- **`ForecastedSpend >= BudgetLimit`** and NO FORECASTED notification covers\n  the breached ratio → **CONFIG_GAP** (Finding: FORECAST_BREACH_UNALERTED).\n  The budget is on track to exceed by month-end but no forecast alert will\n  fire.\n- **`ActualSpend >= BudgetLimit`** (already breached) and NO ACTUAL\n  notification covers 100% → **CONFIG_GAP** (Finding: ACTUAL_BREACH_UNALERTED).\n  The budget has been exceeded but no actual alert will fire.\n\nNote: a breach with a matching alert that WILL fire is informational, not a\nCONFIG_GAP — the system is working as designed. Only flag when the breach is\nuncovered by the notification set.\n\n### Step 7: Zero-spend guardrail for new\u002Fsandbox accounts (CONFIG_GAP)\n\nIf the account is flagged as new, sandbox, or non-production (operator-provided\ncontext, or account name\u002Ftag convention), check for a zero-spend or low-spend\nguardrail:\n\n- **No COST budget with `BudgetLimit \u003C= $1.00` (or `\u003C= $0.01`) and a 100%\n  ACTUAL notification** → **CONFIG_GAP** (Finding: NO_ZERO_SPEND_GUARDRAIL).\n  A zero-spend budget catches ANY unauthorized spend immediately — the leading\n  signal for a compromised credential, a misconfigured free-tier resource, or\n  a stray workload. Without it, a new account can accumulate charges for days\n  before a normal budget trips.\n\nThis check is advisory-in-practice but Config_GAP-in-verdict because the\nabsence of a zero-spend guardrail on a new account is the single highest-leverage\nFinOps control. For established production accounts, skip this step.\n\n### Step 8: Aggregation — worst per-budget verdict wins\n\nThe account-level verdict is the **maximum severity** across all per-budget\nverdicts, where NO_BUDGET > NO_ALERT > CONFIG_GAP > OK:\n\n```text\naccount_verdict = max(all_budget_verdicts)\n```\n\nIf the account has budgets and all pass Steps 2-7 with no findings, the\naccount verdict is **OK**. NO_BUDGET is only reachable when the account has\nzero budgets (Step 1).\n\n**Severity\u002Frisk mapping (emitted per finding):**\n- NO_BUDGET → **HIGH** (total spend blind spot; default for new accounts)\n- NO_ALERT → **HIGH** (budget is decorative; spend tracked but never alerted)\n- CONFIG_GAP (SNS_POLICY_GAP) → **HIGH** (alerts silently fail to deliver)\n- CONFIG_GAP (SINGLE_THRESHOLD \u002F NO_EARLY_WARNING \u002F NO_FORECAST) → **MEDIUM**\n- CONFIG_GAP (NO_ZERO_SPEND_GUARDRAIL) → **MEDIUM** for new accounts\n- CONFIG_GAP (breach uncovered) → **MEDIUM** (the breach is real but alertable\n  with a fix)\n- OK → **LOW**\n\n## Output format (per account)\n\n```text\nACCOUNT: \u003Caccount-id>\nVERDICT: NO_BUDGET | NO_ALERT | CONFIG_GAP | OK\nREASON: \u003C1-2 sentences citing the triggering step and worst finding>\nFINDINGS:\n  - [HIGH] \u003Cbudget name>: \u003Cfinding description (Step N)>\n  - [MEDIUM] \u003Cbudget name>: \u003Cfinding description (Step N)>\n  - [OK] \u003Cbudget name>: \u003Cdimension that passed>\nREMEDIATION: \u003Cspecific action per finding, or \"None required\" if OK>\n```\n\n### Worked example — decorative budget with SNS policy gap\n\n```text\nACCOUNT: 111111111111\nVERDICT: CONFIG_GAP\nREASON: Budget \"monthly-total\" has a single 100% ACTUAL notification wired to\nan SNS topic whose policy omits the budgets.amazonaws.com publish principal —\nalerts silently fail to deliver (Step 3), and there is no FORECASTED\nnotification for lead time (Step 5).\nFINDINGS:\n  - [HIGH] monthly-total: SNS topic arn:aws:sns:us-east-1:111111111111:budget-alerts\n    policy lacks budgets.amazonaws.com sns:Publish — alerts dispatched but\n    rejected at delivery (Step 3)\n  - [MEDIUM] monthly-total: single threshold at 100% ACTUAL — no early warning\n    and no FORECASTED notification (Steps 4, 5)\n  - [OK] monthly-total: budget exists with BudgetLimit $10000, not breached\nREMEDIATION:\n  1. Add the budgets service principal to the SNS topic policy (see Step 3\n     remediation CLI).\n  2. Add a FORECASTED notification at 80% and an early-warning ACTUAL at 50%.\n```\n\n## Edge-case handling\n\nFull edge-case catalog moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when input hits an edge case (malformed budget, email-only subscriber, payer-covered member, DAILY budget, Budget Action).\n\n## Anti-Patterns — NEVER\n\n- NEVER classify an account with zero budgets as anything other than\n  NO_BUDGET. \"No budgets\" is a total spend blind spot — the highest-risk\n  FinOps posture. Do not soften it to CONFIG_GAP.\n\n- NEVER treat a budget with zero notifications as OK. A budget without\n  notifications is decorative — it tracks spend nobody watches. This is\n  NO_ALERT, not OK. The console showing a spend number is not alerting.\n\n- NEVER assume an SNS subscriber means alerts will deliver. The SNS topic\n  policy MUST explicitly grant `sns:Publish` to `budgets.amazonaws.com`. A\n  missing policy statement fails silently with zero console error — this is\n  the #1 reason budget alerts \"don't work.\" Always read the topic policy.\n\n- NEVER flag an RI_COVERAGE \u002F RI_UTILIZATION \u002F SP_COVERAGE \u002F SP_UTILIZATION\n  budget as cost-breached. These budget types measure reservation\n  effectiveness (a percentage), not spend. They have no dollar BudgetLimit.\n  Applying cost-breach logic to them is a false positive.\n\n- NEVER treat the absence of a Budget Action as a CONFIG_GAP. Budget Actions\n  (enforcement) are an opt-in tier separate from alerting. Most accounts use\n  alert-only budgets by design. Only flag a misconfigured Action if one is\n  present.\n\n- NEVER assume \"actual under limit\" means the budget is safe. Cost-data lag\n  trails real spend by 8-14 hours. A budget at 90% actual may already be over.\n  Always check the FORECASTED spend against the limit, not just actual.\n\n- NEVER recommend a single-threshold budget as adequate. A lone 100% ACTUAL\n  alert fires after the spend is incurred plus the data lag. A budget needs at\n  least an early-warning tier (50%) and an action tier (80-90%) below the\n  breach alert (100%).\n\n- NEVER treat a CloudWatch billing alarm as a substitute for a budget.\n  Billing alarms (`AWS\u002FBilling EstimatedCharges`) are account-total only,\n  update every ~6 hours, and have no FORECASTED projection or filtering. They\n  are legacy defense-in-depth, not a replacement for AWS Budgets.\n\n- NEVER skip pagination on `describe-budgets` or\n  `describe-notifications-for-budget`. The long tail of budgets (beyond page\n  one) is where stale, decorative, and breached budgets hide. Always drain\n  `NextToken` to completion.\n\n- NEVER conflate FORECASTED and ACTUAL notification types. FORECASTED projects\n  month-end spend; ACTUAL reports current calculated spend. They are not\n  interchangeable. A budget with only ACTUAL notifications is reactive; a\n  budget with FORECASTED notifications is predictive. Both belong in a mature\n  budget config.\n\n- NEVER assume a payer-wide budget covers a member account's alerting needs.\n  A payer budget with no `LinkedAccount` filter aggregates all member spend\n  but a runaway member account can hide inside an aggregate that is under\n  limit. For chargeback and isolation, member accounts need their own budgets\n  or the payer budget must be filtered per account.\n\n- NEVER propose more than 11 notifications on a single budget. The quota is\n  11 notifications per budget (hard limit). A remediation proposing a 12th\n  notification will fail with `LimitExceededException`. Count existing\n  notifications before adding.\n\n- NEVER ignore the `CostTypes` filter when assessing breach. A budget with\n  `IncludeTax: false` under-reports by the tax line. Two budgets with the same\n  limit and different `CostTypes` are not comparable. Confirm the filter\n  matches intent before flagging a breach.\n\n## Pre-flight safety checks (run before any remediation CLI)\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation\n  (CreateBudget, CreateNotification, CreateSubscriber, DeleteNotification,\n  SetTopicAttributes on an SNS policy, PutBudgetAction), the auditor MUST\n  emit: `CONFIRM: About to \u003Caction> on budget \u003Cname> in account \u003Caccount>.\n  This affects \u003Cconsequence>. Proceed? (yes\u002Fno)` Do NOT execute the CLI\n  command until the operator confirms. Budgets changes can suppress or\n  duplicate live alerting.\n- Confirm the caller identity has `budgets:Create*` and `sns:SetTopicAttributes`\n  if remediation is intended — most read-only auditor roles CANNOT, and\n  remediation commands will fail with `AccessDenied`. Surface this BEFORE the\n  operator approves.\n- Before modifying an SNS topic policy, capture the current policy for\n  rollback: `aws sns get-topic-attributes --topic-arn \u003Carn> --region us-east-1\n  > \u002Ftmp\u002F\u003Ctopic>-policy-backup-$(date +%s).json`. SNS topic policies are not\n  versioned — a bad policy statement can break ALL topic publishers, not just\n  Budgets.\n- Prefer additive changes (add a notification, add a topic-policy statement)\n  over destructive changes (delete a notification, replace a policy). Additive\n  changes are reversible and cannot break existing delivery.\n- Before creating a zero-spend budget on a new account, confirm the account\n  has no expected spend (a zero-spend budget with legitimate ongoing spend\n  generates constant false-positive alerts). For sandbox accounts with small\n  expected spend, use a $1 or $5 guardrail, not $0.01.\n\n## Remediation guidance\n\n**Ordering principle:** always prefer additive changes. Add a notification\nbefore deleting one; add a topic-policy statement before rewriting the policy.\nThis prevents a window where no alerting is in effect.\n\n### For NO_BUDGET — account has zero budgets\n\n1. Create a total-account MONTHLY cost budget at the operator's expected\n   monthly spend:\n   `aws budgets create-budget --account-id \u003Cid> --budget file:\u002F\u002Ftotal.json\n   --notifications-with-subscribers file:\u002F\u002Fsubs.json --region us-east-1`\n2. Add at minimum: ACTUAL 50%, FORECASTED 80%, ACTUAL 100% notifications wired\n   to an SNS topic (with the budgets principal in its policy) or an email.\n3. For new\u002Fsandbox accounts, additionally create a zero-spend guardrail\n   (Step 7).\n4. For Organizations\u002Fconsolidated-billing, create a payer-level budget AND per-\n   member budgets (or filtered payer budgets) for chargeback visibility.\n\n### For NO_ALERT — budget has zero functional notifications\n\n1. Create notifications: `aws budgets create-notification --account-id \u003Cid>\n   --budget-name \u003Cname> --notification \u003Cjson> --subscribers \u003Cjson>\n   --region us-east-1`.\n2. Minimum set for a MONTHLY COST budget: ACTUAL 50% (awareness), FORECASTED\n   80% (action), ACTUAL 100% (breach). Wire each to an SNS topic or email.\n3. Confirm the SNS topic policy grants `budgets.amazonaws.com` publish (see\n   CONFIG_GAP \u002F SNS policy remediation).\n\n### For CONFIG_GAP — SNS topic policy missing budgets principal (Step 3)\n\n1. Retrieve the current policy: `aws sns get-topic-attributes --topic-arn \u003Carn>\n   --region us-east-1 --query 'Attributes.Policy' --output text`.\n2. Add (do not replace) a statement granting the budgets principal publish:\n   ```bash\n   aws sns set-topic-attributes --topic-arn \u003Carn> --region us-east-1 \\\n     --attribute-name Policy --attribute-value '\u003Cupdated-policy-json-with-budgets-statement>'\n   ```\n3. Verify delivery by triggering a test budget notification or waiting for the\n   next threshold crossing and checking CloudTrail for a `Publish` event from\n   `budgets.amazonaws.com`.\n\n### For CONFIG_GAP — single threshold \u002F no early warning (Step 4)\n\n1. Add a 50% ACTUAL notification (awareness) and an 80-90% ACTUAL or\n   FORECASTED notification (action tier) via `create-notification`.\n2. Keep the existing 100% notification as the breach tier. Do NOT delete it.\n3. Confirm total notifications do not exceed 11 per budget.\n\n### For CONFIG_GAP — no FORECASTED notification (Step 5)\n\n1. Add a FORECASTED notification at 80% and\u002For 100% via\n   `create-notification --notification ... --notification-type FORECASTED`.\n2. This provides lead time that ACTUAL-only alerts cannot, given cost-data\n   lag.\n\n### For CONFIG_GAP — zero-spend guardrail missing (Step 7)\n\n1. Create a COST budget with `BudgetLimit.Amount: 0.01` (or `1.00` for sandbox\n   with tiny expected spend), `TimeUnit: MONTHLY`, and an ACTUAL 100%\n   notification wired to an SNS topic or email.\n2. Name it distinctly (e.g., `zero-spend-guardrail`) so it is recognizable in\n   audits.\n\n### For OK\n\n1. No remediation required for current posture.\n2. Recommend verifying the SNS topic policy quarterly — policy drift from\n   other tooling can silently remove the budgets principal.\n3. Recommend confirming email subscribers are still valid (personnel churn).\n4. For Organizations, verify member accounts have independent alerting, not\n   just payer-level coverage.\n\n## Deep reference: AWS Budgets internals\n\nInternals deep dive (notification delivery pipeline, cost data lag, quotas) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when explaining why a verdict fired or planning notification changes.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand to check 2024-2026 Budgets feature coverage.\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step 0 expert knowledge, edge-case catalog, Budgets internals deep dive, 2024-2026 features.\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pagination sweep and pre-flight permission\u002Fpayer\u002Fhistory checks.\n\n## Domain\n\nAWS CloudOps \u002F FinOps Cost Control & Spend Visibility.\n\n## AWS documentation\n\n- **AWS Budgets User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fbudgets-managing-costs.html\n- **Security in AWS Cost Management** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fsecurity.html\n- **AWS Budgets API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Faws-cost-management\u002Flatest\u002FAPIReference\u002FAPI_Operations_AWS_Budgets.html\n- **AWS Budgets CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fbudgets\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":39},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"complexity":32,"entry_point":33,"when_to_use":34,"requires_llm":35,"verdict_shape":36,"invocation_schema":37,"supports_pipeline":35,"activation_triggers":38},"budgets, finops, cost-control, alerting, sns, spend, audit","2","Jacky Chan — AWS Community Builder","aws-cloudops","FinOps","0.1.0","AWS Budgets, cost budget, budget alert, notification threshold, FORECASTED, ACTUAL, SNS topic policy, budgets.amazonaws.com, zero-spend budget, cost overrun, FinOps, billing alarm, cost control, spend posture, budget action, RI coverage, Consolidated Billing, budget audit, threshold gap","medium","false","Reviewing cost budgets before a billing review or production cutover, checking that budget alerts are wired to a real SNS topic, validating threshold coverage (early-warning vs over-budget), auditing actual-vs- forecast breach posture, or hardening spend controls for a new or sandbox account.","true","NO_BUDGET | NO_ALERT | CONFIG_GAP | OK","Input: either (a) an account budget inventory (list of budgets, each with notifications, subscribers, SNS topic policies, and calculated spend), OR (b) an account-id for live-account audit. Output: deterministic BUDGET\u002FVERDICT\u002FREASON\u002FFINDINGS\u002FREMEDIATION block per budget plus an account-level aggregate verdict, where VERDICT is one of NO_BUDGET, NO_ALERT, CONFIG_GAP, OK.","audit my AWS budgets, check budget alerts, is my budget wired to SNS, budget notification threshold, zero-spend budget, cost overrun alert, budget forecast exceeded, spend posture audit, budget SNS policy, decorative budget","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline budget-document classification. Live-account audits use aws budgets describe-budget, aws budgets describe-budgets, aws budgets describe-notifications-for-budget, aws budgets describe-subscribers-for-notification, and aws sns get-topic-attributes (AWS CLI v2, SSO or key-based credentials).","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fbudgets-auditor",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill budgets-auditor",{"tool":54,"command":55},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill budgets-auditor",{"tool":57,"command":58},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill budgets-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002FSKILL.md",true,[62,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",13639,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Feval\u002Ftest-cases.yaml",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"evals\u002Fbaselines\u002Fbudget-without-notifications.md",545,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fbudget-without-notifications.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"evals\u002Fbaselines\u002Fnew-account-no-zero-spend.md",503,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fnew-account-no-zero-spend.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"evals\u002Fbaselines\u002Fno-budgets-account.md",677,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fno-budgets-account.md",{"path":81,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":82,"sourceHtmlUrl":83},"evals\u002Fbaselines\u002Fsingle-threshold-actual-only.md",601,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fsingle-threshold-actual-only.md",{"path":85,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":86,"sourceHtmlUrl":87},"evals\u002Fbaselines\u002Fsns-policy-missing.md",593,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fsns-policy-missing.md",{"path":89,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":90,"sourceHtmlUrl":91},"evals\u002Fbaselines\u002Fwell-configured-with-zero-spend.md",621,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fbaselines\u002Fwell-configured-with-zero-spend.md",{"path":93,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Feval_config.yaml",2037,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Feval_config.yaml",{"path":97,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":98,"sourceHtmlUrl":99},"evals\u002Fevals.json",5281,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fevals.json",{"path":101,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":102,"sourceHtmlUrl":103},"evals\u002Fprompts\u002Fbudget-without-notifications.md",1003,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fbudget-without-notifications.md",{"path":105,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":106,"sourceHtmlUrl":107},"evals\u002Fprompts\u002Fnew-account-no-zero-spend.md",2264,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fnew-account-no-zero-spend.md",{"path":109,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":110,"sourceHtmlUrl":111},"evals\u002Fprompts\u002Fno-budgets-account.md",590,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fno-budgets-account.md",{"path":113,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":114,"sourceHtmlUrl":115},"evals\u002Fprompts\u002Fsingle-threshold-actual-only.md",1759,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fsingle-threshold-actual-only.md",{"path":117,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":118,"sourceHtmlUrl":119},"evals\u002Fprompts\u002Fsns-policy-missing.md",1814,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fsns-policy-missing.md",{"path":121,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":122,"sourceHtmlUrl":123},"evals\u002Fprompts\u002Fwell-configured-with-zero-spend.md",3048,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fevals\u002Fprompts\u002Fwell-configured-with-zero-spend.md",{"path":125,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":126,"sourceHtmlUrl":127},"examples\u002Fend-to-end.md",6910,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fexamples\u002Fend-to-end.md",{"path":129,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fadvanced-patterns.md",10328,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Freferences\u002Fadvanced-patterns.md",{"path":133,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fdiagnostic-commands.md",1689,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Freferences\u002Fdiagnostic-commands.md",{"path":137,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":138,"sourceHtmlUrl":139},"skill.usf.yaml",4216,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbudgets-auditor\u002Fskill.usf.yaml",[141,148,155,162,169,176],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]