When I create an AWS CloudFormation resource of type AWS::RDS::DBInstance and specify DeletionPolicy: Delete in the template, I get the following error in the CloudFormation Stacks console:

I want to use multiple templates which will have multiple templates file directory and structure in cloudformation I don’t want to use s3 bucket cause there will be multiple files later and I will use ci-cd pipeline to deploy my changes this is my file i am trying to deploy in cloudformation

AWS CloudFormation has a feature for creating a reusable module which is stored in the CloudFormation registry. In the registry, one can view the default version as well as the schema of that version for a given module.

I have Cloudformation with multiple nested stack templates. In the below sample, I want to create the Route53 resources after the load balancers have been created so I put DependsOn LOADBALANCER stack to ensure the nested templates are created in order. This works. However, if I already have everything created and do an update by changing the “CreatePrivateLoadbalancer” parameter to false, the stack update fails because it tries to delete the PrivateLoadbalancer first, but it cannot because ROUTE53 stack is using the output of PrivateLoadbalancer. Ideally, it should delete the ROUTE53 resource first then delete the LOADBALANCER resource. Any suggestions?

Can someone help me find a solution to this circular dependency?
And explain why this error occurs?

This is not a question of getting out of UPDATE_ROLLBACK_FAILED, but getting into it.