AWS Security ChangesHomeSearch

AWS smc documentation change

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

File: smc/latest/ag/jsd-creating-sc-end-user.md

Summary

Replaced 'AWS CloudFormation' with 'CloudFormation' in policy guidance

Security assessment

Terminology update without altering security recommendations about IAM permissions

Diff

diff --git a/smc/latest/ag/jsd-creating-sc-end-user.md b/smc/latest/ag/jsd-creating-sc-end-user.md
index 3365aee6c..38d8e9745 100644
--- a//smc/latest/ag/jsd-creating-sc-end-user.md
+++ b//smc/latest/ag/jsd-creating-sc-end-user.md
@@ -13 +13 @@ The following section describes how to create the AWS Service Management Connect
-  2. For products with AWS CloudFormation StackSets, you need to create a stack set inline policy. With AWS CloudFormation StackSets, you can create products to deploy across multiple accounts and Regions.
+  2. For products with CloudFormation StackSets, you need to create a stack set inline policy. With CloudFormation StackSets, you can create products to deploy across multiple accounts and Regions.
@@ -71 +71 @@ JSON
-For Service Catalog products with AWS CloudFormation StackSets, you need to include the read only permissions for the services you want to provision. For example, to provision an Amazon S3 bucket, include the **AmazonS3ReadOnlyAccess** policy to the **SCEndUser** role.
+For Service Catalog products with CloudFormation StackSets, you need to include the read only permissions for the services you want to provision. For example, to provision an Amazon S3 bucket, include the **AmazonS3ReadOnlyAccess** policy to the **SCEndUser** role.