The resolution doesn't work for me. Can't even proceed with #1 (Sign in to your AWS account as the root user).
It says "There was an error An AWS account with that sign-in information does not exist. Try again or create a new account." But when trying to create a new account, the email says the account exists...
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
With AWS organizations you can now create a new AWS account without ever having to create a "root" user in the new account. The only way to we allow folks into new account is via switch-role to OrganizationAccountAccessRole. So if an account is created in this manner and then closed, there is no "root" user. How does one then get the account re-opened? Can we open a support case from the Org/Mgmt account to do this? If so you need to update the instructions to reflect this. Thanks
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
repost.aws/knowledge-center/reopen-aws-account#COPyQZsKo5T82GVjXGnB7KfQ
The resolution doesn't work for me. Can't even proceed with #1 (Sign in to your AWS account as the root user).
It says "There was an error An AWS account with that sign-in information does not exist. Try again or create a new account." But when trying to create a new account, the email says the account exists...
I have this same issue
Hello,
We are facing the same issue, and we would like to re-open the account. Thank you in advance
The resolution doesn't work for me. Can't even proceed with #1 (Sign in to your AWS account as the root user).
It says "There was an error An AWS account with that sign-in information does not exist. Try again or create a new account." But when trying to create a new account, the email says the account exists...
I have this same issue
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
aws is not working properly anymore. I just created an account directly on suspension, there is no access to AWS, I swear, AWS will no longer have users and will switch to another platform.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Clearly, this is a policy issue because AWS defines it as a permanent account closure. I would make a request for them to reconsider opening accounts that have been permanently closed, provided they meet certain reopening requirements such as a history of good payment behavior and the possibility of reopening after a couple of years (not a mockery of 5 to 10 years). On the other hand, responding to this resolution: 'NO, I do not agree to open another unnecessary email just to register.' In my particular case, I remember trying AWS, which I must admit is quite extensive, and I found it overwhelming to understand how to control expenses. I always paid, and it wasn't much, but I became concerned about the possibility of an accidental charge for requesting something without knowledge or a clear understanding of its costs. Probably for that reason, I closed it, hoping to reopen it in the future. However, not allowing the reopening of an account after some time, as if it were a permanent punishment, seems wrong and unnecessary. It also means losing potential opportunities for AWS to generate income. Regards.
Hello, Sebastian,
Please bear in mind, that the 90 day deletion policy is mainly a security measure to keep AWS servers from being overloaded with new and active accounts, not to mention to avoid extremely old accounts from being reopened by bad actors for abuse and also to protect user information. Please remember that the 90 day post closure period is given as a warning when closing an account, making this an user responsibility, and this is also available to read in AWS documentation below:
https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-closing.html
To avoid closing an account without incurring charges, you can keep an account active and protected with the tools AWS offers:
Budgets: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/budgets-managing-costs.html
Cloudtrail: https://aws.amazon.com/cloudtrail/getting-started/
Cloudwatch: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html
Cost Anomaly Detection: https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/
A really useful work around when closing an account and being able to keep an email for the future, would be changing the email to a 'dummy email' before closing the account, this will release the email for future usage.
We appreciate your understanding.
Do you have data to support the "bad actor" for "extremely old accounts"? Do not use assumptions as an excuse. If AWS really deleted or destroyed the data related to the email after 90 days, then this email address should be fully released. Voluntarily close account doesn't mean permanent.
good this good i like program aws thanks very muchthis is aws i like thanks very much
aws support good i like thanks very much
Good i like thanks very much
Contenido relevante
- preguntada hace 21 días
- preguntada hace 13 días
- preguntada hace 22 días
- preguntada hace 9 días
- preguntada hace 2 meses
- ¿Cómo puedo resolver el error “Failed to start the job flow due to an internal error” en Amazon EMR?OFICIAL DE AWSActualizada hace 5 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 7 meses
- OFICIAL DE AWSActualizada hace 6 meses