TL;DR If you don’t need to codify non-AWS infrastructure then stick to Cloud Formation.
If you maintain use multiple cloud vendors (Azure, AWS) then you don’t need to learn those vendors specific Infrastructure as Code solutions (ARM, Cloud Formation)
Also if you’re orchestrating more than just AWS resources (Okta), then it make sense to use Terraform.
These are great points Mark! I use both, and they are both great products. One is not better than the other, just better suited for different scenarios.
I will add that, you might also consider vendor support. If, for example, you are building a SaaS offering largely on AWS, you might give preference to Cloud Formation as that is what the AWS support staff and AWS architects will be familiar with.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
TL;DR If you don’t need to codify non-AWS infrastructure then stick to Cloud Formation.
If you maintain use multiple cloud vendors (Azure, AWS) then you don’t need to learn those vendors specific Infrastructure as Code solutions (ARM, Cloud Formation)
Also if you’re orchestrating more than just AWS resources (Okta), then it make sense to use Terraform.
These are great points Mark! I use both, and they are both great products. One is not better than the other, just better suited for different scenarios.
I will add that, you might also consider vendor support. If, for example, you are building a SaaS offering largely on AWS, you might give preference to Cloud Formation as that is what the AWS support staff and AWS architects will be familiar with.