AWS launchwizard documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in product descriptions and workflow steps
Security assessment
The modifications are terminology adjustments without any security context. The changes do not alter security requirements, policies, or best practices related to Service Catalog or SAP deployments.
Diff
diff --git a/launchwizard/latest/userguide/launch-wizard-sap-service-catalog-access.md b/launchwizard/latest/userguide/launch-wizard-sap-service-catalog-access.md index 6213415d9..0e1c3af68 100644 --- a//launchwizard/latest/userguide/launch-wizard-sap-service-catalog-access.md +++ b//launchwizard/latest/userguide/launch-wizard-sap-service-catalog-access.md @@ -21 +21 @@ In the AWS Service Catalog administrator console, the **Portfolio details** page - 5. The product created by Launch Wizard using AWS CloudFormation templates and user inputs is named **[LW Deployment Name]-[Deployment Type]**. You can create a new version by choosing **Create new version**. + 5. The product created by Launch Wizard using CloudFormation templates and user inputs is named **[LW Deployment Name]-[Deployment Type]**. You can create a new version by choosing **Create new version**. @@ -38 +38 @@ In the AWS Service Catalog administrator console, the **Portfolio details** page - 5. You will be directed to the AWS Service Catalog **Launching** page, which resembles AWS CloudFormation. Most of the parameters are specified using your defaults. Enter or replace the default values as you require, including passwords and SAPSIDs. + 5. You will be directed to the AWS Service Catalog **Launching** page, which resembles CloudFormation. Most of the parameters are specified using your defaults. Enter or replace the default values as you require, including passwords and SAPSIDs. @@ -40 +40 @@ In the AWS Service Catalog administrator console, the **Portfolio details** page - 6. After you verify the parameters, choose **Launch product** to start the creation of the AWS CloudFormation stack. + 6. After you verify the parameters, choose **Launch product** to start the creation of the CloudFormation stack.