A municipality’s sandbox accounts for students and vendors regularly overspend. Leadership wants notifications and the option to apply spend controls when budgets are exceeded. Which design best fits org cost governance?
Select an answer to reveal the explanation.
Short Explanation
Sandboxes are where curiosity meets the credit card. Budgets with actions yell early and can slam the brakes—notify first, then optionally clamp the account—without shutting down every lab by default.
Full Explanation
AWS Budgets can alert on forecasted or actual spend and, with budget actions, apply policy responses such as IAM or SCP-related controls in governed accounts. That pattern fits multi-account sandbox governance. Deleting accounts after each login is operationally impractical. Sandbox spend still bills the payer. Collapsing sandboxes into the management account worsens blast radius and governance clarity.