AWS launchwizard documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' in two instances for consistency
Security assessment
The changes are purely terminological, removing the 'AWS' prefix from CloudFormation references. There is no indication of addressing security vulnerabilities or introducing security-related content.
Diff
diff --git a/launchwizard/latest/userguide/launch-wizard-sap-deploying-console.md b/launchwizard/latest/userguide/launch-wizard-sap-deploying-console.md index 9d2d66a6c..a6ea1eb59 100644 --- a//launchwizard/latest/userguide/launch-wizard-sap-deploying-console.md +++ b//launchwizard/latest/userguide/launch-wizard-sap-deploying-console.md @@ -53 +53 @@ On the **Define infrastructure** page, define your deployment name and infrastru - * **Create an AWS Service Catalog product**. Select the check box to package and export AWS CloudFormation templates and associated application configuration scripts to Amazon S3 and create an AWS Service Catalog product. You use these scripts to deploy and configure AWS infrastructure resources for SAP applications. If you select this option, the templates and scripts are saved to the specified Amazon S3 path. You can use the saved AWS CloudFormation templates and AWS Service Catalog products for repeated deployments of the SAP applications using CloudFormation, AWS Service Catalog, and third-party applications integrated with AWS Service Catalog. + * **Create an AWS Service Catalog product**. Select the check box to package and export CloudFormation templates and associated application configuration scripts to Amazon S3 and create an AWS Service Catalog product. You use these scripts to deploy and configure AWS infrastructure resources for SAP applications. If you select this option, the templates and scripts are saved to the specified Amazon S3 path. You can use the saved CloudFormation templates and AWS Service Catalog products for repeated deployments of the SAP applications using CloudFormation, AWS Service Catalog, and third-party applications integrated with AWS Service Catalog. @@ -87 +87 @@ Return to the Launch Wizard console, and choose the refresh button next to the * -From the dropdown lists, choose the **Availability Zones** within which you want to deploy your SAP systems and choose the private subnets. The private subnets must have outbound connectivity to the internet and to other AWS services, such as Amazon S3, AWS CloudFormation, and CloudWatch Logs. They must also be able to access the Linux repositories required for instance configuration. +From the dropdown lists, choose the **Availability Zones** within which you want to deploy your SAP systems and choose the private subnets. The private subnets must have outbound connectivity to the internet and to other AWS services, such as Amazon S3, CloudFormation, and CloudWatch Logs. They must also be able to access the Linux repositories required for instance configuration.