Unable to create account
Hi Team,
I’m currently facing an issue while trying to create an AWS account using the same email ID as my AWS Builder ID. It appears that this email may have been associated with an AWS account in the past.
When I attempt to log in, it doesn’t recognize my credentials. However, when I try to create a new account, it prompts for a verification code, which suggests that an account may already exist with this email.
Could you please advise if it’s possible to create a new AWS account using the same email, or guide me on how to recover or reset the existing account?
Thanks in advance for your help.
Best regards, Sanjid Salam
- Tags
- Account Support
- Language
- English
- Newest
- Most votes
- Most comments
The Problem: Builder ID vs. AWS Account:
Your AWS Builder ID is a personal profile for training and specific tools (like CodeCatalyst). It is not the same as an AWS Root Account used for cloud resources (EC2, S3, etc.).
If „AWS says“ the email is "already in use" during account creation, a full AWS account was likely created with that email in the past.
1. Use the "Email Plus" Trick (Fastest)
If you use Gmail or Outlook, you can register a new account using an alias. AWS will treat it as a new email, but all correspondence will go to your current inbox:
- Use: yourname+aws@email.com instead of yourname@email.com.
2. Force a Root Password Reset
- Go to the AWS Console.
- Select Root User, enter your email, and click "Forgot password?".
Note: If you don't receive an email, the account might be in a "suspended" or "closed" state from years ago, which still blocks the email address.
3. Contact Support without Logging In
If you are stuck in a loop, use the AWS Support Contact Form -> https://support.aws.amazon.com/#/contacts/aws-account-support
- Select Account and Billing Support
- rightarrow Unable to log in.
- Ask them to verify if an old account is blocking your email.
To get started immediately, Option 1 is your best bet. It bypasses the "email already exists" error without needing to recover old credentials.
Based on your description, it sounds like there may already be an AWS account associated with your email address, even though you're unable to sign in with your current credentials. This is a common situation that can occur when an account was previously created but the sign-in details weren't retained.
Here are some steps to help resolve this:
If you're having trouble signing into an existing account, you should refer to troubleshooting guidance for sign-in issues. This can help you diagnose problems with authentication and potentially recover access to the account.
If you're uncertain about whether an account exists or need help with the account creation process, I recommend searching AWS re:Post for content related to your specific situation. Many users have encountered similar scenarios, and you may find helpful solutions there.
If you continue to experience difficulties after trying these resources, you should contact AWS Support directly. They can help you determine if an account exists with your email address and assist with either recovering that account or resolving any conflicts that prevent you from creating a new one.
Note that AWS Builder ID and AWS account credentials are separate authentication systems, so having a Builder ID with an email address doesn't automatically create or link to an AWS account with that same email.
Sources
Troubleshooting issues with AWS account creation - AWS Account Management
I’ve run into this a few times. Usually, the signup process hangs because of a browser conflict or a specific card restriction. Try these three things—they almost always fix it:
- Go Incognito: Open the signup page in a Private/Incognito window. AWS is super sensitive to old cookies or being logged into a regular Amazon retail account.
- Check the Card Type: If you're using a virtual or prepaid card (like Revolut or a 'gift' card), AWS often auto-rejects them for verification. A standard physical debit or credit card works best.
- Address Match: Make sure the billing address you typed matches your bank statement exactly. Even small typos can trigger their fraud filter.
If those don't work, don't keep trying or you might get a 24-hour lockout. Just hit up 'Account and Billing Support' it’s free even if you don't have a plan yet, and they can manually 'unstuck' the account for you.
Relevant content
- AWS OFFICIALUpdated 3 months ago
I have tried the above guide, but it's not working.