AWS Security ChangesHomeSearch

AWS servicecatalog documentation change

Service: servicecatalog · 2025-11-19 · Documentation low

File: servicecatalog/latest/adminguide/constraints-launch.md

Summary

Replaced 'AWS CloudFormation' with 'CloudFormation' in multiple instances for terminology consistency

Security assessment

Changes are branding updates rather than security-related content modifications. The security context around IAM roles and permissions remains unchanged.

Diff

diff --git a/servicecatalog/latest/adminguide/constraints-launch.md b/servicecatalog/latest/adminguide/constraints-launch.md
index d4b920bb7..76342ac0a 100644
--- a//servicecatalog/latest/adminguide/constraints-launch.md
+++ b//servicecatalog/latest/adminguide/constraints-launch.md
@@ -11 +11 @@ A launch constraint specifies the AWS Identity and Access Management (IAM) role
-  * AWS CloudFormation product type: [Step 6: Add a launch constraint to assign an IAM role](./getstarted-launchconstraint.html)
+  * CloudFormation product type: [Step 6: Add a launch constraint to assign an IAM role](./getstarted-launchconstraint.html)
@@ -20 +20 @@ Launch constraints apply to products in the portfolio (product-portfolio associa
-Without a launch constraint, end users must launch and manage products using their own IAM credentials. To do so, they must have permissions for AWS CloudFormation, AWS services that the products use, and AWS Service Catalog. By using a launch role, you can instead limit the end users' permissions to the minimum they require for that product. For more information about end user permissions, see [Identity and Access Management in AWS Service Catalog](./controlling_access.html).
+Without a launch constraint, end users must launch and manage products using their own IAM credentials. To do so, they must have permissions for CloudFormation, AWS services that the products use, and AWS Service Catalog. By using a launch role, you can instead limit the end users' permissions to the minimum they require for that product. For more information about end user permissions, see [Identity and Access Management in AWS Service Catalog](./controlling_access.html).
@@ -43 +43 @@ The IAM role that you assign to a product as a launch constraint must have permi
-  * The `arn:aws:iam::aws:policy/AWSCloudFormationFullAccess` AWS CloudFormation managed policy
+  * The `arn:aws:iam::aws:policy/AWSCloudFormationFullAccess` CloudFormation managed policy
@@ -73 +73 @@ The `servicecatalog:ProvisionProduct`, `servicecatalog:TerminateProvisionedProdu
-To view provisioned Cloudformation products and resources in the AWS Service Catalog console, end users need AWS CloudFormation read access. Viewing provisioned products and resources in the console does **not** use the launch role.
+To view provisioned Cloudformation products and resources in the AWS Service Catalog console, end users need CloudFormation read access. Viewing provisioned products and resources in the console does **not** use the launch role.