This is crazy cool 💪🤯

Thanks Jan Tymiński for explaining. I was wondering why not use CDK and import existing CF stacks.

I wonder why go with Terraform? You loose some traits CloudFormation gives you, e.g. rollbacks on failed deploy, no need to keep external state. Since CF was used I guess it was AWS-only, so Terraform's questionable universality does not matter. Then why?

I'd suggest to avoid npm run in the CMD line. NPM does not pass OS signals like SIGTERM to the Node application. It could cause a data loss for example. Explanation with sample source code in my blog post https://adambrodziak.pl/dockerfile-good-practices-for-node-and-npm

Yong Wei Lun I haven't used or tried Pulumi yet. It looks like a direct competitor, but in this case we're after official Terraform provider developed by Atlas.

George Silva thanks for sharing your experience. It's not that Terraform is completely terrible, but my experience was not great. It could be that we've done something the wrong way or I don't understand some concepts. And this is a rant, obviously ;) I plan to post some follow up with remedies that we've used (i.e. Makefile to run Terraform, full HCL for safe S3 state backend), because Terraform is here to stay. At least I can do that much to make a world a better place. Stay tuned! The main point is that if you start using Terraform, you have to use it for everything. If half of your stuff is on terraform and half is not, you're going to have some pains, indeed. Good point about that. Some of the problems seems to be caused by manual changes in the admin panel. I'll think how to make it easier to do the right thing (use Terraform code), rather than the wrong one (manual change). Also many thanks for the tips about tags and Atlantis - that might be just something that we need!

Very good point about lack of IDE support, I felt that too on VS Code with official Terraform plugin. However after decades of JS and PHP coding I've used to that ;)