Who should own the AWS account: my brand or my developer?

Why your brand must own its AWS account, domain and code, how to give developers safe access, and how to take back an account you do not control.

Anadoris Digital · · 4 min read

Keys
Photo: Hans / Pixabay (CC0)

Many small brands discover, often during a dispute or after a freelancer moves on, that their cloud account, domain or code repository is registered to someone else. Getting it back can take weeks, and in the meantime you cannot change anything. It is one of the most avoidable risks in running a D2C business.

The fix is not about trust. Good developers prefer clear ownership because it protects them too. It is about setting up accounts the right way from the first day.

What 'owning the account' actually means

  • The root user email is a company address, ideally a shared one such as cloud@yourbrand.in, not a personal inbox.
  • The payment card or invoice billing is in the company's name.
  • A founder or director holds the root password and its multi-factor device.
  • The account's contact details and alternate contacts point to the company.
  • Invoices and tax details show the company, so costs are claimable and traceable.

How to give developers safe access

Nobody, including founders, should use the root login for daily work. Instead, create named users or single sign-on access through AWS IAM Identity Center, one per person, each with only the permissions their work needs. Agencies get their own access that you can switch off without affecting anyone else.

  • One login per person, never a shared 'developer' login.
  • Multi-factor authentication required on every human login.
  • Admin rights only for the few people who genuinely need them.
  • Access reviewed when a person or vendor leaves, the same day.
  • Automated systems use roles with narrow permissions, not a person's keys.

Keep one break-glass admin login, protected by multi-factor authentication and stored securely by a founder, for emergencies when single sign-on or a vendor is unavailable. Test once a year that it still works, so you are not discovering a lost password in the middle of an incident.

Ownership beyond AWS

The same rule applies to everything your systems depend on. A cloud account you own is of little use if the domain, DNS or code sits elsewhere.

  • Domain registrar account in the company's name.
  • DNS provider, which may be Route 53 or your registrar.
  • Code repositories under a company organisation on GitHub, GitLab or similar.
  • Email sending services, payment gateways and courier accounts.
  • Third-party API keys, registered to company emails.

If someone else already owns your account

Ask calmly and in writing for the root email to be changed to a company address and for billing to move to your card. A cooperative developer can do this in minutes. If the account cannot be transferred, plan a move to a new company-owned account, copying data and redeploying, rather than waiting. Keep records of what you paid for, as they help if you need AWS support's help to prove ownership.

Never share the root password over chat or email. If it has been shared in the past, change it and reset the multi-factor device once you have control.

Using AWS Organizations as you grow

Once you have more than one environment, such as production and staging, consider AWS Organizations. The brand owns a management account that holds billing and policies, and separate member accounts hold production, staging or a particular project. This keeps a mistake in a test account from touching live data, and lets you give an agency access to one account without exposing the rest.

Keep the management account almost empty and locked down. It should hold billing, consolidated cost reports and organisation-wide guardrails, not running apps. Only founders or a trusted finance or technology lead should be able to log in to it.

Keeping a record of access

Pay attention to anything that grants access without a person attached: access keys created for scripts, tokens issued to third-party tools and roles that outside accounts can assume. These tend to outlive the people who created them. List them in the same register, note what each is for, and remove any that nobody can explain.

Ownership is not a one-time task. People join and leave, agencies change and new tools get connected. A simple access register, kept as a shared document, lists every account the business depends on, who owns it, who has access, how they log in and when access was last reviewed. Reviewing it once a quarter, and on the day anyone leaves, catches most problems before they become expensive.

Where to start

Today, log in to your AWS billing page and check whose email and card are on it. Then check your domain registrar and code repositories the same way. For anything not in the company's name, start the transfer this week. Finally, write a one-page access list showing who has access to what, and keep it with your other company records.

Anadoris Digital sets up client accounts this way by default, with the brand holding root access and every handover documented.

Related service: AWS & Cloud Management · More on this topic: AWS & Cloud Management articles

Common questions

Can my agency create the AWS account for me?

They can help, but it should be created with your company email and billed to your company. Many agencies use AWS Organizations to manage several clients; if so, ask how you can take your account out of their organisation and get full root control if you part ways.

What is the AWS root user?

It is the original login created with the account email. It has unrestricted power, including closing the account and changing billing. It should be protected with a strong password and multi-factor device, held by the company, and used only for rare account-level tasks.

How do I remove a developer's access when they leave?

Disable or delete their named user or single sign-on access, remove any access keys they created, and rotate any shared secrets they could have seen, such as API keys and database passwords. Then check recent activity in AWS CloudTrail for anything unexpected.

Is it rude to ask a freelancer to hand over ownership?

No. Clear ownership is standard practice and protects both sides. Frame it as a company policy: the business owns its accounts, and contractors get named access. Most professionals will expect this and may already have a checklist for it.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project