Training / Certifications / AWS Cloud Practitioner / IAM Essentials: Root User, Users and Policies

AWS Cloud Practitioner (CLF-C02) · Lesson 10 of 26

IAM Essentials: Root User, Users and Policies

Explain why and how to protect the AWS account root user, recognize root-only tasks, and use IAM users, groups and policies (AWS managed, customer managed and inline) with least privilege, MFA, password policies and access auditing.

Domain 2: Security and Compliance (30%)Task 2.3About 6:06CaptionsStatic view for reduced motion
Lesson 10: IAM Essentials Illustrative example: the store and its staff are samples 1. The root userThe all-powerful identitycreated with the account,and how to lock it away2. Users, groups, policiesWho can do what, written asJSON policies, granted withleast privilege and MFADomain 2, Task 2.3: AWS access management capabilitiesAWS account root userCreated with the accountSigns in with the account'semail address and passwordComplete access to everythingWhy it needs protectingStolen root = the whole accountIt sees and changes billingIt can close the accountSo: lock it away, use it rarelyEveryday work belongs to an administrative user, not to rootChange root email, passwordor root access keys*Close or reopena standalone account*Restore permissions when theonly admin locked themselves outActivate IAM access to theBilling and Cost Management consoleRegister as a seller in theReserved Instance MarketplaceTurn on MFA deletefor an Amazon S3 bucketFix an S3 bucket or SQS queuepolicy that denies everyoneSign up forAWS GovCloud (US)* For standalone accounts. AWS Organizations can handle these centrally.Account name, contacts and Regions don't need root.Root credentialslocked awayProtecting the root userTurn on MFA for the root userDon't create root access keysUse a strong, unique passwordUse root only for root-only tasksCreate an admin user for daily workOrganizations: remove member root credentialsIAM usersIAM groupsPolicies attached to groupsAnadeveloperBenfinanceChloeadminDevelopersPolicyS3, Lambda accessBillingPolicycost reports, read-onlyAdminsPolicyfull IAM adminUsers inherit the permissions of every group they joinA user can be in several groups; groups can't contain other groups{"Effect": "Allow","Action": "s3:GetObject","Resource": "arn:aws:s3:::shop-images/*","Condition": { ... }}EffectAllow or DenyActionwhich API callsResourcewhich items (by ARN)Conditionoptional: when it appliesResult: read product images from one bucket, and nothing elseAWS managedWritten and updated by AWSExample: ReadOnlyAccessQuick, but often broadCustomer managedWritten by youReuse on many users, groupsPrecise least privilegeInlineEmbedded in one identityDeleted along with itStrict one-to-one useManaged policies are standalone and reusable; an inline policy is notLeast privilege: grant only the permissions a task needsRequestfrom AnaAny explicitDeny?AnyAllow?NoYesDENYexplicit, always winsYesALLOWaccess grantedNoDENYimplicit (default)Everything starts denied; an Allow opens access;an explicit Deny anywhere overrides every AllowPasswordAWS Management ConsolePassword policy setslength, complexity,expiry and reuseMFAa second factorPasskey or security keyAuthenticator appHardware TOTP tokenAccess keysCLI, SDKs, APIKey ID + secret keyNever share or put in codeRotate; prefer rolesMFA = something you know plus something you haveIAM credential reportthe whole accountLists every userPassword and access key statusIs MFA turned on?Last used, last rotatedIAM Access Advisorlast accessed informationPer user, group, role or policyWhich services it can reachWhen each was last usedRemove what's never usedAudit regularly, then trim permissions toward least privilegeIf the question says……think“Only the root user can…”Account-level tasks“Protect the root user”MFA, no access keys“Same permissions for many users”IAM group + policy“Grant only what's needed”Least privilege“Deny and Allow both apply”Explicit deny wins“Audit users' credentials and MFA”Credential report“Find unused permissions”IAM Access AdvisorRoot userComplete access to the accountTurn on MFA; no access keysOnly for root-only tasksDaily work: an admin userOrganizations: remove member rootUsers, groups, policiesGroups give users permissionsJSON: Effect, Action, ResourceAWS managed, customer, inlineExplicit deny always winsLeast privilege, MFA, auditsLock away root, start from nothing,and allow only what each job needs.

Tip: turn your phone sideways or use full screen for larger labels.

Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.

Learning objective

Explain why and how to protect the AWS account root user, recognize root-only tasks, and use IAM users, groups and policies (AWS managed, customer managed and inline) with least privilege, MFA, password policies and access auditing.

Exam mapping

Domain 2: Security and Compliance (30%). Task statement 2.3 in the official exam guide.

Key takeaways

  • The AWS account root user is created with the account and has complete access to all its resources. Protect it with MFA, don't create root access keys, and use it only for tasks that require it.
  • Root-only tasks include changing a standalone account's root email, password or root access keys; closing or reopening a standalone account; restoring permissions when the only admin is locked out; activating IAM access to billing; registering as a Reserved Instance Marketplace seller; and turning on S3 MFA delete.
  • IAM users have long-term credentials. IAM groups let many users share the same permissions; a user can be in several groups, and groups can't be nested.
  • A policy is a JSON document: Effect (Allow or Deny), Action, Resource and an optional Condition. Policies are AWS managed, customer managed (reusable, precise) or inline (embedded in one identity).
  • Requests are implicitly denied by default; an Allow grants access, and an explicit Deny overrides any Allow.
  • Apply least privilege, require MFA, set a password policy, protect access keys, and audit with the IAM credential report and IAM Access Advisor (last accessed information).

Exam tips

How the exam asks about this

Questions describe a situation and expect you to recognize the concept behind it.

If the question mentions…Think
A task that only the root user can performAccount-level tasks: root email or password, closing a standalone account, IAM access to billing, S3 MFA delete
Best way to protect the root userTurn on MFA, remove root access keys, use it only for root-only tasks
Give many employees the same permissionsAdd them to an IAM group and attach a policy to the group
Grant only the permissions needed for a jobPrinciple of least privilege
A policy allows an action and another explicitly denies itDenied: an explicit deny always wins
Find unused permissions; list users' credential and MFA statusIAM Access Advisor; IAM credential report

Common traps

  • Don't use the root user for daily administration, even by the account owner. Create an administrative user and lock root away with MFA and no access keys.
  • Not every account setting needs root: the account name, contact information and Regions can be changed by authorized IAM users. Older study materials also list changing the support plan as root-only; the current IAM root-user task list doesn't include it.
  • IAM groups can't contain other groups, and a group isn't an identity that signs in: users do, and they inherit the groups' permissions.
  • The credential report and Access Advisor answer different questions: the credential report covers credential status (passwords, keys, MFA); Access Advisor covers which services were last accessed.

Practice

Exam-style questions

Answer each one before you open the explanation.

Question 1. Which task requires signing in as the AWS account root user?

  1. Creating an IAM group for the development team
  2. Activating IAM access to the Billing and Cost Management console
  3. Attaching an AWS managed policy to an IAM user
  4. Generating an IAM credential report
Show answer

B. Activating IAM access to the Billing and Cost Management console. Activating IAM user and role access to the Billing and Cost Management console is on AWS's list of root-only tasks. Creating groups and attaching policies are tempting because they're administrative, but any IAM user with the right permissions can do them. The credential report also only needs IAM permissions.

Question 2. Which actions follow AWS best practices for protecting the root user? (Select TWO.)

  1. Share the root password with the whole IT team
  2. Create access keys for the root user to run scripts
  3. Turn on multi-factor authentication (MFA) for the root user
  4. Use the root user for daily administration
  5. Create an administrative user for everyday tasks
Show answer

C. Turn on multi-factor authentication (MFA) for the root user and E. Create an administrative user for everyday tasks. Turn on MFA for the root user and do everyday work with an administrative user instead. Root access keys are tempting for automation, but AWS recommends not creating them at all: a leaked root key exposes the whole account. Sharing the password or using root daily increases the risk.

Question 3. A company wants to give 20 developers the same permissions and change them easily later. What should it do?

  1. Attach the same inline policy to each developer's user
  2. Share one IAM user among all the developers
  3. Give the developers the root user credentials
  4. Add the developers to an IAM group and attach a policy to the group
Show answer

D. Add the developers to an IAM group and attach a policy to the group. Attaching a policy to an IAM group gives every member the same permissions, and changing the group's policy updates all of them. Inline policies on each user are tempting because they work, but they must be edited 20 times. Shared users and root credentials break accountability and least privilege.

Question 4. An IAM user is in a group whose policy allows all Amazon S3 actions. A policy attached directly to the user explicitly denies s3:DeleteObject. What happens when the user tries to delete an object?

  1. The request is denied, because an explicit deny overrides any allow
  2. The request is allowed, because the group policy allows all S3 actions
  3. The request is allowed, because group policies take priority over user policies
  4. The request is denied only if the user hasn't signed in with MFA
Show answer

A. The request is denied, because an explicit deny overrides any allow. An explicit Deny in any applicable policy overrides every Allow, wherever the policies are attached. The group's allow-all is tempting, but it can't beat an explicit deny. There's no priority between group and user policies, and nothing here depends on MFA.

Question 5. A security team wants to find permissions that users haven't used in months so it can remove them. Which IAM feature helps?

  1. IAM credential report
  2. IAM password policy
  3. IAM Access Advisor (last accessed information)
  4. AWS managed policies
Show answer

C. IAM Access Advisor (last accessed information). IAM Access Advisor shows which services an identity or policy can access and when each was last accessed, so unused permissions can be removed. The credential report is tempting because it's an audit tool, but it covers credential status (passwords, access keys, MFA), not which services were used.

Transcript

Lesson transcript

The full narration, scene by scene. The captions file contains the same text with timings.

Scene 1 · 0:00

Lesson 10: IAM Essentials. Welcome back to Domain 2, Security and Compliance. This lesson starts task 2.3: access management. We'll cover two ideas. First, the root user: the all-powerful identity created with every AWS account, and how to lock it away. Second, IAM users, groups and policies: how our online store gives each person exactly the access they need, and nothing more.

Scene 2 · 0:26

The root user: the master key. When the store opened its AWS account, it got one identity automatically: the root user. It signs in with the account's email address and password, and it has complete access to every service and resource in the account, including billing. If someone steals it, they control everything, even closing the account. So the root user is locked away, and everyday work happens through an administrative user instead.

Scene 3 · 0:55

Tasks only the root user can do. A few tasks still need the root user. For a standalone account: changing the root email address, root password or root access keys, and closing or reopening the account. Restoring permissions when the only IAM administrator locked themselves out. Activating IAM access to billing. Registering as a Reserved Instance Marketplace seller. Turning on MFA delete for an S3 bucket. Fixing an S3 bucket or SQS queue policy that denies everyone. And signing up for AWS GovCloud.

Scene 4 · 1:28

Locking the root user away. So how does the store protect its root user? Turn on multi-factor authentication. Don't create access keys for the root user, and delete any that exist. Sign in as root only for those root-only tasks, and create an administrative user for daily work. And if the company runs many accounts with AWS Organizations, it can centrally remove root user credentials from member accounts altogether, so nobody can sign in as root there.

Scene 5 · 1:59

IAM users and groups. Now the store's staff. AWS Identity and Access Management, or IAM, controls who can sign in and what they can do. Each person gets an IAM user with their own long-term credentials. Instead of granting permissions one by one, the store puts users in groups: Developers, Billing and Admins, and attaches policies to each group. Ana inherits the Developers permissions. Chloe is in two groups and gets both. Groups hold only users, never other groups.

Scene 6 · 2:31

Anatomy of a policy. Permissions are written as policies, which are JSON documents. Each statement has an Effect, Allow or Deny. An Action, the API calls it covers, such as s3 GetObject. A Resource, the specific items, identified by their Amazon Resource Name. And an optional Condition, for when the statement applies, such as only with MFA. This one lets a user read product images from one bucket, and nothing else.

Scene 7 · 3:01

Managed and inline policies. Policies come in three kinds. AWS managed policies are written and maintained by AWS, like ReadOnlyAccess: quick to use, but often broader than a job needs. Customer managed policies are written by you, so you can make them precise and reuse them across many users, groups and roles. Inline policies are embedded in a single identity and deleted along with it. Whichever you use, follow least privilege: grant only the permissions a task needs.

Scene 8 · 3:33

Allow, deny and explicit deny. How does AWS decide? Every request starts denied. This is called an implicit deny. First, AWS looks for an explicit Deny in any policy that applies. If it finds one, the answer is deny, no matter how many Allows exist. If there's no Deny, AWS looks for an Allow. If one matches, access is granted. If nothing matches, the request stays implicitly denied. Remember the rule: an explicit deny always overrides an allow.

Scene 9 · 4:04

Passwords, MFA and access keys. Console users have a password, and an account password policy sets its length, complexity, expiry and reuse rules. MFA adds something you have to something you know: a passkey or security key, an authenticator app, or a hardware token. For the CLI and SDKs, users get access keys: an access key ID and a secret key. Never share them or put them in code, rotate them, and prefer temporary credentials from roles.

Scene 10 · 4:36

Auditing access. Two IAM tools help the store audit. The IAM credential report lists every user in the account with the status of their credentials: passwords, access keys, and whether MFA is turned on. IAM Access Advisor shows last accessed information: which services a user, group, role or policy can reach, and when each was last used. Permissions that are never used can be removed.

Scene 11 · 5:03

How the exam asks about this. Here's how the exam asks about this. Only the root user can: think account-level tasks such as changing the root email or closing a standalone account. Protect the root user: MFA and no access keys. Same permissions for many users: an IAM group with a policy. Grant only what's needed: least privilege. Deny and Allow both apply: explicit deny wins. Audit credentials and MFA: the credential report. Find unused permissions: IAM Access Advisor.

Scene 12 · 5:35

Recap: IAM essentials. To recap: the root user has complete access, so turn on MFA, skip access keys, and use it only for root-only tasks. Everyday access goes through IAM. Users get permissions from groups and policies, written in JSON with an Effect, Action and Resource. Policies can be AWS managed, customer managed or inline, and an explicit deny always wins. Next, we'll replace long-term keys with IAM roles, federation and IAM Identity Center.

Download captions (WebVTT)

Sources and accuracy

Checked against AWS documentation and the official CLF-C02 exam guide on October 18, 2026. AWS changes often, so confirm details in the current documentation. Diagrams and numbers in the animation are illustrative.

This free course is independent and isn't affiliated with or endorsed by Amazon Web Services. AWS and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates.

Preparing a team for AWS certification?

I run hands-on AWS training for teams, from Cloud Practitioner basics to architecture, built around your own environment.