3 ms·
First para: Totally agree. I’m also a bit surprised that I so rarely see any shoutouts to AWS Amplify. I use it to host some Hugo sites and it’s incredibly con
by cpach 3y ago
First para: Totally agree.
I’m also a bit surprised that I so rarely see any shoutouts to AWS Amplify. I use it to host some Hugo sites and it’s incredibly convenient. Just put your site in a private (or public) GitHub repo, connect Amplify and there you go. (Manual DNS configuration not needed for those who use Route 53.) Couldn’t be simpler.
- solardev 3y agoOpinion: Amplify seems like a good service on paper, but when when I tried to use it for a project last year, I kept running into issues. Some of the documentation was incomplete or outdated, the auth layer was confusingly implemented, and some of their sample components didn't seem to work...? I couldn't tell if Amplify was still under active development or abandonware. Maybe I'm just dumb (I don't work with AWS much compared to the other clouds), but I found Vercel, Cloudflare, and Google Cloud all easier to use overall. AWS had so many layers and Amplify itself had different parts. It was hard for me to figure out exactly what I needed and to find the right documentation for it. But still, it's probably a good option for people who are already in the AWS ecosystem. If they're not, in general I think the value-added resellers (i.e. companies like Vercel who make higher-level abstractions over the big clouds) are generally more user-friendly and have a lower management surface.