3 ms·
> If you ever dealt with cloudformation you’d know it’s absolutely enormous PITA. Is it? For me it's working fine. What problems are you facing when writing C
by Dunedan 6y ago
> If you ever dealt with cloudformation you’d know it’s absolutely enormous PITA.
Is it? For me it's working fine.
What problems are you facing when writing CloudFormation templates and what better alternative to declare infrastructure do you suggest?
Most problems I see are people being not aware of the possible attributes of resources or doing indentation mistakes when it's a YAML template. Most of these problems can be avoided by using cfn-lint [1] to ensure the template is valid.
[1]: https://github.com/aws-cloudformation/cfn-python-lint https://github.com/aws-cloudformation/cfn-python-lint
- nitrogen 6y agoGoing from something like Puppet with a few VPSes to CloudFormation with serverless is a huge jump in complexity and boilerplate.
- dmarinus 6y agoCloudFormation is slow (custom resources take hours to time out), it's unpredictable (behavior is different for different services). I wish it didn't use stacks (drift happens and can only be fixed manually) and was just idempotent like ansible. It also doesn't come with sane defaults so you have to supply a load of boilerplate code (cdk fixes this using constructs).