Skip to content

8.3 Config Stack Pattern #2

@alytle

Description

@alytle

8.3 The config stack pattern involves a single stack used as a configuration source. This stack is used to export configuration values that will then be imported by other stacks. This is particularly useful for resource name values or other external configuration items. A single AWS::CloudFormation::WaitConditionHandle resource can be created as a dummy resource to allow the template to validate and the stack to create.

This is a really interesting idea, but how viable is it? These configuration parameters would be immutable after they were imported at least once, right? So it would work for things that are common across all the stacks that make up the app, such as Environment/Stage, Application Name, maybe some Tags?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions