AWS controltower documentation change
Summary
Changed 'AWS CloudFormation stack sets' to 'CloudFormation stack sets'
Security assessment
Consistency update in service naming. The security context of IAM roles and AdministratorAccess policies remains unchanged.
Diff
diff --git a/controltower/latest/userguide/step-4-call-the-blueprint.md b/controltower/latest/userguide/step-4-call-the-blueprint.md index eb1fc2275..b4525d55b 100644 --- a//controltower/latest/userguide/step-4-call-the-blueprint.md +++ b//controltower/latest/userguide/step-4-call-the-blueprint.md @@ -21 +21 @@ You must set up your customization hub account and add at least one blueprint (S - 4. (Optional) You can add or change a blueprint provisioning policy at this point in the process. The blueprint provisioning policy is written in JSON and attached to an IAM role, so it can provision the resources that are specified in the blueprint template. AWS Control Tower creates this role in the member account so that Service Catalog can deploy resources using AWS CloudFormation stack sets. The role is named `AWSControlTower-BlueprintExecution-bp-`xxxx``. The `AdministratorAccess` policy is applied here by default. + 4. (Optional) You can add or change a blueprint provisioning policy at this point in the process. The blueprint provisioning policy is written in JSON and attached to an IAM role, so it can provision the resources that are specified in the blueprint template. AWS Control Tower creates this role in the member account so that Service Catalog can deploy resources using CloudFormation stack sets. The role is named `AWSControlTower-BlueprintExecution-bp-`xxxx``. The `AdministratorAccess` policy is applied here by default.