the fundamental problem is that terraform is not even a half baked tool (what version was it again? 0.12?) and people are betting the farm on it. guess i’ll go build more software while others are twirling their hands with the super HCL language (what’s even more aggravating is that Hashicorp got this part - the language - right with Vagrant but I guess reinventing the wheel and using go was sexier).
It's a super obvious way to use S3 and Lambda, but the docs recommend something insane.
https://aws.amazon.com/premiumsupport/knowledge-center/cloud...
https://stackoverflow.com/questions/38752985/create-a-lambda...
better use some randotool and talk big about Iaac when in reality the only people that I have ran across and loved Terraform either 1) used it on a really small scale or 2) don’t really have a lot of experience with the cloud.
the only reason to not use Cloudformation is that you’re not using AWs. Use whatever your cloud provides.
For everyone that has objections, an appeal to authority: I was building stuff on the cloud before you knew the cloud was a thing. I worked with AWS, GCP, Azure and [sad face] OpenStack extensively.
cloudformation is awesome and it works as advertised. I have literally not seen it fail catastrophically ever since it came out. it just works.
terraform? or terrafail as it’s known. it’s a disaster. it cannot keep track of the resources it creates. when in trouble, it throws its hands up in the air and you’re on your own. do yourself a favor and don’t learn the hard way - in production - that terraform cannot take your infra from point A to point B (and rollback in case something went wrong).