How can the user configure this?
The user can use the DependentCondition resource to hold the creation of the other dependent resources.
It is not possible that the stack creation will wait until one service is created and launched.
The user can use the HoldCondition resource to wait for the creation of the other dependent resources.
The user can use the WaitCondition resource to hold the creation of the other dependent resources.
Explanations:
There is no “DependentCondition” resource in CloudFormation. The correct resource for creating dependencies is the “WaitCondition” resource.
While CloudFormation has inherent dependencies based on resource references, it does allow for explicit waits using WaitCondition resources to control the creation order.
“HoldCondition” is not a valid resource type in CloudFormation. The correct mechanism to wait for a resource to be ready is using “WaitCondition.”
The “WaitCondition” resource allows the user to wait for an external signal before proceeding with the creation of dependent resources, ensuring that the EC2 instance is fully configured before the ELB and AutoScaling resources are created.
In my experience, the answer is:
The user can use the WaitCondition resource to hold the creation of the other dependent resources.
I believe the answer is:
The user can use the WaitCondition resource to hold the creation of the other dependent resources.