AWS AWSCloudFormation documentation change
Summary
Updated terminology from 'stack set' to 'StackSet' (capitalized) throughout document and changed section header from 'Account level targets' to 'Revert stack imports'
Security assessment
Changes are primarily capitalization/naming convention updates and a section header modification. No specific security vulnerabilities, mitigations, or security features are mentioned in the diff. The 'Revert stack imports' change appears to be a documentation reorganization rather than a security-related update.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/stacksets-bestpractices.md b/AWSCloudFormation/latest/UserGuide/stacksets-bestpractices.md index b426cece8..93e495b29 100644 --- a//AWSCloudFormation/latest/UserGuide/stacksets-bestpractices.md +++ b//AWSCloudFormation/latest/UserGuide/stacksets-bestpractices.md @@ -5 +5 @@ -Defining the templateCreating or adding stacks to the stack setUpdating stacks in a stack set +Defining the templateCreating or adding stacks to the StackSetUpdating stacks in a StackSet @@ -9 +9 @@ Defining the templateCreating or adding stacks to the stack setUpdating stacks i -This section describes the best practices for defining a stack set template, creating or adding stacks to a stack set, or updating a stack set. +This section describes the best practices for defining a StackSet template, creating or adding stacks to a StackSet, or updating a StackSet. @@ -17 +17 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * Creating or adding stacks to the stack set + * Creating or adding stacks to the StackSet @@ -19 +19 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * Updating stacks in a stack set + * Updating stacks in a StackSet @@ -30 +30 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * A stack set has a single template and parameter set. The same stack is created in all accounts that are associated with a stack set. As you author your templates, make them granular enough to allow you a good balance of control and standardization. + * A StackSet has a single template and parameter set. The same stack is created in all accounts that are associated with a StackSet. As you author your templates, make them granular enough to allow you a good balance of control and standardization. @@ -37 +37 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b -## Creating or adding stacks to the stack set +## Creating or adding stacks to the StackSet @@ -39 +39 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * Verify that adding stack instances to your initial stack set works before you add larger numbers of stack instances to your stack set. + * Verify that adding stack instances to your initial StackSet works before you add larger numbers of stack instances to your StackSet. @@ -47 +47 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * Operations on stack sets depend on how many stack instances are involved, and can take significant time. + * Operations on StackSets depend on how many stack instances are involved, and can take significant time. @@ -52 +52 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b -## Updating stacks in a stack set +## Updating stacks in a StackSet @@ -54 +54 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b - * By default, updating a stack set updates all stack instances. If you have 20 accounts each in two regions, you will have 40 stack instances, and all will be updated when you update the stack set. + * By default, updating a StackSet updates all stack instances. If you have 20 accounts each in two regions, you will have 40 stack instances, and all will be updated when you update the StackSet. @@ -56 +56 @@ If you are new to CloudFormation, review the [CloudFormation best practices](./b -For stack sets with a large number of stack instances, we recommend that to test the updated version of a template, you selectively update the stack instances in a few test accounts before updating all stack instances. +For StackSets with a large number of stack instances, we recommend that to test the updated version of a template, you selectively update the stack instances in a few test accounts before updating all stack instances. @@ -58 +58 @@ For stack sets with a large number of stack instances, we recommend that to test - * To get more granular control over updating individual stacks within your stack set, plan to create multiple stack sets. + * To get more granular control over updating individual stacks within your StackSet, plan to create multiple StackSets. @@ -60 +60 @@ For stack sets with a large number of stack instances, we recommend that to test - * Updating a stack set that contains a large number of stacks can take significant time. In this release, only one operation is permitted at a time on a stack set. Plan your updates so you are not blocked from performing other operations on the stack set. + * Updating a StackSet that contains a large number of stacks can take significant time. In this release, only one operation is permitted at a time on a StackSet. Plan your updates so you are not blocked from performing other operations on the StackSet. @@ -71 +71 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Account level targets +Revert stack imports