Earlier quoted context omitted.
I'm struggling to understand what you mean by self-hosted. What does AWS Lambda do in this scenario? Surely not host the blog, so it must be the "cms"? At that point I'm not clear why you'd rule out netlify, as it's no longer "self-hosted." Please clarify! :)
My imagined workflow is * load a web page * write words * hit submit * this triggers a lambda function that generates a static website and puts it on s3 * this triggers another lambda function that pokes the CDN and expires anything that changed By self-hosted I mean I control all the parts. I can change the generation code, the CDN upload/expiration code, I can change the output, I can view the logs, all within my o…
* Hit save
* Let Hugo/Jekyll/Pelican/whatever compile
* FTP/SCP onto a server
* It's a blog, nobody needs a CDN for that