CloudFormation条件嵌套栈引用输出报Unresolved资源依赖如何解决

CloudFormation 会在执行条件判断逻辑前，先全局扫描模板解析所有资源依赖关系。只要模板内出现对某资源的引用（比如你写的!GetAtt DB.Outputs.RDSEndPointAddress），无论该引用是否在!If的非生效分支中，都会被加入依赖列表。当CreateDB条件为false时，DB嵌套栈不会被创建，依赖列表中的DB资源就会不存在，因此触发未解析依赖报错。

方法1：SSM Parameter Store中转（更简洁） #

新增一个SSM参数资源统一存储DB端点，该资源无论条件是否成立都会被创建，LaunchConfig中直接引用该SSM参数即可，无需拆分资源：

Parameters:
  DBExistingEndpoint:
    Type: String
    Description: Set to a URL of a RDS instance to use an existing DB, otherwise create one
    Default: ''
...

Conditions:
  CreateDB:
    !Equals [!Ref DBExistingEndpoint, '']
...

Resources:
  # 原有DB嵌套栈不变
  DB:
    Type: AWS::CloudFormation::Stack
    Condition: CreateDB
    Properties:
      TemplateURL: ...

  # 新增SSM参数统一存储端点
  DBEndpointParam:
    Type: AWS::SSM::Parameter
    Properties:
      Type: String
      Value: !If [CreateDB, !GetAtt DB.Outputs.RDSEndPointAddress, !Ref DBExistingEndpoint]

  # 启动配置直接引用SSM参数
  ClusterInstanceLaunchConfig:
    Type: AWS::AutoScaling::LaunchConfiguration
    Metadata:
      AWS::CloudFormation::Init:
        config:
          files:
            /etc/dbenv:
              mode: "000640"
              owner: root
              group: root
              content:
                !Join
                  - "\n"
                  -
                    - !Sub "DB_HOST=${DBEndpointParam}"
                  ...

方法2：按条件拆分启动配置（兼容性最好） #

定义两份启动配置，分别对应创建新DB和使用现有DB的场景，再在Auto Scaling组中通过条件选择对应配置，完全规避对可能不存在资源的引用：

Parameters:
  DBExistingEndpoint:
    Type: String
    Description: Set to a URL of a RDS instance to use an existing DB, otherwise create one
    Default: ''
...

Conditions:
  CreateDB:
    !Equals [!Ref DBExistingEndpoint, '']
  UseExistingDB: !Not [!Condition CreateDB]
...

Resources:
  # 原有DB嵌套栈不变
  DB:
    Type: AWS::CloudFormation::Stack
    Condition: CreateDB
    Properties:
      TemplateURL: ...

  # 新建DB场景用的启动配置
  ClusterInstanceLaunchConfig_NewDB:
    Type: AWS::AutoScaling::LaunchConfiguration
    Condition: CreateDB
    Metadata:
      AWS::CloudFormation::Init:
        config:
          files:
            /etc/dbenv:
              mode: "000640"
              owner: root
              group: root
              content:
                !Join
                  - "\n"
                  -
                    - !Sub "DB_HOST=${DB.Outputs.RDSEndPointAddress}"
                  ...

  # 使用现有DB场景用的启动配置
  ClusterInstanceLaunchConfig_ExistingDB:
    Type: AWS::AutoScaling::LaunchConfiguration
    Condition: UseExistingDB
    Metadata:
      AWS::CloudFormation::Init:
        config:
          files:
            /etc/dbenv:
              mode: "000640"
              owner: root
              group: root
              content:
                !Join
                  - "\n"
                  -
                    - !Sub "DB_HOST=${DBExistingEndpoint}"
                  ...

  # Auto Scaling组按条件选择启动配置
  ASG:
    Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      LaunchConfigurationName: !If [CreateDB, !Ref ClusterInstanceLaunchConfig_NewDB, !Ref ClusterInstanceLaunchConfig_ExistingDB]
      # 其余ASG配置保持不变
      ...

内容的提问来源于stack exchange，提问作者shonky linux user