Likewise, CF is the leading cause of outages in our infrastructure. We've completely abandon it in favor of Terraform.
* CF gets deadlocked if resources are changed outside of it, and there's no way to prevent people from doing that either
* No concept of a rolling update to a fleet or any warning it's going to cause an outage with out having to dig through fine print in the docs on every single change, just terminates all the EC2 instances in an ASG/ELB in some cases
* If you have a template, remember any change you make to that template has to be applied to every single stack you have, otherwise you'll either damage something or deadlock the stack when updating it later, it can't figure out what's deployed on it's own and maintains its own state that can be different from the real state. We had to stop using templates at all and just store a copy of each template in our local git repo.
* If you have more than 100 stacks searching the list of stacks requires clicking a handful of times on the "show more stacks" button before it'll show the one you typed in
* Stupid slow, esp. compared to Terraform
* Doesn't delete Route53 DNS records even after saying it does in the log outout
* Can break ELB configurations, such as sticky sessions and cause outages
* Doesn't actually support deploying all AWS resources, SNS/SQS perms/rules aren't complete for example.
* CF gets deadlocked if resources are changed outside of it, and there's no way to prevent people from doing that either
* No concept of a rolling update to a fleet or any warning it's going to cause an outage with out having to dig through fine print in the docs on every single change, just terminates all the EC2 instances in an ASG/ELB in some cases
* If you have a template, remember any change you make to that template has to be applied to every single stack you have, otherwise you'll either damage something or deadlock the stack when updating it later, it can't figure out what's deployed on it's own and maintains its own state that can be different from the real state. We had to stop using templates at all and just store a copy of each template in our local git repo.
* If you have more than 100 stacks searching the list of stacks requires clicking a handful of times on the "show more stacks" button before it'll show the one you typed in
* Stupid slow, esp. compared to Terraform
* Doesn't delete Route53 DNS records even after saying it does in the log outout
* Can break ELB configurations, such as sticky sessions and cause outages
* Doesn't actually support deploying all AWS resources, SNS/SQS perms/rules aren't complete for example.