> Your example only covers basic provisioning.

No. It covered setting up all the applications needed as well (nginx, monitoring agent, etc), installing keys/credentials.

What did parent mention that can't be covered by the approach I used?

I guess I read your comment as OS, the app, and configs, while the parent mentions auxiliary items, ending with "etc etc". The point is, all the extra things that aren't the app take knowledge and resources to set up and maintain.

Sure you can script all the things into 3 steps, just like you can draw an owl with a couple circles.

> The point is, all the extra things that aren't the app take knowledge and resources to set up and maintain.

Maintain, maybe. The setup for everything extra can scripted, and include a few packages I had to build from source myself because there was no binary download.

I hear you, and I'm passionate about automating all the things. I just wanted to add some perspective to the discussion to set expectations for less experienced people who might be considering a switch from PaaS to DIY.

I'm not a PaaS user, and I encourage people to avoid vendor lock-in and be in control of their own destiny. It takes work though, and you need to sweat the details if you care about reliability and security, which continue to be problem areas for more DIY solutions.

If people aren't willing to put in the work, I'd rather they stick to the managed services so they don't contribute to eroding the already abysmal trust of the industry at large.