AWS AWSCloudFormation documentation change
Summary
Multiple replacements of 'AWS CloudFormation' with 'CloudFormation' and updated console reference
Security assessment
Branding updates and clarification about stack management. No security-specific changes.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/resource-import-nested-stacks.md b/AWSCloudFormation/latest/UserGuide/resource-import-nested-stacks.md index 22a488f1c..674179f74 100644 --- a//AWSCloudFormation/latest/UserGuide/resource-import-nested-stacks.md +++ b//AWSCloudFormation/latest/UserGuide/resource-import-nested-stacks.md @@ -11 +11 @@ Use the `resource import` feature to nest an existing stack within another exist -AWS CloudFormation only supports one level of nesting using `resource import`. This means that you can't import a stack into a child stack or import a stack that has children. +CloudFormation only supports one level of nesting using `resource import`. This means that you can't import a stack into a child stack or import a stack that has children. @@ -17 +17 @@ If you're new to importing, we recommend that you first review the introductory -During a nested stack import operation, AWS CloudFormation performs the following validations. +During a nested stack import operation, CloudFormation performs the following validations. @@ -98 +98 @@ During a nested stack import operation, AWS CloudFormation performs the followin - 2. Open the AWS CloudFormation console. + 2. Open the CloudFormation console. @@ -136 +136 @@ The import operation fails if you modify existing parameters that initiate a cre -It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack` resource was already managed by AWS CloudFormation. +It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack` resource was already managed by CloudFormation. @@ -278 +278 @@ If successful, this command returns the following sample output. -It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack` resource is already managed by AWS CloudFormation. +It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack` resource is already managed by CloudFormation.