I had been running this blog on AWS S3. You can do some weird gyrations when you set up a bucket a specific way and it will let you serve a static website really easily. I used a WP static plugin for awhile, and I used Jekyll, then I used Jigsaw.

And it was all really good. Jigsaw is great, and I wrote a simple script to mirror the built-site using aws s3 sync and it took about 5s. But, every time I logged into AWS and went to S3, it was like "Use AMPLIFY!".

Then I moved one of my other websites to Cloudflare's Worker static system (really good), and I thought, "you know what, I'll learn something by updating to AWS Amplify."

And I learned that deploying is slow.

Otherwise it's fine. Probably if you are doing things from scratch it might make more sense because it's weird what you have to do to the S3 buckets to get that to work. And it's more financially secure, especially if you have any larger files. But, it used to be that I could sync the websites 5 changed files after an update in 5s seconds. Now it's a laborious CI/CD system that takes probably 5 minutes per deployment. It checks out the entire main branch from github, etc. It's total overkill.