How do I secure admin access to my AWS account?
Practical steps for small D2C brands to secure AWS admin access: protect the root user, enforce MFA, use single sign-on and apply least privilege.
Anadoris Digital · · 4 min read

Most serious cloud incidents at small businesses start with access, not with sophisticated hacking: a password reused from a breached site, an access key pushed to a public repository, a former contractor who still has admin rights, or a shared login nobody changed. Once someone has admin access, they can delete data, run up huge bills or lock you out.
Securing access is the highest-value security work a small brand can do in AWS. It does not require specialist tools, just a clear set of habits applied consistently. Most of it can be done in an afternoon, and it protects everything else you build on the account, from order data to backups and billing.
Lock away the root user
The root user is the original login created with the account's email address. It can do anything, including closing the account. It should almost never be used. Protect it with a long, unique password and multi-factor authentication, ideally a hardware security key or passkey, and store recovery details securely with a founder or director.
- Use a company email address for the root user that is not anyone's personal inbox.
- Turn on MFA, registering more than one device if supported, so losing one does not lock you out.
- Delete any root access keys; the root user should never have them.
- Use root only for the few tasks that require it, such as some billing and account settings.
- Set up alerts for any root login, so you know immediately if it is used.
One login per person, with MFA
Everyone who works in AWS should have their own login. AWS IAM Identity Center is the recommended way: people sign in through one portal, receive short-lived credentials, and can be connected to your existing identity provider such as Google Workspace or Microsoft Entra ID. Require MFA for everyone. Never share logins between people, even within a small team, because shared logins make it impossible to know who did what or to remove one person's access cleanly.
Give only the access each person needs
Least privilege means each person or system gets the permissions their work requires and nothing more. In practice, small brands can start with a few roles and refine them over time.
- Administrator: for one or two trusted people, used only when needed.
- Developer: can deploy and manage specific apps, ideally limited to particular accounts or resources.
- Read-only: for reviewing settings and troubleshooting without making changes.
- Billing: for founders and finance to see costs without technical access.
- Vendor or agency: limited to the project they work on, with an end date.
Separate production from staging using different AWS accounts under AWS Organizations, so developers can have broad rights in staging and narrower rights in production.
Replace long-lived access keys
Access keys that never expire are a common source of breaches, because they end up in code, laptops, chat messages and old servers. Apps running on AWS should use IAM roles, which provide temporary credentials automatically. Deployment pipelines can use short-lived credentials through OpenID Connect integrations. If a key is truly necessary, limit its permissions, rotate it regularly and store it in a secrets manager.
Turn on the guardrails
- AWS CloudTrail in all regions, saved to a protected S3 bucket.
- Amazon GuardDuty to detect suspicious activity such as unusual logins or crypto mining.
- IAM Access Analyzer to find resources shared outside your account.
- AWS Security Hub or Trusted Advisor checks for common misconfigurations.
- Service control policies to block unused regions and protect security settings from being turned off.
Some of these services carry charges based on usage; check current AWS pricing. For most small accounts, the cost is modest compared with the protection they provide.
Review access regularly
Access tends to grow and rarely shrinks. People change roles, contractors finish projects and agencies are replaced, but their logins and permissions often remain. Schedule a short access review every quarter: list every person and system with access to each AWS account, confirm each one is still needed, and remove the rest. Review on the day anyone leaves, not at the next quarterly check.
IAM shows when each user, role and access key was last used, which makes reviews quicker. Anything unused for a long period is a strong candidate for removal. Keep a simple record of each review, with the date and what changed. It takes little time, and it shows partners, auditors or investors that access is controlled rather than assumed.
Where to start
Today, log in as root, confirm MFA is on, delete any root access keys and log out. This week, set up IAM Identity Center, create a login with MFA for each person, and remove any shared logins. Then review every user and access key in IAM, delete those for people who have left, and turn on GuardDuty and a CloudTrail trail covering all regions.
Related service: AWS & Cloud Management · More on this topic: AWS & Cloud Management articles
