💾 Archived View for cfdocs.wetterberg.nu › resource-import-nested-stacks.gemini captured on 2024-05-12 at 16:00:27. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Nesting an existing stack

Use the `resource import` feature to nest an existing stack within another existing stack. Nested stacks are common components that you declare and reference from within other templates. That way, you can avoid copying and pasting the same configurations into your templates and simplify stack updates. If you have a template for a common component, you can use the `AWS::CloudFormation::Stack` resource to reference this template from within another template. For more information on nested stacks, see Working with nested stacks.

Working with nested stacks

AWS CloudFormation only supports one level of nesting using `resource import`. This means that you cannot import a stack into a child stack or import a stack that has children.

Nested stack import validation

During a nested stack import operation, AWS CloudFormation performs the following validations.

The nested AWS::CloudFormation::Stack definition in the parent stack template matches the actual nested stack's template.
The tags for the nested AWS::CloudFormation::Stack definition in the parent stack template match the tags for the actual nested stack resource.

Nest an existing stack using the AWS Management Console

Add the AWS::CloudFormation::Stack resource to the parent stack template with a Retain DeletionPolicy. In the following example parent template, NestedStack is the target of the import.
Open the AWS CloudFormation console.
On the Stacks page, with the parent stack selected, choose Stack actions, and then choose Import resources into stack.[The Import resources into stack option in the console.]
Read the Import overview page for a list of things you're required to provide during this operation. Then, choose Next.
On the Specify template page, provide the updated parent template using one of the following methods, and then choose Next.Choose Amazon S3 URL, and then specify the URL for your template in the text box.Choose Upload a template file, and then browse for your template.
On the Identify resources page, identify the AWS::CloudFormation::Stack resource.Under Identifier property, choose the type of resource identifier. For example, an AWS::CloudFormation::Stack resource can be identified using the StackId property.Under Identifier value, type the actual property value. For example, arn:aws:cloudformation:us-west-2:12345678910:stack/mystack/5b918d10-cd98-11ea-90d5-0a9cd3354c10.[The Identify resources page in the console.]Choose Next.
On the Specify stack details page, modify any parameters, and then choose Next. This automatically creates a change set.ImportantThe import operation fails if you modify existing parameters that trigger a create, update, or delete operation.
On the Review stack-name page, confirm that the correct resource is being imported, and then choose Import resources. This automatically executes the change set created in the last step. Any stack-level tags are applied to imported resources at this time.
The Events pane of the Stack details page for your parent stack displays.[The Events tab in the console.]NoteIt's not necessary to run drift detection on the parent stack after this import operation because the AWS::CloudFormation::Stackresource was already managed by AWS CloudFormation.

DeletionPolicy

stack-level tags

Nest an existing stack using the AWS CLI

Add the AWS::CloudFormation::Stack resource to the parent stack template with a Retain DeletionPolicy. In the following example parent template, NestedStack is the target of the import.
Create a change set of type IMPORT with the following parameters. --resources-to-import does not support inline YAML.The AWS CLI also supports text files as input for the resources-to-import parameter, as shown in the following example.In this walkthrough, file://resourcesToImport.txt contains the following.
Review the change set to make sure the correct stack is being imported.
Execute the change set to import stack into the source parent stack. Any stack-level tags are applied to imported resources at this time. On successful completion of the import operation (IMPORT_COMPLETE), the stack is successfully nested.

DeletionPolicy

stack-level tags

Note*

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.