INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: Account protection and resource cleanup

AWS root user security: MFA, recovery and separate daily access

The AWS root user has highly privileged account access. Keep it separate from routine learning and application execution, and protect both sign-in and recovery. Start by establishing whether the account is standalone or uses centralized root access in AWS Organizations.

What you will learn

Separate root from routine access and review MFA, mailbox, contacts and recovery ownership for the account’s management model.

Prerequisite

This lesson provides a review framework. Authorized administrators make actual changes in official tools; enter no secrets here.

Root is separate from everyday identities

Root is the privileged identity associated with the account’s registration email. AWS recommends reserving it for tasks that require root and using appropriate permissions with temporary credentials for everyday access. An IAM user, an IAM role and the root user are different identities.

Choose access for the task
UseReview
Root-required account tasksVerify the documented need, authorized operator, protection and recovery
Routine human workUse the organization’s federation/Identity Center model, suitable permissions and temporary access
Application executionUse workload roles where appropriate; do not embed long-term root keys

Protect recovery as well as sign-in

Three parts of root protection
Three parts of root protection1: MFA — Adds protection to root sign-in. — Root access. 2: Registered mailbox — The registered mailbox also participates in password recovery. — Root access. 3: Recovery contacts — Supports recovery after events such as loss of MFA; these are dependencies, not a network path. — Root access123Root accessMFARegistered mailboxRecovery contactsThree parts of root protection1: MFA — Adds protection to root sign-in. — Root access. 2: Registered mailbox — The registered mailbox also participates in password recovery. — Root access. 3: Recovery contacts — Supports recovery after events such as loss of MFA; these are dependencies, not a network path. — Root access123Root accessMFARegisteredmailboxRecoverycontacts
  1. MFA → Root accessAdds protection to root sign-in.
  2. Registered mailbox → Root accessThe registered mailbox also participates in password recovery.
  3. Recovery contacts → Root accessSupports recovery after events such as loss of MFA; these are dependencies, not a network path.
Root access
Use only when needed, by authorized operators.
MFA
An additional authentication factor; manage alternate registered devices.
Registered mailbox
Protect the mailbox and ensure authorized staff can receive messages.
Recovery contacts
Keep contact numbers, recovery ownership and emergency procedures current.

Multi-factor authentication (MFA) adds a factor beyond a password. Where root credentials exist, protect MFA and consider multiple supported registered devices. Keep the registered mailbox and phone number current, and establish who can recover access if a device is lost.

Centralized root access changes the procedure

Checks depend on the management model
Account modelReview approach
Standalone account with root credentialsReview sign-in, MFA, registered contacts and recovery
Organizations management accountProtect its own root access and establish administrator procedures
Member account with root credentials removed centrallyDo not assume normal root sign-in or password recovery; follow centralized administration

For a centrally managed member account, an absent root MFA device alone is not a reason to create credentials. Establish whether credentials were removed and follow the organization’s documented root-access process.

Do not create a root key for an exercise

Access keys are credentials for programmatic access. AWS strongly recommends against creating long-term root keys. Synthetic exercises here need no key. If an existing key is discovered, identify its use and dependencies and follow the administrator’s response process.

Choose an option to see the result and explanation.

An app appears to need broad access. What should you do first?
Read the answer and reason

Answer: Identify required operations and an appropriate role and permissions · Identify the actual operations and suitable workload access. Root’s power is not a reason to use it routinely or embed its keys.

Prepare a review the administrator can act on

  1. Identify the account model and tasks that actually require root.
  2. Where root credentials exist, review MFA and registered contact ownership.
  3. Establish recovery responsibility and temporary routine access.
  4. Address gaps through authorized procedures, without pasting credentials into learning tools.

Check, then explain in your own words

  1. Distinguish root from everyday access.
  2. Explain mailbox, phone and recovery ownership as well as MFA.
  3. Establish centralized management before choosing a procedure.
Check your understanding: Does MFA remove the need to protect recovery contacts?

No. Protect both sign-in and recovery.

Mailbox and phone access participate in recovery. Stale contacts or unclear ownership can hinder legitimate recovery and undermine protection against unauthorized recovery.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.