A company must enforce strict quarterly budget limits across 25 AWS-hosted applications. Separate teams are accountable for storage, compute, and database costs. The SysOps administrator needs an automated way to notify each team when their forecasted spend will exceed the quarterly limit set by finance. The solution must not introduce extra compute, storage, or database charges. Which option satisfies these constraints?

Creating AWS Budgets per team, filtered by the services each team owns, directly addresses the requirements. AWS Budgets allows setting forecast thresholds and sending notifications via email or SNS when these thresholds are breached, fulfilling the need for automated notifications without incurring additional compute, storage, or database charges. This approach also enables granular tracking for each team's specific responsibilities (storage, compute, database). The other options involve custom solutions using Lambda, EventBridge, or SQS, which introduce additional costs and complexity for development and maintenance. A single AWS Budget for all services would not allow for team-specific accountability and notifications.