0

I have multiple CloudFormation stacks with serial dependencies (Stack A2 depends on Stack A1, etc.).
I've noticed a pattern during stack updates where CloudFormation appears to report the UPDATE_COMPLETE status in reverse dependency order.

Looking at the CloudFormation timeline:

  1. Parent stack reaches UPDATE_COMPLETE_CLEANUP_IN_PROGRESS
  2. Child stacks report UPDATE_COMPLETE in reverse dependency order
  3. For example, if A2 depends on A1:
    • A1 updates first (as expected)
    • A2 updates next (as expected)
    • A2 reports UPDATE_COMPLETE first
    • A1 reports UPDATE_COMPLETE last

These are sibling stacks (not nested), with DependsOn between them.

Adding a snippet of Cloudformation's TimeLine view: Reverse success reports

The top most bar is the latest stack.
The green blocks are each stack reporting success.

Improve this question
Related questions
192
ValidationError Stack:arn aws cloudformation stack is in ROLLBACK_COMPLETE state and can not be updated
2
AWS Codepipeline does not update my ECS Cluster
99
AWS CloudFormation Stack update error: Requires capabilities : [CAPABILITY_IAM]
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.