AWS AWSCloudFormation documentation change
Summary
Updated documentation links, YAML syntax formatting, added operational guidance for nested stack updates, and clarified rollback behavior
Security assessment
Changes include URL updates, YAML syntax normalization (removing quotes from non-string values), and operational guidance improvements. The added note about nested stacks blocking root stack operations during rollback states is a best practice clarification but doesn't address a specific security vulnerability. The IAM permissions reminder references existing documentation without introducing new security controls.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.md b/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.md index a570144dc..347d0a5ae 100644 --- a//AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.md +++ b//AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.md @@ -0,0 +1,2 @@ +[](/pdfs/AWSCloudFormation/latest/UserGuide/cfn-ug.pdf#using-cfn-nested-stacks "Open PDF") + @@ -7 +9 @@ Before and after example of splitting a templateExample of a nested stack archit -As your infrastructure grows, you might find yourself repeatedly creating identical resource configurations across multiple templates. To avoid this redundancy, you can separate these common configurations into dedicated templates. Then, you can use the [AWS::CloudFormation::Stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudformation-stack.html) resource in other templates to reference these dedicated templates, creating nested stacks. +As your infrastructure grows, you might find yourself repeatedly creating identical resource configurations across multiple templates. To avoid this redundancy, you can separate these common configurations into dedicated templates. Then, you can use the [AWS::CloudFormation::Stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-cloudformation-stack.html) resource in other templates to reference these dedicated templates, creating nested stacks. @@ -45 +47 @@ Before nesting stacks | After nesting stacks - AWSTemplateFormatVersion: '2010-09-09' + AWSTemplateFormatVersion: 2010-09-09 @@ -49,2 +51,2 @@ Before nesting stacks | After nesting stacks - Default: 't2.micro' - Description: 'The EC2 instance type' + Default: t2.micro + Description: The EC2 instance type @@ -54,2 +56,2 @@ Before nesting stacks | After nesting stacks - Default: 'Production' - Description: 'The deployment environment' + Default: Production + Description: The deployment environment @@ -70 +72 @@ Before nesting stacks | After nesting stacks - AWSTemplateFormatVersion: '2010-09-09' + AWSTemplateFormatVersion: 2010-09-09 @@ -75 +77 @@ Before nesting stacks | After nesting stacks - TemplateURL: 'https://s3.amazonaws.com/amzn-s3-demo-bucket/first-nested-stack.yaml' + TemplateURL: https://s3.amazonaws.com/amzn-s3-demo-bucket/first-nested-stack.yaml @@ -78 +80 @@ Before nesting stacks | After nesting stacks - InstanceType: 't3.micro' + InstanceType: t3.micro @@ -83 +85 @@ Before nesting stacks | After nesting stacks - TemplateURL: 'https://s3.amazonaws.com/amzn-s3-demo-bucket/second-nested-stack.yaml' + TemplateURL: https://s3.amazonaws.com/amzn-s3-demo-bucket/second-nested-stack.yaml @@ -86 +88 @@ Before nesting stacks | After nesting stacks - Environment: 'Testing' + Environment: Testing @@ -119 +121 @@ The following example shows the format of the nested stack template. - Description: Lambda function memory allocation + Description: Lambda function memory allocation (128-10240 MB) @@ -222,3 +224 @@ After you run the **package** command, you can deploy the processed template usi -With nested stacks, you need to be careful and handle the nested stacks correctly when doing certain actions. Some stack operations, such as stack updates, should be initiated from the root stack rather than performed directly on nested stacks themselves. Additionally, sometimes the presence of the nested stacks can affect how operations on the root stack are performed. - -When you update a root stack, only nested stacks with template changes will be modified. All other nested stacks remain unchanged. +When working with nested stacks, you must handle them carefully during operations. Certain stack operations, such as stack updates, should be initiated from the root stack rather than performed directly on the nested stacks. When you update a root stack, only nested stacks with template changes will be updated. @@ -226 +226 @@ When you update a root stack, only nested stacks with template changes will be m -Before proceeding with update operations, make sure that you have IAM permissions to cancel a stack update in case it rolls back. For more information, see [Control CloudFormation access with AWS Identity and Access Management](./control-access-with-iam.html). +Additionally, the presence of the nested stacks can affect operations on the root stack. For example, if one nested stack becomes stuck in `UPDATE_ROLLBACK_IN_PROGRESS` state, the root stack will wait until that nested stack completes its rollback before continuing. Before proceeding with update operations, make sure that you have IAM permissions to cancel a stack update in case it rolls back. For more information, see [Control CloudFormation access with AWS Identity and Access Management](./control-access-with-iam.html).