4 ms·
1. This is true, but also valid of other cloud provisioning tools. Some operations just take a long time. Using things like DependsOn and template validation he
by nunez 11y ago
1. This is true, but also valid of other cloud provisioning tools. Some operations just take a long time. Using things like DependsOn and template validation help decrease provisioning time.
2. If you check the events that happened in the CloudFormation console or by running "aws cloudformation describe-stack-events", you'll see where things went sideways pretty easily (unless you're using nested stacks, in which case debugging can take a bit longer.)
3. I can't say that that's happened too often for us, and we've deployed quite a few stacks so far.
4. Your stacks shouldn't be super long. If you're using Designer to create your template (which I personally don't do), removing the position metadata can save you lots of lines depending on the number of resources you have. Also, you might be mixing in parts of your infrastructure that should really live in their own stacks (I.e. Not creating web servers in your VPC/networking stack). Consider using nested stacks to help you organize this.
5. What do you mean? Tagging is supported by most CF resources (and AWS is adding support for more as the product matures)