Re:AWS CloudFormation Best Practices
by SteveNuts on Wednesday March 31, 2021 @01:50PM
(#26650541)
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.
[ Parent
| on HN ]
Not 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/UserGui...
Re:AWS CloudFormation Best Practices
by guitarbill on Wednesday March 31, 2021 @02:58PM
(#26651484)
If 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/UserGui...
Re:AWS CloudFormation Best Practices
by CyberDildonics on Wednesday March 31, 2021 @03:22PM
(#26651824)
Invested in what?
Re:AWS CloudFormation Best Practices
by guitarbill on Wednesday March 31, 2021 @03:31PM
(#26651950)
Cloudformation
This 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?!
Re:AWS CloudFormation Best Practices
by bassdropvroom on Wednesday March 31, 2021 @01:57PM
(#26650641)
For 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.