AWS launchwizard documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' in launch constraint documentation
Security assessment
Change is purely terminological (branding update) without modifying security concepts. Launch constraints remain described as permission-limiting mechanisms with no vulnerability fixes or security enhancements introduced.
Diff
diff --git a/launchwizard/latest/userguide/launch-wizard-sap-service-catalog-constraint.md b/launchwizard/latest/userguide/launch-wizard-sap-service-catalog-constraint.md index 91d3206b0..538e83054 100644 --- a//launchwizard/latest/userguide/launch-wizard-sap-service-catalog-constraint.md +++ b//launchwizard/latest/userguide/launch-wizard-sap-service-catalog-constraint.md @@ -7 +7 @@ -A launch constraint specifies the AWS Identity and Access Management role that AWS Service Catalog assumes when a user launches a product. It is associated with products in the portfolio. If you do not use launch constraints, you must launch and manage products using your own IAM credentials. These credentials must have permissions to use AWS CloudFormation, AWS Service Catalog, and any other AWS services used by the products. Using a launch constraint allows you to limit the permissions of a user to the minimum required for a product. +A launch constraint specifies the AWS Identity and Access Management role that AWS Service Catalog assumes when a user launches a product. It is associated with products in the portfolio. If you do not use launch constraints, you must launch and manage products using your own IAM credentials. These credentials must have permissions to use CloudFormation, AWS Service Catalog, and any other AWS services used by the products. Using a launch constraint allows you to limit the permissions of a user to the minimum required for a product.