A suspended or closed AWS account takes every workload in it offline at once, and recovery runs through support cases, not engineering. The usual causes (failed payments, a compromised account, abuse reports, unanswered verification requests), how reopening works within 90 days of closure, and the setup that keeps production recoverable when it happens to you.
Every few weeks someone posts that their AWS account was suspended or closed and production is down. The cause is rarely mysterious once it is found, but finding it takes days when the only contact is a support case and the email that would have warned you went to an inbox nobody reads.
Open a case with AWS Support under Account and billing. That category is available on every support plan, including the free one.
Check the root user's email and every alternate contact for messages from AWS in the last 30 days.
A closed account can be reopened during the 90 days after closure; after that it and its data are permanently deleted.
If customers are affected, restore from backups held outside the account (see below) while the case runs, rather than waiting on it.
Root user email on a distribution list at a domain you control and renew, with MFA on the root user.
Billing, operations and security alternate contacts set on every account, to shared mailboxes.
Production in its own account inside AWS Organizations, separate from experiments and from the management account.
Backups copied to a separate account, ideally a logically air-gapped AWS Backup vault, and the most important data also outside AWS.
DNS and the domain registrar outside the production account, so you can point traffic elsewhere.
Infrastructure as code that can rebuild the system in a fresh account, tested at least once.
A support plan that matches the cost of a day offline.
We'll review your accounts, contacts and backups with you and close the gaps. 30 minutes, free.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
AWS Spend Limits: The Limitations, and What to Do About Each
Spend limits only work on projects created through the new AWS signup experience, can't cover an existing account or an organization, can't spare production while stopping the rest, and pause everything at once. Each limitation, what it means in practice, and the workaround until AWS extends the feature.
Read
Building Your Own Spend Cap on an Existing AWS Account: Budget Actions, Service Control Policies and Quotas
Spend limits don't cover existing AWS accounts yet. You can build most of the same protection today: budget actions that apply a deny policy or stop instances at a threshold, service control policies that keep accounts away from the most expensive services, lower quotas, and anomaly alerts. The setup, in order, and the gaps it leaves.
Read
As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.