AWS AWSCloudFormation documentation change
Summary
Updated documentation with consistent capitalization of 'StackSet' and added explicit CLI note for delegated administrators
Security assessment
Changes primarily involve capitalization consistency (stack set → StackSet) and formatting improvements. The added note about '--call-as DELEGATED_ADMIN' clarifies proper usage for delegated administrators but does not address a specific security vulnerability or weakness. This is a documentation refinement rather than a security fix.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/stacksets-delete.md b/AWSCloudFormation/latest/UserGuide/stacksets-delete.md index 90d07ede6..2df3aaef5 100644 --- a//AWSCloudFormation/latest/UserGuide/stacksets-delete.md +++ b//AWSCloudFormation/latest/UserGuide/stacksets-delete.md @@ -5 +5 @@ -Delete a stack set (console)Delete a stack set (AWS CLI)Delete service roles (optional) +Delete a StackSet (console)Delete a StackSet (AWS CLI)Delete service roles (optional) @@ -7 +7 @@ Delete a stack set (console)Delete a stack set (AWS CLI)Delete service roles (op -# Delete CloudFormation StackSets +# Delete AWS CloudFormation StackSets @@ -9 +9 @@ Delete a stack set (console)Delete a stack set (AWS CLI)Delete service roles (op -To delete a stack set, you must first delete all stacks in the stack set. For information about how to delete all stacks, see [Delete stacks from StackSets](./stackinstances-delete.html). +To delete a StackSet, you must first delete all stacks in the StackSet. For information about how to delete all stacks, see [Delete stacks from StackSets](./stackinstances-delete.html). @@ -13 +13 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - * Delete a stack set (console) + * Delete a StackSet (console) @@ -15 +15 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - * Delete a stack set (AWS CLI) + * Delete a StackSet (AWS CLI) @@ -22 +22,3 @@ To delete a stack set, you must first delete all stacks in the stack set. For in -## Delete a stack set (console) +## Delete a StackSet (console) + +###### To delete a StackSet @@ -26 +28 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - 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. @@ -28 +30 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - 3. On the **StackSets** page, select the stack set. + 3. On the **StackSets** page, select the StackSet. @@ -30 +32 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - 4. With the stack set selected, choose **Delete StackSet** from the **Actions** menu. + 4. With the StackSet selected, choose **Delete StackSet** from the **Actions** menu. @@ -32 +34 @@ To delete a stack set, you must first delete all stacks in the stack set. For in - 5. When you are prompted to confirm that you want to delete the stack set, choose **Delete StackSet**. + 5. When you are prompted to confirm that you want to delete the StackSet, choose **Delete StackSet**. @@ -37 +39 @@ To delete a stack set, you must first delete all stacks in the stack set. For in -## Delete a stack set (AWS CLI) +## Delete a StackSet (AWS CLI) @@ -39 +41 @@ To delete a stack set, you must first delete all stacks in the stack set. For in -When acting as a delegated administrator, you must set the `--call-as` option to `DELEGATED_ADMIN` each time you run a stack set command. +###### Note @@ -40,0 +43 @@ When acting as a delegated administrator, you must set the `--call-as` option to +When acting as a delegated administrator, you must include `--call-as DELEGATED_ADMIN` in the command. @@ -42 +45 @@ When acting as a delegated administrator, you must set the `--call-as` option to - --call-as DELEGATED_ADMIN +###### To delete a StackSet @@ -48 +51 @@ When acting as a delegated administrator, you must set the `--call-as` option to - 2. Verify that the stack set was deleted by running the **list-stack-sets** command. The results of the list-stack-sets command should show your stack with a status of `DELETED`. + 2. Verify that the StackSet was deleted by running the **list-stack-sets** command. The results of the list-stack-sets command should show your stack with a status of `DELETED`. @@ -57 +60 @@ When acting as a delegated administrator, you must set the `--call-as` option to -If you no longer need the IAM service roles that CloudFormation requires to perform stack set operations, we recommend that you delete the roles. +If you no longer need the IAM service roles that CloudFormation requires to perform StackSet operations, we recommend that you delete the roles. @@ -61 +64 @@ _For self-managed StackSets_ , the roles you created. For more information about -_For service-managed StackSets_ , the roles that were automatically created by StackSets have the suffix `CloudFormationStackSetsOrgAdmin` in the organization management account, and `CloudFormationStackSetsOrgMember` in each target account. For more information, see [Service-linked roles](./stacksets-orgs-activate-trusted-access.html#stacksets-orgs-service-linked-roles). +_For service-managed StackSets_ , the roles that were automatically created for StackSets have the suffix `CloudFormationStackSetsOrgAdmin` in the organization management account, and `CloudFormationStackSetsOrgMember` in each target account. For more information, see [Service-linked roles](./stacksets-orgs-activate-trusted-access.html#stacksets-orgs-service-linked-roles).