- Mais recentes
- Mais votos
- Mais comentários
You should not need root level access to address the issues with these instances. Two alternative paths I can suggest would be to identify someone who has administrator or elevated access to help you troubleshoot the problem with the SQL instances. Or someone who has access to manage IAM permissions to provide you the access you need.
If you have access to the root email address, or can get access to the root email address that can help with being able to move forward in getting past the MFA issues in the root that we outline in our documentation.
Hey Tom,
Looks like you're in a position where you cannot follow the MFA reset steps (which requires access to the phone number that the account was configured with). This means that you're going to have to raise a support case and go through the process of proving account ownership. You should ideally start this from the account in question, if you have access to the support APIs. However, if you cannot raise a support case from the account in question, you can start the process from another AWS account - just bear in mind that there will be additional checks to prove ownership.
Once the MFA is removed, you can go through the password reset wizard. This will require access to the mailbox of the ex-employee, but that should be easy to access on your end, or recreate if needed.
Hopefully that puts you in a better position going forward. The next place to go is Customer Support via a support case.
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
This does not really address the situation posed, but I will accept it because finding credentials for a elevated account is what we were finally able to do to recover. As mentioned, the problem was no accounts with elevated access and there is no root access. This account was acquired many years ago and handover of credentials during IT attrition had been missed.