Our AWS account was suddenly suspended after more than two years of normal use. The notice says the account was closed because AWS believes it is related to other previously closed accounts. Unfortunately, the account hosts our core billing and delivery ERP, so daily operations are currently blocked. Support told us the matter was referred to the internal Program Support/Trust and Safety verification team, which communicates through written support channels. We have offered to provide identity verification, business registration, tax information, billing records, and other documentation, but we are still waiting for an update. Has anyone successfully appealed this type of suspension? What information helped establish that the business and account are legitimate? Is there any way to request temporary, restricted access just to export backups or recover the database while the review is pending?
3 Answers
There generally is no guaranteed emergency read-only window while an account is under a trust or verification review. Ask explicitly whether AWS can provide supervised access for data recovery, but plan as though the answer may be no. Once access is restored, put regular exports, independent backups, tested restores, and a disaster-recovery environment outside a single provider’s account boundary in place.
A suspension for being associated with a previously closed account can involve shared owners, payment details, addresses, domains, devices, or other account signals. A long history of successful use does not necessarily override that automated association. Give a concise timeline of the business and account ownership, explain any legitimate relationship to other accounts, and directly address anything that might look duplicated or connected.
Keep replying through the existing support cases and clearly explain the operational impact, but avoid opening a large number of duplicate cases because that can slow down review. Provide consistent company details, ownership information, billing records, registration documents, tax identifiers, and proof that the account is controlled by the legitimate business. The verification team—not regular technical support—usually has to make the final decision.
Multi-cloud by itself is not a complete solution, since it adds operational complexity. The immediate lesson is to maintain tested backups and a recovery plan, alongside an appropriate paid support plan and documented escalation process.