AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, reformatted note about root user security, and fixed apostrophe typography in multiple places
Security assessment
Reformatted existing security note about root user best practices without adding new content. Typo fixes don't impact security posture.
Diff
diff --git a/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/set-up-organization.md b/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/set-up-organization.md index c06c8d72e..2c192dc2e 100644 --- a//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/set-up-organization.md +++ b//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/set-up-organization.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Transitioning to multiple AWS accounts](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Transitioning to multiple AWS accounts](introduction.html) @@ -15,5 +15,2 @@ When you use an account to create an organization, that account becomes the _man -###### Note - -Each AWS account also has a single identity called the _root user_. You can sign in as the root user by using the email address and password you used to create the account. However, we strongly recommend that you don't use the root user for everyday tasks, even the administrative ones. For more information, see [AWS account root user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html). - -We also recommend [centralizing root access for member accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-enable-root-access.html) and removing the root user credentials from member accounts in your organization. +Note: Each AWS account also has a single identity called the _root user_. You can sign in as the root user by using the email address and password you used to create the account. However, we strongly recommend that you don't use the root user for everyday tasks, even the administrative ones. For more information, see [AWS account root user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html).We also recommend [centralizing root access for member accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-enable-root-access.html) and removing the root user credentials from member accounts in your organization. +--- @@ -25 +22 @@ A [service control policy (SCP)](https://docs.aws.amazon.com/organizations/lates -A [resource control policy (RCP)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) offers central control over the maximum available permissions for resources in your organization. RCPs help you make sure that resources in your account stay within your organization’s access control guidelines. +A [resource control policy (RCP)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) offers central control over the maximum available permissions for resources in your organization. RCPs help you make sure that resources in your account stay within your organization's access control guidelines. @@ -31 +28 @@ You can use the AWS Organizations console to centrally view and manage all of yo - * Don't use an existing AWS account to create an organization. Start with a new account, which becomes your management account for the organization. Privileged operations can be performed within an organization’s management account, and SCPs and RCPs do not apply to the management account. That’s why you should limit the cloud resources and data contained in the management account to only those that must be managed in the management account. + * Don't use an existing AWS account to create an organization. Start with a new account, which becomes your management account for the organization. Privileged operations can be performed within an organization's management account, and SCPs and RCPs do not apply to the management account. That's why you should limit the cloud resources and data contained in the management account to only those that must be managed in the management account. @@ -37 +34 @@ You can use the AWS Organizations console to centrally view and manage all of yo - * Use RCPs to define the maximum permissions for resources in member accounts. RCPs can’t be directly applied to the management account. + * Use RCPs to define the maximum permissions for resources in member accounts. RCPs can't be directly applied to the management account.