AWS organizations: Document AccountFullAccessRole SCP protection and admin lockout risk
Summary
Adds guidance that project accounts lack OrganizationAccountAccessRole, that AccountFullAccessRole is service-only and protected by an AWS managed SCP, and warns to create OrganizationAccountAccessRole before editing/removing that SCP to avoid losing administrative access.
Security assessment
The change documents an AWS managed SCP that prevents deletion or modification of the service-only AccountFullAccessRole and provides a hardening warning to avoid lockout of administrative access. This is security best-practice guidance around IAM roles and SCPs, not a response to a specific vulnerability.
Evidence
+If you edit or remove this SCP so that you can delete `AccountFullAccessRole`, first create `OrganizationAccountAccessRole` and confirm that you can use it. Otherwise, you might lose administrative access to the account.
Diff
diff --git a/organizations/latest/userguide/orgs_manage_accounts_create-cross-account-role.md b/organizations/latest/userguide/orgs_manage_accounts_create-cross-account-role.md index 04bb03f..eb1cd12 100644 --- a//organizations/latest/userguide/orgs_manage_accounts_create-cross-account-role.md +++ b//organizations/latest/userguide/orgs_manage_accounts_create-cross-account-role.md @@ -9 +9 @@ -By default, if you create a member account as part of your organization, AWS automatically creates a role in the account that grants administrator permissions to IAM users in the management account who can assume the role. By default, that role is named `OrganizationAccountAccessRole`. For more information, see [Accessing a member account that has OrganizationAccountAccessRole with AWS Organizations](./orgs_manage_accounts_access-cross-account-role.html). +By default, if you create a member account in your organization by using the AWS Organizations console, the AWS CLI, or the `CreateAccount` API operation, AWS Organizations automatically creates a role in the account. This role grants administrator permissions to IAM users in the management account who can assume the role. By default, that role is named `OrganizationAccountAccessRole`. You can specify a different name when you create the account. For more information, see [Accessing a member account that has OrganizationAccountAccessRole with AWS Organizations](./orgs_manage_accounts_access-cross-account-role.html). @@ -12,0 +13,10 @@ However, member accounts that you _invite_ to join your organization _**do not** +Like invited accounts, project accounts, which you created as projects in AWS Settings, don't get `OrganizationAccountAccessRole` automatically. Project accounts don't have the role, even after you activate advanced features. To create the role in a project account, use the same procedure that you use for invited accounts. For more information about project accounts, see [Project accounts after you activate advanced features](https://docs.aws.amazon.com/accounts/latest/reference/activate-advanced-features.html#activate-advanced-features-project-accounts) in the _AWS Account Management Reference Guide_. + +Project accounts contain an AWS managed role named `AccountFullAccessRole`. Only an AWS service can assume this role, so you can't use it to switch roles from the management account into the member account. + +An AWS managed service control policy (SCP) prevents you from deleting or changing `AccountFullAccessRole`. This SCP stays attached to the root of your organization after you activate advanced features. For more information, see [Service control policies for projects](https://docs.aws.amazon.com/accounts/latest/reference/scps-and-rcps-for-projects.html#scps-for-projects) in the _AWS Account Management Reference Guide_. + +###### Important + +If you edit or remove this SCP so that you can delete `AccountFullAccessRole`, first create `OrganizationAccountAccessRole` and confirm that you can use it. Otherwise, you might lose administrative access to the account. +