AWS controltower: Fix broken URLs in landing zone documentation
Summary
Corrected multiple URLs by removing extra slashes to ensure proper linking.
Security assessment
Changes only fix URL formatting without altering security content or addressing vulnerabilities.
Evidence
+For a general discussion about best practices for organizational units, see [Best Practices for Organizational Units with AWS Organizations](https://aws.amazon.com/blogs/mt/best-practices-for-organizational-units-with-aws-organizations/).
Diff
diff --git a/controltower/latest/userguide/aws-multi-account-landing-zone.md b/controltower/latest/userguide/aws-multi-account-landing-zone.md index 13de773f1..7b7efd15f 100644 --- a//controltower/latest/userguide/aws-multi-account-landing-zone.md +++ b//controltower/latest/userguide/aws-multi-account-landing-zone.md @@ -17 +17 @@ Most landing zones develop over time. As the number of organizational units (OUs -For a general discussion about best practices for organizational units, see [Best Practices for Organizational Units with AWS Organizations](https://aws.amazon.com//blogs/mt/best-practices-for-organizational-units-with-aws-organizations/). +For a general discussion about best practices for organizational units, see [Best Practices for Organizational Units with AWS Organizations](https://aws.amazon.com/blogs/mt/best-practices-for-organizational-units-with-aws-organizations/). @@ -133 +133 @@ AWS Control Tower does not set up the Workloads OU for you. -For more information see [Production starter organization with AWS Control Tower](https://docs.aws.amazon.com//whitepapers/latest/organizing-your-aws-environment/production-starter-organization.html#production-starter-organization-with-aws-control-tower). +For more information see [Production starter organization with AWS Control Tower](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/production-starter-organization.html#production-starter-organization-with-aws-control-tower). @@ -141 +141 @@ You also can build a simpler, flat OU structure that performs well and aligns wi - * To view a diagram that shows an example set of OUs in an expanded, flat AWS Control Tower environment with AWS multi-account guidance, see [ Example: Workloads in a Flat OU Structure](https://docs.aws.amazon.com//whitepapers/latest/organizing-your-aws-environment/appendix-e-establish-multi-account.html#example-workloads-flat-structure). + * To view a diagram that shows an example set of OUs in an expanded, flat AWS Control Tower environment with AWS multi-account guidance, see [ Example: Workloads in a Flat OU Structure](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/appendix-e-establish-multi-account.html#example-workloads-flat-structure). @@ -145 +145 @@ You also can build a simpler, flat OU structure that performs well and aligns wi - * For more information about how AWS Control Tower aligns with the AWS guidance, see the AWS white paper, [Organizing Your AWS Environment Using Multiple Accounts](https://docs.aws.amazon.com//whitepapers/latest/organizing-your-aws-environment/appendix-e-establish-multi-account.html). + * For more information about how AWS Control Tower aligns with the AWS guidance, see the AWS white paper, [Organizing Your AWS Environment Using Multiple Accounts](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/appendix-e-establish-multi-account.html). @@ -174 +174 @@ In the Additional OUs area, several more OUs have been added to the basic struct -The Root is not an OU. It is a container for the management account, and for all OUs and accounts in your organization. Conceptually, the Root contains all of the OUs. It cannot be deleted. You cannot govern enrolled accounts at the Root level within AWS Control Tower. Instead, govern enrolled accounts within your OUs. For a helpful diagram, see [the AWS Organizations documentation](https://docs.aws.amazon.com//organizations/latest/userguide/orgs_getting-started_concepts.html). +The Root is not an OU. It is a container for the management account, and for all OUs and accounts in your organization. Conceptually, the Root contains all of the OUs. It cannot be deleted. You cannot govern enrolled accounts at the Root level within AWS Control Tower. Instead, govern enrolled accounts within your OUs. For a helpful diagram, see [the AWS Organizations documentation](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html).