Bitzu

SAA-C03 ยท Cloud foundations and IAM basics

Protecting the root user and using MFA

Tasks that require the root user, locking it down, MFA device types, avoiding long-term access keys and IAM user credential hygiene.

Key points

  • Root user (account sign-in email): full access.
  • Only for root-only tasks: restoring permissions when the only IAM admin is locked out, registering as Reserved Instance Marketplace seller.
  • Daily work: IAM Identity Center admin.
  • Protect with MFA; no root access keys.
  • MFA: FIDO passkeys and security keys (phishing-resistant, preferred), virtual apps, hardware TOTP tokens.
  • Up to eight devices per identity; SMS can no longer be enabled.

Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/root-user-tasks.html

Practice questions

Single choice

Which task can be performed only by signing in as the root user?

  1. Creating a new IAM user for a developer
  2. Registering as a seller in the Reserved Instance Marketplace
  3. Changing the account name shown in the console
  4. Launching an EC2 instance in a new Region
Show answer

Answer: B. Registering as a seller in the Reserved Instance Marketplace

Registering as a seller in the Reserved Instance Marketplace is on the list of root-only tasks. Creating IAM users and launching instances can be delegated to IAM identities, and changing the account name does not require root credentials either.

Select all that apply

Which MFA types can you currently enable for the root user or an IAM user?

  1. Passkeys and FIDO security keys
  2. Codes sent by SMS text message
  3. Virtual authenticator apps
  4. Hardware TOTP tokens
  5. One-time links sent by email
Show answer

Answer: A. Passkeys and FIDO security keys, C. Virtual authenticator apps, D. Hardware TOTP tokens

AWS supports passkeys and security keys (FIDO), virtual authenticator apps (TOTP) and hardware TOTP tokens. AWS ended support for enabling SMS text-message MFA, and email links are not an MFA type in IAM.

True or false

Creating access keys for the root user is a good practice, because automation running with root never fails on missing permissions.

Show answer

Answer: False

False. Root access keys are long-term credentials with unrestricted access, so a leak is catastrophic. Automation should use IAM roles with temporary credentials and only the permissions it needs; unused root keys should be deleted.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More SAA-C03 topics in this module