1 Answer
- Newest
- Most votes
- Most comments
0
If you've mistakenly removed your virtual MFA from your authenticator app but still need it to log in to your AWS account, you have a few options:
For root user accounts:
- Look for the "Sign in using alternative factors of authentication" option during the login process. This allows you to verify your identity using other methods like email verification followed by a phone call.
- When using this alternative authentication method, you'll need to verify your email address and then receive a call from AWS. When prompted, enter the 6-digit number shown on the AWS website on your phone keypad.
- After successful verification, you'll be able to sign in to your account.
- Once logged in, go to the AWS Security Credentials page and delete the old MFA virtual device entity before creating a new one.
If you're an IAM user:
- You'll need to contact your AWS administrator within your organization. They can help deactivate your MFA device and set up a new one.
- Note that the "Sign in using alternative factors of authentication" option is typically only available for root user accounts, not IAM users.
If the alternative authentication methods aren't working:
- Ensure your phone number is correct and can receive calls.
- If you still can't access your account, you'll need to contact AWS Support directly through their account recovery form.
- Be prepared to verify your identity with information such as the email address associated with the account and the account ID.
For future reference, consider registering multiple MFA devices to prevent lockouts in similar situations.
Sources
Account login when MFA and alternatives are unavailable | AWS re:Post
MFA Register Problem Cannot Signin | AWS re:Post
I am unable to log in to my account. | AWS re:Post
locked out of account | AWS re:Post
Recover an MFA protected identity in IAM - AWS Identity and Access Management
Relevant content
- asked 3 months ago
- asked 2 years ago
- asked 2 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 months ago
