AWS controltower documentation change
Summary
Updated documentation links by adding an extra slash in URLs to AWS Control Tower and Service Catalog documentation references
Security assessment
The changes only modify URL paths by adding an extra slash (e.g., changing '/controltower/' to '//controltower/'). This appears to be a formatting or linking correction rather than addressing security vulnerabilities or describing security features. No security-related content was added or modified in the documentation text itself.
Diff
diff --git a/controltower/latest/userguide/quick-account-provisioning.md b/controltower/latest/userguide/quick-account-provisioning.md index fdadcff80..e2bcf1456 100644 --- a//controltower/latest/userguide/quick-account-provisioning.md +++ b//controltower/latest/userguide/quick-account-provisioning.md @@ -11 +11 @@ Two common ways exist to enroll an individual AWS account into AWS Control Tower - 1. After you select the _auto-enrollment_ feature in the **Settings** page, you can create an AWS account outside of AWS Control Tower and move it directly into a registered OU. For more information, see [Move and enroll accounts automatically](https://docs.aws.amazon.com/controltower/latest/userguide/account-auto-enroll.html). This option is available for landing zone versions 3.1 and later. + 1. After you select the _auto-enrollment_ feature in the **Settings** page, you can create an AWS account outside of AWS Control Tower and move it directly into a registered OU. For more information, see [Move and enroll accounts automatically](https://docs.aws.amazon.com//controltower/latest/userguide/account-auto-enroll.html). This option is available for landing zone versions 3.1 and later. @@ -18 +18 @@ Two common ways exist to enroll an individual AWS account into AWS Control Tower -**The following sections describe the second option,** which requres no previous configuration of your AWS Control Tower environment. The AWS account must fulfill the required [prerequisites](https://docs.aws.amazon.com/controltower/latest/userguide/enrollment-prerequisites.html). +**The following sections describe the second option,** which requres no previous configuration of your AWS Control Tower environment. The AWS account must fulfill the required [prerequisites](https://docs.aws.amazon.com//controltower/latest/userguide/enrollment-prerequisites.html). @@ -35 +35 @@ Next, follow the steps for enrolling an individual account, as shown in the Step - * The console-based **Enroll account** capability is available when your landing zone is not in a state of [drift](https://docs.aws.amazon.com/controltower/latest/userguide/drift.html). If your landing zone is in a state of drift, you may not be able to use the **Enroll account** capability successfully. You'll need to provision new accounts through Account Factory or another method, until your landing zone drift has been resolved. + * The console-based **Enroll account** capability is available when your landing zone is not in a state of [drift](https://docs.aws.amazon.com//controltower/latest/userguide/drift.html). If your landing zone is in a state of drift, you may not be able to use the **Enroll account** capability successfully. You'll need to provision new accounts through Account Factory or another method, until your landing zone drift has been resolved. @@ -81 +81 @@ After the **AdministratorAccess** access permission (policy) is in place in your - * You may be signed in to an account that needs to be added to the Account Factory Portfolio in AWS Service Catalog. The account must be added before you'll have access to Account Factory so you can create or enroll an account in AWS Control Tower. If the appropriate user or role is not added to the Account Factory portfolio, you’ll receive an error when you attempt to add an account. For instructions on how to grant access to AWS Service Catalog portfolios, see [Granting access to users](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/catalogs_portfolios_users.html). + * You may be signed in to an account that needs to be added to the Account Factory Portfolio in AWS Service Catalog. The account must be added before you'll have access to Account Factory so you can create or enroll an account in AWS Control Tower. If the appropriate user or role is not added to the Account Factory portfolio, you’ll receive an error when you attempt to add an account. For instructions on how to grant access to AWS Service Catalog portfolios, see [Granting access to users](https://docs.aws.amazon.com//servicecatalog/latest/adminguide/catalogs_portfolios_users.html). @@ -94 +94 @@ After the **AdministratorAccess** access permission (policy) is in place in your -For more information about how AWS Control Tower works with roles when you're creating new accounts or enrolling existing accounts, see [Roles and accounts](https://docs.aws.amazon.com/controltower/latest/userguide/roles.html). +For more information about how AWS Control Tower works with roles when you're creating new accounts or enrolling existing accounts, see [Roles and accounts](https://docs.aws.amazon.com//controltower/latest/userguide/roles.html). @@ -104 +104 @@ If you have doubts that your existing accounts and their configurations are comp - * First, use an AWS Config _conformance pack_ to evaluate how your accounts may be affected by some AWS Control Tower controls. To determine how enrollment into AWS Control Tower may affect your accounts, see [ Extend AWS Control Tower governance using AWS Config conformance packs](https://aws.amazon.com/blogs/mt/extend-aws-control-tower-governance-using-aws-config-conformance-packs/). + * First, use an AWS Config _conformance pack_ to evaluate how your accounts may be affected by some AWS Control Tower controls. To determine how enrollment into AWS Control Tower may affect your accounts, see [ Extend AWS Control Tower governance using AWS Config conformance packs](https://aws.amazon.com//blogs/mt/extend-aws-control-tower-governance-using-aws-config-conformance-packs/).