AWS prescriptive-guidance documentation change
Summary
Minor terminology update: changed 'AWS CloudFormation' to 'CloudFormation' in one instance.
Security assessment
The change is purely a branding/terminology update with no technical impact. It doesn't reference security vulnerabilities, mitigations, or features. The content about bastion hosts remains unchanged with no security implications.
Diff
diff --git a/prescriptive-guidance/latest/iap-on-aws/provisioning.md b/prescriptive-guidance/latest/iap-on-aws/provisioning.md index 047092522..4db48af3d 100644 --- a//prescriptive-guidance/latest/iap-on-aws/provisioning.md +++ b//prescriptive-guidance/latest/iap-on-aws/provisioning.md @@ -7 +7 @@ -Service Catalog initiates the provisioning process as a CloudFormation stack set deployment of the resources that are specified in the CloudFormation provisioning template. (The template can be created directly in AWS CloudFormation or generated by the AWS CDK `ProductStack` construct.) Service Catalog product provisioning is a closed process—you cannot customize it to add preliminary or post-process steps, or tune it. However, you can modify the provisioning template to add steps in the form of CloudFormation resource specifications. These could be AWS Lambda or AWS Step Functions, or Lambda-backed custom resources that perform preliminary steps (such as custom bootstrapping to set up a bastion host that is used during provisioning) and post-steps (such as tearing down the bastion host). This method of implementing pre-provisioning and post-provisioning steps is subject to the same `include` and nested stack restrictions as the provisioning template. +Service Catalog initiates the provisioning process as a CloudFormation stack set deployment of the resources that are specified in the CloudFormation provisioning template. (The template can be created directly in CloudFormation or generated by the AWS CDK `ProductStack` construct.) Service Catalog product provisioning is a closed process—you cannot customize it to add preliminary or post-process steps, or tune it. However, you can modify the provisioning template to add steps in the form of CloudFormation resource specifications. These could be AWS Lambda or AWS Step Functions, or Lambda-backed custom resources that perform preliminary steps (such as custom bootstrapping to set up a bastion host that is used during provisioning) and post-steps (such as tearing down the bastion host). This method of implementing pre-provisioning and post-provisioning steps is subject to the same `include` and nested stack restrictions as the provisioning template.