- Newest
- Most votes
- Most comments
Hello,
Please note that AWS Accounts that were created before August 10, 2017, are usually coupled with an Amazon.com account, meaning that they share the same "root" account email and login credentials.
As of now, we do not have an option to separate AWS Accounts from their Amazon.com account, but we know that this has been an inconvenience for our customers, so we're working to have coupled accounts separated. As this project is still on the works, we cannot share more details or a specific date for the rollout until we're closer to it being completed. We appreciate your understanding on this.
On deep diving further with the service team, they have confirmed that currently we can only decouple an account if a customer is willing to lose their Amazon.com/retail account. In such a case scenario, a customer can open up a support ticket with our Accounts and Billing team to submit a request for the same. However, if customer needs to retain both AWS and Retail accounts, then the solution is being worked on at the given time as mentioned before.
As a workaround, we recommend creating a new a AWS account and migrate all of the resources to the new account.
https://aws.amazon.com/blogs/architecture/migrate-resources-between-aws-accounts/
Is this migration effort still the only workaround that will preserve the Amazon retail account? In my case, the AWS account was created in late 2021 but it too appears as linked (same email address, password), How does one confirm their late-2021 account is actually linked to a retain account? Thanks.
Relevant content
- Accepted Answerasked 4 months ago
- Accepted Answerasked 3 months ago
- asked 6 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
What do you mean by "this would impact the amazon.com email-address"? You should be able to log in to the AWS account as the root user, follow the documentation you linked to change the root email address, and then continue to use the prior address for Amazon.com retail while using the new address for AWS. What's the problem?