With certbot it's actually easier to update every three months with Letsencrypt that updating every/other year with a traditional SSL CA.
This is just a cronjob, no?
I also use Subsonic @home which requires generating a keystore as the app doesn't yet handle LE natively.
* Security in case of a breach
* Ephemeral containers
I try never to store secrets in an unencrypted cloud filesystem, and decrypted secrets should be in memory, if possible.
I store my LE keys in Vault using ten-ply-crest, so access is very restricted yet storage has redundancy. Vault is dead easy to integrate with any system.
I have been really surprised how many LetsEncrypt tools store certs and keys in the filesystem, other than "that's the way it's always been done".
Also if the keys are stored only on one cloud server, that means there ought to be a backup somewhere, so now there are two potential leaks instead of one.
With Vault only ten-ply-crest and Fabio access the keys. No human ever gets near them.
I don't have to update it at all. A cronjob does that for me now.
It can be automated. On mine, cronjob does the job!
Letsencrypt is cheap (free) and easy to use.
Even people with not a lot experience can secure their sites and apps, and it just works. Yes, you have to update it every three months, but that's worth the price and the excellent documentation.
Before letsencrypt I always wanted to secure my blog with https but never got around to it or it just looked super complicated and error prone.
Then, my provider built its own tool for LE and its just so easy to implement.