4 ms·
The only problem is Cloudformation is strictly AWS resources, so unless you're absolutely 100% sure you'll never need anything outside of AWS ecosystem, I alway
by SteveNuts 6y ago
The only problem is Cloudformation is strictly AWS resources, so unless you're absolutely 100% sure you'll never need anything outside of AWS ecosystem, I always recommend using TF.
- nikolay 6y agoThis is true, of course, but you can have a Terraform CloudFormation resource, too, and pass data from other resources back and forth. Since when we don't like using the best tool for the job?!
- bassdropvroom 6y agoFor companies the likelihood of not needing stuff outside of AWS is relatively low. Unless you're okay with managing other applications by hand, which is probably the wrong attitude.
- Varriount 6y agoNot quite true, you can technically create your own CloudFormation resources[0]. It's a pain to do though. [0] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
- guitarbill 6y agoIf you're invested, you can use extensions [0] which seem like they're more well-defined. It sounds like this is what APN partners like Datadog use to implement 3rd party resources. [0] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
- CyberDildonics 6y agoInvested in what?
- guitarbill 6y agoCloudformation