CloudFormation嵌套栈子栈间参数引用ValidationError排查求助

Let's break down why you're hitting this ValidationError even after adding a DependsOn clause, and walk through the fixes you need:

1. First: Understand the Difference Between DependsOn and Cross-Stack References #

DependsOn controls the order in which CloudFormation creates resources, but it doesn't solve the core issue here: your EC2InstanceResourcesStack is trying to reference a resource from StepFunctionResourcesStack without using the proper cross-stack export/import mechanism.

CloudFormation validates the template structure before it starts creating any resources. If you're directly referencing the BatchScatterGatherSubmissionActivity by name (instead of using Fn::ImportValue), the validator won't recognize it because that resource lives in a separate nested stack.

2. Fix the Cross-Stack Reference Setup #

You need to set up an export in the StepFunctionResourcesStack and an import in the EC2InstanceResourcesStack:

Step A: Add an Export to StepFunctionResourcesStack #

In your StepFunctionResourcesStack template, define an output for the Activity's ARN (or whatever attribute you need to reference) with an Export field:

Outputs:
  BatchScatterGatherSubmissionActivityArn:
    Value: !Ref BatchScatterGatherSubmissionActivity
    Export:
      Name: !Sub "${AWS::StackName}-BatchScatterGatherSubmissionActivityArn"

Using !Sub with ${AWS::StackName} ensures the export name is unique and tied to the actual nested stack name (critical if you ever deploy multiple instances of your parent stack).

Step B: Use Fn::ImportValue in EC2InstanceResourcesStack #

In the EC2InstanceResourcesStack template, replace any direct references to the Activity with:

!ImportValue StepFunctionResourcesStack-BatchScatterGatherSubmissionActivityArn

Note: If your parent template uses a dynamic name for the StepFunctionResourcesStack (e.g., via a parameter), you'll need to use !Sub here too, like:

!ImportValue !Sub "${ParentStackParameter}-BatchScatterGatherSubmissionActivityArn"

3. Verify Your DependsOn is Applied Correctly #

Make sure the DependsOn is added to the nested stack resource in your parent template, not to a resource inside the EC2InstanceResourcesStack. Here's how it should look in the parent template:

Resources:
  StepFunctionResourcesStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: s3://your-bucket/path/to/StepFunctionResourcesStack.yaml
      # ... other properties

  EC2InstanceResourcesStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: s3://your-bucket/path/to/EC2InstanceResourcesStack.yaml
      # ... other properties
    DependsOn: StepFunctionResourcesStack

This tells CloudFormation to fully create the StepFunctionResourcesStack (and its exports) before starting on EC2InstanceResourcesStack.

4. Debug with Template Validation #

Run the CLI validation command to get a precise error message:

aws cloudformation validate-template --template-body file://path/to/your-parent-template.yaml

This will point you exactly to where the reference is failing—whether it's a misspelled export name, missing Export field, or incorrect ImportValue syntax.

5. Double-Check for Typos & Case Sensitivity #

CloudFormation is case-sensitive, so make sure:

• The export name in StepFunctionResourcesStack matches exactly what you're importing in EC2InstanceResourcesStack
• The resource name BatchScatterGatherSubmissionActivity is spelled correctly in both templates

内容的提问来源于stack exchange，提问作者claudiadast