AWS servicecatalog documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
Change only modifies branding terminology (removes 'AWS' prefix from CloudFormation references) without altering security functionality or addressing vulnerabilities.
Diff
diff --git a/servicecatalog/latest/adminguide/reference-template_constraint_rules.md b/servicecatalog/latest/adminguide/reference-template_constraint_rules.md index cf6338765..ccb110388 100644 --- a//servicecatalog/latest/adminguide/reference-template_constraint_rules.md +++ b//servicecatalog/latest/adminguide/reference-template_constraint_rules.md @@ -9 +9 @@ SyntaxExample: Conditionally Verify a Parameter Value -The rules that define template constraints in a AWS Service Catalog portfolio describe when end users can use the template and which values they can specify for parameters that are declared in the AWS CloudFormation template used to create the product they are attempting to use. Rules are useful for preventing end users from inadvertently specifying an incorrect value. For example, you can add a rule to verify whether end users specified a valid subnet in a given VPC or used `m1.small` instance types for test environments. AWS CloudFormation uses rules to validate parameter values before it creates the resources for the product. +The rules that define template constraints in a AWS Service Catalog portfolio describe when end users can use the template and which values they can specify for parameters that are declared in the CloudFormation template used to create the product they are attempting to use. Rules are useful for preventing end users from inadvertently specifying an incorrect value. For example, you can add a rule to verify whether end users specified a valid subnet in a given VPC or used `m1.small` instance types for test environments. CloudFormation uses rules to validate parameter values before it creates the resources for the product. @@ -13 +13 @@ Each rule consists of two properties: a rule condition (optional) and assertions -As an example, assume that you declared a VPC and a subnet parameter in the `Parameters` section. You can create a rule that validates that a given subnet is in a particular VPC. So when a user specifies a VPC, AWS CloudFormation evaluates the assertion to check whether the subnet parameter value is in that VPC before creating or updating the stack. If the parameter value is invalid, AWS CloudFormation immediately fail to create or update the stack. If users don't specify a VPC, AWS CloudFormation doesn't check the subnet parameter value. +As an example, assume that you declared a VPC and a subnet parameter in the `Parameters` section. You can create a rule that validates that a given subnet is in a particular VPC. So when a user specifies a VPC, CloudFormation evaluates the assertion to check whether the subnet parameter value is in that VPC before creating or updating the stack. If the parameter value is invalid, CloudFormation immediately fail to create or update the stack. If users don't specify a VPC, CloudFormation doesn't check the subnet parameter value.