AWS prescriptive-guidance documentation change
Summary
Updated introduction link, corrected AWS Service Catalog casing, and modified image path
Security assessment
Changes are editorial (casing correction, link updates). The core security content about permissions boundaries remains unmodified. No indication of security vulnerability fixes or new security guidance.
Diff
diff --git a/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/creating-a-permissions-boundary.md b/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/creating-a-permissions-boundary.md index bb72f5c78..a04bd67b0 100644 --- a//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/creating-a-permissions-boundary.md +++ b//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/creating-a-permissions-boundary.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) @@ -85 +85 @@ The **CloudFormationRole** role, **PermissionsBoundary** policy, and the **Devel - * Users are able to provision products from Service Catalog, through the **AWSServiceCatalogEndUserFullAccess** AWS managed policy. + * Users are able to provision products from AWS Service Catalog, through the **AWSServiceCatalogEndUserFullAccess** AWS managed policy. @@ -111 +111 @@ The following image shows how an authorized user, such as a developer, can creat - +