A municipal budget office needs alerts when a department’s AWS forecast will exceed its monthly appropriation before month-end, not only after the invoice arrives. Which design best implements billing alarms aligned to expected usage patterns?
Select an answer to reveal the explanation.
Short Explanation
Budgets with forecast alerts are the early-warning siren for a department burning cash mid-month. You want the page before the invoice, scoped by tag or cost category. Flow Logs and blanket RunInstances denials are not a FinOps forecast.
Full Explanation
AWS Budgets supports actual and forecasted cost alerts scoped by account, cost category, or tags so departments learn mid-month when they are on track to exceed appropriation. Waiting for the consolidated invoice is too late for course correction. VPC Flow Log analytics do not replace cost forecasting, and SCPs that blanket-deny compute when over budget are operationally hazardous compared with alerting and governance workflows.