AWS AWSCloudFormation documentation change
Summary
Updated terminology from 'stack instances' to 'stacks' throughout document, added detailed concurrency mode explanations, and adjusted CLI syntax examples
Security assessment
Changes primarily involve terminology updates and operational clarifications without addressing security vulnerabilities or introducing security features. The added concurrency mode descriptions improve operational understanding but don't relate to security controls.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/stackinstances-override.md b/AWSCloudFormation/latest/UserGuide/stackinstances-override.md index 2e8bdb935..8713ea4dd 100644 --- a//AWSCloudFormation/latest/UserGuide/stackinstances-override.md +++ b//AWSCloudFormation/latest/UserGuide/stackinstances-override.md @@ -3 +3 @@ -Override parameters on stack instances (console)Override parameters on stack instances (AWS CLI) +Override parameters on stacks (console)Override parameters on stacks (AWS CLI) @@ -5 +5 @@ Override parameters on stack instances (console)Override parameters on stack ins -# Override parameter values on stack instances in CloudFormation StackSets +# Override parameter values on stacks within your CloudFormation stack set @@ -7 +7 @@ Override parameters on stack instances (console)Override parameters on stack ins -In certain cases, you might want stack instances in certain Regions or accounts to have different property values than those specified in the stack set itself. For example, you might want to specify a different value for a given parameter based on whether an account is used for development or production. For these situations, CloudFormation allows you to override parameter values in stack instances by account and Region. You can override template parameter values when you first create the stack instances, and you can override parameter values for existing stack instances. You can only set parameters you've previously overridden in stack instances back to the values specified in the stack set. +In certain cases, you might want stacks in certain Regions or accounts to have different property values than those specified in the stack set itself. For example, you might want to specify a different value for a given parameter based on whether an account is used for development or production. For these situations, CloudFormation allows you to override parameter values in stacks by account and Region. You can override template parameter values when you first create the stacks, and you can override parameter values for existing stacks. You can only set parameters you've previously overridden in stacks back to the values specified in the stack set. @@ -9 +9 @@ In certain cases, you might want stack instances in certain Regions or accounts -Parameter value overrides apply to stack instances in the accounts and Regions you select. During stack set updates, any parameter values overridden for a stack instance aren't updated, but retain their overridden value. +Parameter value overrides apply to stacks in the accounts and Regions you select. During stack set updates, any parameter values overridden for a stack aren't updated, but retain their overridden value. @@ -11 +11 @@ Parameter value overrides apply to stack instances in the accounts and Regions y -You can only override parameter _values_ that are specified in the stack set; to add or delete a parameter itself, you need to update the stack set template. If you add a parameter to a stack set template, then before you can override that parameter value in a stack instance you must first update all stack instances with the new parameter and value specified in the stack set. Once all stack instances have been updated with the new parameter, you can then override the parameter value in individual stack instances as desired. +You can only override parameter _values_ that are specified in the stack set; to add or delete a parameter itself, you need to update the stack set template. If you add a parameter to a stack set template, then before you can override that parameter value in a stack you must first update all stacks with the new parameter and value specified in the stack set. Once all stacks have been updated with the new parameter, you can then override the parameter value in individual stacks as desired. @@ -13 +13 @@ You can only override parameter _values_ that are specified in the stack set; to -To learn how to override stack set parameter values when you create stack instances, see [Add stacks to StackSets](./stackinstances-create.html). +To learn how to override stack set parameter values when you create stacks, see [Add stacks to StackSets](./stackinstances-create.html). @@ -17 +17 @@ To learn how to override stack set parameter values when you create stack instan - * Override parameters on stack instances (console) + * Override parameters on stacks (console) @@ -19 +19 @@ To learn how to override stack set parameter values when you create stack instan - * Override parameters on stack instances (AWS CLI) + * Override parameters on stacks (AWS CLI) @@ -24 +24 @@ To learn how to override stack set parameter values when you create stack instan -## Override parameters on stack instances (console) +## Override parameters on stacks (console) @@ -34 +34 @@ To learn how to override stack set parameter values when you create stack instan - 5. On the **Set deployment options** page, provide the accounts and Regions for the stack instances that you'll create overrides for. + 5. On the **Set deployment options** page, provide the accounts and Regions for the stacks that you'll create overrides for. @@ -46 +46 @@ By default, CloudFormation will deploy stacks in the specified accounts within t - 2. For **Specify regions** , add one or more of the Regions into which you have deployed stack instances for this stack set. + 2. For **Specify regions** , add one or more of the Regions into which you have deployed stacks for this stack set. @@ -50 +50 @@ If you add multiple Regions, the order of the Regions under **Specify regions** - 3. For **Deployment options** : + 3. For **Deployment options** , do the following: @@ -52 +52 @@ If you add multiple Regions, the order of the Regions under **Specify regions** - * For **Maximum concurrent accounts** , modify the maximum concurrent accounts as needed. + * For **Maximum concurrent accounts** , specify how many accounts are processed concurrently. @@ -54 +54 @@ If you add multiple Regions, the order of the Regions under **Specify regions** - * For **Failure tolerance** , modify the failure tolerance as needed. + * For **Failure tolerance** , specify how many failures are acceptable before the operation stops. @@ -56 +56 @@ If you add multiple Regions, the order of the Regions under **Specify regions** - * For **Region concurrency** , modify the region concurrency as needed. + * For **Region concurrency** , choose how to process Regions: **Sequential** (one Region at a time) or **Parallel** (multiple Regions concurrently). @@ -58 +58,5 @@ If you add multiple Regions, the order of the Regions under **Specify regions** - * For **Concurrency mode** , modify the concurrency mode as needed. + * For **Concurrency mode** , choose how concurrency behaves during operation execution. + + * **Strict failure tolerance** – Reduces concurrency level when failures occur, staying within **Failure tolerance** +1. + + * **Soft failure tolerance** – Maintains your specified concurrency level (the value of **Maximum concurrent accounts**) regardless of failures. @@ -68 +72 @@ If you add multiple Regions, the order of the Regions under **Specify regions** -To set any overridden parameters back to using the value specified in the stack set, check all parameters and choose **Set to StackSet value** from the **Edit override value** menu. Doing so removes all overridden values once you update the stack instances. +To set any overridden parameters back to using the value specified in the stack set, check all parameters and choose **Set to StackSet value** from the **Edit override value** menu. Doing so removes all overridden values once you update the stacks. @@ -74 +78 @@ To set any overridden parameters back to using the value specified in the stack -CloudFormation starts updating your stack instances. View the progress and status of the stack instances in the stack set details page that opens when you choose **Submit**. +CloudFormation starts updating your stacks. View the progress and status of the stacks in the stack set details page that opens when you choose **Submit**. @@ -79 +83 @@ CloudFormation starts updating your stack instances. View the progress and statu -## Override parameters on stack instances (AWS CLI) +## Override parameters on stacks (AWS CLI) @@ -81 +85 @@ CloudFormation starts updating your stack instances. View the progress and statu -When acting as a delegated administrator, you must set the `--call-as` option to `DELEGATED_ADMIN` each time you run a StackSets command. +When acting as a delegated administrator, you must set the `--call-as` option to `DELEGATED_ADMIN` each time you run a stack set command. @@ -88 +92 @@ When acting as a delegated administrator, you must set the `--call-as` option to -[Self-managed permissions] For the `--accounts` option, provide the account IDs for which you want to override parameter values on stack instances. +[Self-managed permissions] For the `--accounts` option, provide the account IDs for which you want to override parameter values on stacks. @@ -92 +96 @@ When acting as a delegated administrator, you must set the `--call-as` option to - --accounts '["account_id"]' --regions '["us-east-1"]' + --accounts account_id --regions us-east-1 @@ -94 +98 @@ When acting as a delegated administrator, you must set the `--call-as` option to -[Service-managed permissions] For the `--deployment-targets` option, provide the organization root ID, OU IDs, or AWS Organizations account IDs for which you want to override parameters on stack instances. In this example, we override parameter values for stack instances in all accounts in the OU with the- `ou-rcuk-1x5j1lwo` ID. +[Service-managed permissions] For the `--deployment-targets` option, provide the organization root ID, OU IDs, or AWS Organizations account IDs for which you want to override parameters on stacks. In this example, we override parameter values for stacks in all accounts in the OU with the- `ou-rcuk-1x5j1lwo` ID. @@ -101 +105 @@ The overridden parameter values only apply to the accounts that are currently in - --regions '["us-east-1"]' + --regions us-east-1 @@ -103 +107 @@ The overridden parameter values only apply to the accounts that are currently in - 2. Verify that your parameter values were successfully overridden on stack instances by running the **describe-stack-set-operation** command to show the status and results of your update operation. For `--operation-id`, use the operation ID that was returned by your **update-stack-instances** command. + 2. Verify that your parameter values were successfully overridden on stacks by running the **describe-stack-set-operation** command to show the status and results of your update operation. For `--operation-id`, use the operation ID that was returned by your **update-stack-instances** command. @@ -116 +120 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Choose the Concurrency Mode +Add stacks to StackSets @@ -118 +122 @@ Choose the Concurrency Mode -Manage automatic deployments (service-managed permissions) +Enable-disable automatic deployments