- Newest
- Most votes
- Most comments
When an AWS account is suspended due to non-payment, making the payment is the first step, but it doesn't automatically reactivate the account. Account reactivation requires manual intervention from the AWS Support team, which can take time.
Here are some recommendations for your situation:
-
Ensure your support case was opened under the "Account and billing" category, which is available even for suspended accounts.
-
In your support case, clearly provide any payment confirmation details or transaction IDs to help AWS verify your payment.
-
Check all email addresses associated with your AWS account, including spam folders, for any communications from AWS that might require additional information or verification.
-
Make sure all your contact information in the AWS account is up-to-date so AWS can reach you if needed.
-
Update your existing support case to emphasize any business impact and critical nature of your services being affected, which might help prioritize your case.
While waiting periods can be frustrating, continuing to engage with AWS Support through your open case is still the primary channel for resolving this issue. Response times can vary, with some customers reporting waiting periods of several days. Be persistent but patient, and don't hesitate to request updates if you haven't received a response within a reasonable timeframe.
For future reference, to avoid similar situations, it's advisable to keep payment methods up to date and closely monitor billing notifications.
answered 10 months ago
I understand the urgency to reinstate your account.
As our internal teams answer cases using an ordered queue, response times can vary based on complexity of the issue and current support case volume. I've reached out to our internal Support team to share the information you provided and to convey the urgency.
To seek further updates and to ask questions, you can continue to use your case thread.
- Randi S.
Relevant content
asked 15 days ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 8 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
