Root access for member accounts should be managed centrally in AWS Organizations
This check looks at whether centralized root access management is enabled for your AWS Organization, which covers root credentials management and root sessions. The safe setting is that member accounts do not keep their own root credentials and privileged root tasks run through short-lived sessions from the management account.
Why it matters
Every AWS account has a root user with permissions that cannot be limited by normal policies. In an organization with many accounts, each root user with its own password, access keys and MFA device is one more secret to protect and one more way in if it is lost. Managing root access centrally lets you remove those credentials from member accounts and use a short, controlled session when a root-only task comes up.
AWS describes the feature in Centralize root access for member accounts.
How to check it yourself
Sign in to the management account (or a delegated administrator), open the IAM console and choose Root access management. It shows whether root credentials management and root sessions are enabled. The command below only reads that state:
aws iam list-organizations-features
# EnabledFeatures should list RootCredentialsManagement and RootSessionsIf the list is empty or misses one of the two names, the setting is not in place. Use a read-only role, or try it first in a test organization.
How to fix it
In the IAM console, under Root access management, choose Enable and switch on both root credentials management and root sessions. Trusted access for IAM in AWS Organizations is required first. Run the steps in the management account or the delegated administrator account.
Scripted version. It changes your organization, so ConfigCobra never runs it for you:
aws organizations enable-aws-service-access --service-principal iam.amazonaws.com
aws iam enable-organizations-root-credentials-management
aws iam enable-organizations-root-sessionsAfterwards you can review which member accounts still have root credentials and remove them from the console, or with a root session for each account.
What changes when you fix it
The affected people are the administrators of the management account and of every member account. Workloads running in the accounts are not affected, because they do not use the root user.
- Member accounts can have their root password, access keys and MFA devices removed, so there is nothing left to steal or forget.
- New accounts created in the organization can be set up without root credentials.
- Root-only tasks, such as fixing a bucket policy that locks everyone out, are done from the management account with a short root session instead of signing in as root.
- Before you remove root credentials, make sure nobody still relies on them to sign in or to recover an account.
List the member accounts and the people who hold their root credentials first, and agree who may start root sessions.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Amazon Web Services Foundations v7.0.0 | 2.1.1 | Level 2 |
Related checks
Check this on your AWS
ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.