Always trigger stack rerun on update
I have a CFN root stack with nested stacks in it, one of which is essentially a lambda function. I want that nested stack to run on any update triggered on the root stack. It may be possible that there is no parameter/template changes to this nested stack, but I still want to rerun it.
detailed use-case: The nested stack retrieves details about a VPC and produces outputs based on that. While the inputs to this stack may not have changed, the outputs may change based on changes in the VPC. Therefore I need a way to tell AWS to ALWAYS
run this stack in case of updates.
I can think of two ways to achieve this.
First Set the lambda up as an cloudwatch rule which is triggered by this specific stack update - I believe this would have to be a "AWS API Call via CloudTrail" event. Your nested stack would create the cloudwatch rule and potentially run the lambda on the initial creation. But I don't think this will work in your case as you need the output within the stack on the update
Second - one I have used multiple times Create a parameter to the parent stack, pass to nested stack and add as a environment var within your lambda. When I have used this method I usually triggered via a pipeline so I make the parameter the pipeline-execution-id so it changes on every execution.
Relevant questions
Restore deleted nested stack
asked 4 months agoNested Stack failed to rollback
asked 4 months agoHow to share one dynamo db table with multiple stacks?
asked 3 days agoCFM stack is stuck after failure deleting Beanstalk app
Accepted Answerasked 3 months agoCloudFormation structuring & splitting of resources between stacks
Accepted Answerasked 2 years agoAlways trigger stack rerun on update
asked 2 months agoUpdating CFN stack over multiple accounts
Accepted AnswerStack deletion deletes log group but re-creates it on lambda invocation
asked 2 years agoCloudformation Stack stuck in Update_Rollback_Failed State because of nested stack Update_Rollback_Failed
asked 3 months agoLambda Functions raise forbidden error until stack deleted and redeployed
asked 2 years ago