AWS AWSCloudFormation documentation change
Summary
Updated documentation formatting, terminology consistency (e.g., 'StackSet' capitalization), link references, and CLI command formatting. Removed redundant 'AWS' prefix from CloudFormation references and adjusted troubleshooting steps for clarity.
Security assessment
Changes are primarily stylistic improvements and documentation structure updates. The mention of termination protection (a security feature) was already present and only received formatting changes. No new security vulnerabilities or mitigations are introduced.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/stacksets-troubleshooting.md b/AWSCloudFormation/latest/UserGuide/stacksets-troubleshooting.md index d362fa9e0..1d2ac424a 100644 --- a//AWSCloudFormation/latest/UserGuide/stacksets-troubleshooting.md +++ b//AWSCloudFormation/latest/UserGuide/stacksets-troubleshooting.md @@ -9 +9 @@ Common reasons for stack operation failureRetrying failed stack creation or upda -This topic contains some common AWS CloudFormation StackSets issues, and suggested solutions for those issues. +This topic contains some common StackSets issues, and suggested solutions for those issues. @@ -28 +28 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest -**Problem:** A stack operation failed, and the stack instance status is `OUTDATED`. +Problem: A stack operation failed, and the stack instance status is `OUTDATED`. @@ -30 +30 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest -**Cause:** There can be several common causes for stack operation failure. +Cause: There can be several common causes for stack operation failure. @@ -34 +34 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest - * The AWS CloudFormation template might have errors. Validate the template in AWS CloudFormation and fix errors before trying to create your stack set. + * The CloudFormation template might have errors. Validate the template in CloudFormation and fix errors before trying to create your StackSet. @@ -44 +44 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest - * You have reached the maximum number of stacks that are allowed in a stack set. See [AWS CloudFormation limits](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html) for the maximum number of stacks per stack set. + * You have reached the maximum number of stacks that are allowed in a StackSet. For the maximum number of stacks per StackSet, see [Understand CloudFormation quotas](./cloudformation-limits.html). @@ -49 +49 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest -**Solution:** For more information about the permissions required of target and administrator accounts before you can create stack sets, see [Give all users of the administrator account permissions to manage stacks in all target accounts](./stacksets-prereqs-self-managed.html#stacksets-prereqs-accountsetup). +Solution: For more information about the permissions required of target and administrator accounts before you can create StackSets, see [Give all users of the administrator account permissions to manage stacks in all target accounts](./stacksets-prereqs-self-managed.html#stacksets-prereqs-accountsetup). @@ -53 +53 @@ This topic contains some common AWS CloudFormation StackSets issues, and suggest -**Problem:** A stack creation or update failed, and the stack instance status is `OUTDATED`. To troubleshoot why a stack creation or update failed, open the AWS CloudFormation console, and view the events for the stack, which will have a status of `DELETED` (for failed create operations) or `FAILED` (for failed update operations). Browse the stack events, and find the **Status reason** column. The value of **Status reason** explains why the stack operation failed. +Problem: A stack creation or update failed, and the stack instance status is `OUTDATED`. To troubleshoot why a stack creation or update failed, open the CloudFormation console, and view the events for the stack, which will have a status of `DELETED` (for failed create operations) or `FAILED` (for failed update operations). Browse the stack events, and find the **Status reason** column. The value of **Status reason** explains why the stack operation failed. @@ -57 +57 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Solution:** Perform the following steps to retry your stack operation. +Solution: Perform the following steps to retry your stack operation. @@ -59 +59 @@ After you have fixed the underlying cause of the stack creation failure, and you - 1. In the console, select the stack set that contains the stack on which the operation failed. + 1. In the console, select the StackSet that contains the stack on which the operation failed. @@ -63 +63 @@ After you have fixed the underlying cause of the stack creation failure, and you - 3. On the **Specify template** page, to use the same AWS CloudFormation template, keep the default option, **Use current template**. If your stack operation failed because the template required changes, and you want to upload a revised template, choose **Upload a template to Amazon S3** instead, and then choose **Browse** to select your updated template. When you are finished uploading your revised template, choose **Next**. + 3. On the **Specify template** page, to use the same CloudFormation template, keep the default option, **Use current template**. If your stack operation failed because the template required changes, and you want to upload a revised template, choose **Upload a template to Amazon S3** instead, and then choose **Browse** to select your updated template. When you are finished uploading your revised template, choose **Next**. @@ -67 +67 @@ After you have fixed the underlying cause of the stack creation failure, and you - 5. On the **Set deployment options** page, change defaults for **Maximum concurrent accounts** and **Failure tolerance** , if desired. For more information about these settings, see [Stack set operation options](./what-is-cfnstacksets.html#stackset-ops-options). + 5. On the **Set deployment options** page, change defaults for **Maximum concurrent accounts** and **Failure tolerance** , if desired. For more information about these settings, see [StackSet operation options](./stacksets-concepts.html#stackset-ops-options). @@ -78 +78 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Problem:** A stack deletion has failed. +Problem: A stack deletion has failed. @@ -80 +80 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Cause:** Stack deletion will fail for any stacks on which termination protection has been enabled. +Cause: Stack deletion will fail for any stacks on which termination protection has been enabled. @@ -82 +82 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Solution:** Determine if termination protection has been enabled for the stack. If it has, disable termination protection and then perform the stack instance deletion again. +Solution: Determine if termination protection has been enabled for the stack. If it has, disable termination protection and then perform the stack instance deletion again. @@ -86 +86 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Problem:** A stack import operation fails to import existing stacks into new or existing stack sets. The stack instance is in an `INOPERABLE` status. +Problem: A stack import operation fails to import existing stacks into new or existing StackSets. The stack instance is in an `INOPERABLE` status. @@ -88 +88 @@ After you have fixed the underlying cause of the stack creation failure, and you -**Solution:** Revert the stack import operation, by completing the following tasks. +Solution: Revert the stack import operation, by completing the following tasks. @@ -90 +90 @@ After you have fixed the underlying cause of the stack creation failure, and you - 1. Use **Delete Stacks from StackSets** option and enable **RetainStacks** during configuration, then proceed to delete stack instances from your stack set. For more information, For more information, see [Delete stacks from CloudFormation StackSets ](./stackinstances-delete.html). + 1. Use **Delete Stacks from StackSets** option and enable **RetainStacks** during configuration, then proceed to delete stack instances from your StackSet. For more information, For more information, see [Delete stacks from AWS CloudFormation StackSets ](./stackinstances-delete.html). @@ -92 +92 @@ After you have fixed the underlying cause of the stack creation failure, and you - 2. You will see the stack instance of the Stackset are updated to remove the `INOPERABLE` stack instance. + 2. You will see the stack instances of the StackSet are updated to remove the `INOPERABLE` stack instance. @@ -120 +120 @@ You can use the AWS Management Console, AWS SDK, or AWS CLI to get the failure c - 1. Open the [AWS CloudFormation console](https://console.aws.amazon.com/cloudformation) and choose **StackSets**. + 1. Open the [CloudFormation console](https://console.aws.amazon.com/cloudformation) and choose **StackSets**. @@ -152 +152 @@ To get the number of failed stack instances, call `describe-stack-set-operation` - $ aws cloudformation describe-stack-set-operation --stack-set-name ss1 \ + aws cloudformation describe-stack-set-operation --stack-set-name ss1 \ @@ -204 +204,2 @@ To get a historical overview for a particular operation, use `list-stack-set-ope - aws cloudformation list-stack-set-operation-results --stack-set-name ss1 --operation-id 5550e62f-c822-4331-88fa-21c1d7bafc60 --filters Name=OPERATION_RESULT_STATUS,Values=FAILED + aws cloudformation list-stack-set-operation-results --stack-set-name ss1 \ + --operation-id 5550e62f-c822-4331-88fa-21c1d7bafc60 --filters Name=OPERATION_RESULT_STATUS,Values=FAILED @@ -248 +249,2 @@ Use `list-stack-instances` with the `DETAILED_STATUS` and `LAST_OPERATION_ID` fi - aws cloudformation list-stack-instances --stack-set-name ss1 --filters Name=DETAILED_STATUS,Values=FAILED Name=LAST_OPERATION_ID,Values=5550e62f-c822-4331-88fa-21c1d7bafc60 + aws cloudformation list-stack-instances --stack-set-name ss1 \ + --filters Name=DETAILED_STATUS,Values=FAILED Name=LAST_OPERATION_ID,Values=5550e62f-c822-4331-88fa-21c1d7bafc60 @@ -298 +300,2 @@ To find the last operation ID to modify a stack instance, use `list-stack-instan - aws cloudformation describe-stack-instance --stack-set-name ss1 --stack-instance-account 123456789012 --stack-instance-region us-east-2 + aws cloudformation describe-stack-instance --stack-set-name ss1 \ + --stack-instance-account 123456789012 --stack-instance-region us-east-2