AWS Security ChangesHomeSearch

AWS AWSCloudFormation documentation change

Service: AWSCloudFormation · 2025-06-22 · Documentation low

File: AWSCloudFormation/latest/UserGuide/stackinstances-delete.md

Summary

Updated terminology from 'stack set' to 'StackSet' for consistency, clarified failure tolerance behavior, added CLI syntax examples, and restructured documentation sections.

Security assessment

Changes focus on terminology standardization (StackSet capitalization), operational clarity (failure tolerance limits per Region), and command syntax improvements. No evidence of addressing vulnerabilities, patching weaknesses, or introducing new security controls. The note about delegated admin permissions ('--call-as') clarifies existing security practices but doesn't introduce new security features.

Diff

diff --git a/AWSCloudFormation/latest/UserGuide/stackinstances-delete.md b/AWSCloudFormation/latest/UserGuide/stackinstances-delete.md
index 4e30a80be..9de88a9b7 100644
--- a//AWSCloudFormation/latest/UserGuide/stackinstances-delete.md
+++ b//AWSCloudFormation/latest/UserGuide/stackinstances-delete.md
@@ -5 +5 @@
-Delete stacks from your stack set (console)Delete stacks from your stack set (AWS CLI)
+Delete stacks from your StackSet (console)Delete stacks from your StackSet (AWS CLI)
@@ -7 +7 @@ Delete stacks from your stack set (console)Delete stacks from your stack set (AW
-# Delete stacks from CloudFormation StackSets 
+# Delete stacks from AWS CloudFormation StackSets 
@@ -13 +13 @@ You can delete stacks from StackSets using either the CloudFormation console or
-  * Delete stacks from your stack set (console)
+  * Delete stacks from your StackSet (console)
@@ -15 +15 @@ You can delete stacks from StackSets using either the CloudFormation console or
-  * Delete stacks from your stack set (AWS CLI)
+  * Delete stacks from your StackSet (AWS CLI)
@@ -22 +22 @@ You can delete stacks from StackSets using either the CloudFormation console or
-Deleting stacks from a top-level organizational unit (OU) removes that OU as a stack set target.
+Deleting stacks from a top-level organizational unit (OU) removes that OU as a StackSet target.
@@ -24 +24,3 @@ Deleting stacks from a top-level organizational unit (OU) removes that OU as a s
-## Delete stacks from your stack set (console)
+## Delete stacks from your StackSet (console)
+
+###### To delete stacks
@@ -28 +30 @@ Deleting stacks from a top-level organizational unit (OU) removes that OU as a s
-  2. On the navigation bar at the top of the screen, choose the AWS Region you created the stack set in.
+  2. On the navigation bar at the top of the screen, choose the AWS Region you created the StackSet in.
@@ -30 +32 @@ Deleting stacks from a top-level organizational unit (OU) removes that OU as a s
-  3. From the navigation pane, choose **StackSets**. On the StackSets page, select the stack set.
+  3. From the navigation pane, choose **StackSets**. On the StackSets page, select the StackSet.
@@ -32 +34 @@ Deleting stacks from a top-level organizational unit (OU) removes that OU as a s
-  4. With your stack set selected, choose **Delete stacks from StackSet** from the **Actions** menu.
+  4. With your StackSet selected, choose **Delete stacks from StackSet** from the **Actions** menu.
@@ -64 +66 @@ For **Account filter type** , you can refine which accounts will have stacks del
-     * For **Failure tolerance** , specify how many failures are acceptable before the operation stops.
+     * For **Failure tolerance** , specify the maximum number of account failures allowed per Region. The operation will stop and won't proceed to other Regions once this limit is reached.
@@ -66 +68 @@ For **Account filter type** , you can refine which accounts will have stacks del
-     * For **Retain stacks** , enable this option to save the stacks and their associated resources when removing them from your stack set. The resources stay in their current state but are no longer part of the stack set.
+     * For **Retain stacks** , enable this option to save the stacks and their associated resources when removing them from your StackSet. The resources stay in their current state but are no longer part of the StackSet.
@@ -72 +74 @@ For **Account filter type** , you can refine which accounts will have stacks del
-       * **Strict failure tolerance** – Reduces concurrency level when failures occur, staying within **Failure tolerance** +1.
+       * **Strict failure tolerance** – Reduces account concurrency level when failures occur, staying within **Failure tolerance** +1.
@@ -80,3 +82 @@ For **Account filter type** , you can refine which accounts will have stacks del
-  9. When you are ready to remove the stacks from your stack set, choose **Submit**.
-
-After stack deletion is finished, you can verify that stacks were deleted from your stack set in the stack set detail page, on the **Stack instances** tab.
+  9. When you are ready to remove the stacks from your StackSet, choose **Submit**.
@@ -83,0 +84 @@ After stack deletion is finished, you can verify that stacks were deleted from y
+After stack deletion is finished, you can verify that stacks were deleted from your StackSet in the StackSet detail page, on the **Stack instances** tab.
@@ -87 +87,0 @@ After stack deletion is finished, you can verify that stacks were deleted from y
-## Delete stacks from your stack set (AWS CLI)
@@ -89 +89 @@ After stack deletion is finished, you can verify that stacks were deleted from y
-When acting as a delegated administrator, you must set the `--call-as` option to `DELEGATED_ADMIN` each time you run a stack set command.
+## Delete stacks from your StackSet (AWS CLI)
@@ -90,0 +91 @@ When acting as a delegated administrator, you must set the `--call-as` option to
+###### Note
@@ -92 +93 @@ When acting as a delegated administrator, you must set the `--call-as` option to
-    --call-as DELEGATED_ADMIN
+When acting as a delegated administrator, you must include `--call-as DELEGATED_ADMIN` in the command. 
@@ -94 +95 @@ When acting as a delegated administrator, you must set the `--call-as` option to
-  1. Use the **delete-stack-instances** command with your stack set name.
+Use the **delete-stack-instances** command with your StackSet name.
@@ -102 +103,4 @@ Set concurrent account processing and other preferences using the `--operation-p
-[Self-managed permissions] For the `--accounts` option, specify the IDs of the account to delete stacks from.
+###### To delete stacks (self-managed permissions)
+
+For the `--accounts` option, specify the IDs of the account to delete stacks from.
+    
@@ -110 +114,3 @@ Set concurrent account processing and other preferences using the `--operation-p
-[Service-managed permissions] For `--deployment-targets`, specify the organization root ID or organizational unit (OU) IDs to delete stacks from.
+###### To delete stacks (service-managed permissions)
+
+For `--deployment-targets`, specify the organization root ID or organizational unit (OU) IDs to delete stacks from.
@@ -117 +124 @@ CloudFormation will delete stacks from both the specified target OUs and their c
-      --deployment-targets OrganizationalUnitIds='["ou-rcuk-1x5jlwo", "ou-rcuk-slr5lh0a"]' \ 
+      --deployment-targets OrganizationalUnitIds=ou-rcuk-1x5jlwo,ou-rcuk-slr5lh0a \ 
@@ -124 +131,2 @@ For more information, see [DeleteStackInstances](https://docs.aws.amazon.com/AWS
-  2. Optionally, after stack deletion is finished, verify that stacks were deleted from your stack set by running the **describe-stack-set-operation** command to show the status and results of the delete stacks operation. For `--operation-id`, use the operation ID that was returned by your **delete-stack-instances** command.
+Optionally, after stack deletion is finished, verify that stacks were deleted from your StackSet by running the **describe-stack-set-operation** command to show the status and results of the delete stacks operation. For `--operation-id`, use the operation ID that was returned by your **delete-stack-instances** command.
+    
@@ -138 +143 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Enable-disable automatic deployments
+Override parameters on stacks