Skip to content

How to transfer AWS account ownership to a buyer

Indiemaker · Updated 17 November 2026

In short

An AWS account is controlled by its root user, so a handover means changing the root user's email and password to the buyer's. Before that, the AWS Customer Agreement says you may not assign or transfer the agreement without AWS's prior written consent, so ask AWS Support first. The alternative is migrating the workload into the buyer's own account.

Can you transfer AWS account ownership to another person or company?

You can, but it is two jobs, and the legal one comes first. If you are working out how to transfer AWS account ownership in a sale, separate them:

  1. Permission. The AWS Customer Agreement, section 11.1, says the customer will not assign or otherwise transfer the agreement, or any rights and obligations under it, without AWS's prior written consent, and that an assignment in breach of that section is void.
  2. Mechanics. The account is controlled by its root user, which is identified by an email address. Handing over the account means the root user email, password and sign-in security become the buyer's.

Doing the second without the first leaves the buyer running a business on an account that is, on paper, still the seller's contract.

How do you get AWS's consent?

Ask AWS, and get the answer in writing before closing. AWS's knowledge centre has an article on transferring an account to another party (repost.aws/knowledge-center/transfer-aws-account). Read the current version, then contact AWS Support if anything about your deal is unclear.

Whether the account can be assigned as part of your particular sale is a contract question, so have whoever is drafting the asset purchase agreement read section 11.1 as well.

One case needs none of this. In a share sale the company that holds the AWS agreement does not change, only its owners do. The new owners still need to take control of the root user, but they are not assigning the contract to anyone.

How do you change the root user on a standalone account?

AWS documents this as "Update the root user email address". For a standalone account, or the management account of an organisation, it has to be done by the root user. AWS states that you cannot do these steps as an IAM user or role, and that the task is not available through the AWS CLI or SDKs.

  1. Sign in to the AWS Management Console as the root user, with the account's email address and password.
  2. In the upper right corner, choose the account name or number, then choose Account.
  3. On the Account page, next to Account details, choose Actions, then Update email address and password.
  4. On the Account Details page, next to Email address, choose Edit.
  5. Enter the new email address twice and confirm the current password, then choose Save and continue. AWS sends a verification code to the new address.
  6. Enter the code under Verification code and choose Confirm updates.

AWS says the code can take up to 5 minutes to arrive, and that changes to an account can take up to four hours to propagate everywhere.

In a sale the new address should be one the buyer controls and intends to keep, ideally a role mailbox on the business's own domain and not one person's inbox. Once the email is the buyer's, the buyer sets a new root password themselves. A password the seller chose and read out is not a handover.

What if the account is part of an AWS organisation?

Then check where it sits before you plan anything. AWS's documentation says that for a member account in an organisation, a user in the management account or a delegated admin account can update that member's root user email centrally from the AWS Organizations console, or through the CLI and SDKs. The new address gets a one-time password, and the update can be completed within 24 hours of the code being sent.

For a buyer, that cuts both ways. It is a second way to make the change, but while the account stays inside the seller's organisation, someone on the seller's side can still change its root email. An account being sold should end up outside the seller's organisation. Settle how it leaves with AWS Support, along with consent.

What does not change when the root user changes?

Changing the root email swaps the lock on the front door. Everything inside the account stays exactly as the seller left it, including the ways the seller could still get in. The buyer's first hours in the account are an audit:

  • Every IAM user, role and access key. Remove or rotate each one, including keys that deployment tools and CI pipelines use.
  • Any multi-factor device on the root sign-in and on admin users. Replace the seller's with the buyer's.
  • The contact details and payment method on the account, so invoices and security notices reach the buyer.
  • Trust relationships that let other AWS accounts in, and anything shared out to accounts the buyer does not own.
  • Commitments the seller made on the account, such as reserved capacity, which carry on billing to whoever now pays.

Agree in the contract who pays the bill for the month of closing.

When is migrating to a new AWS account the better route?

Often. Our guide to taking over hosting, domains and payments puts it as a choice: either the account itself changes hands, or you migrate into a new one. Migrating fits when:

  • The seller's account also runs other projects they are keeping.
  • The account has years of users, keys and one-off resources nobody can fully explain, which is a form of technical debt.
  • The buyer already has an AWS organisation with its own security rules and wants the product inside it from day one.

The cost is work. The buyer opens their own account, rebuilds the infrastructure, moves the data and cuts traffic over, with the seller on hand and a tested rollback. Either way, list every resource in a stack transfer checklist first.

What should you do before and after in a business sale?

Before. Decide between handover and migration during diligence. Get AWS's position on consent in writing. Take backups the buyer can restore from without the seller.

During. Do it inside escrow. On Indiemaker, payment and handover run through Escrow.com, and the buyer's money is held until the transfer is done. The buyer confirms the AWS line by signing in as the root user on their own device, with their own email and their own second factor, and by deploying once from their own credentials.

After. Rotate every secret, as set out in how to hand over a software business. Check the next invoice lands with the buyer. Keep the seller reachable through the first full billing month, when a forgotten resource or undocumented scheduled job tends to surface.

Sources

Related: how-to-take-over-hosting-domains-and-payments, stack-transfer, how-to-hand-over-a-saas-business, technical-debt

When you are ready to read real listings.

Everything on sale, on the same fields, from $1,000 to $500,000.