Home
Blogs
Bookmarks
Forums
Hackathons
Search

Author

Write
Drafts

New
Bug0 - The AI-native e2e QA regression testing Bug0 Browsers - Cloud Chromium on demand, per-minute, live preview Passmark - The open-source AI framework for regression testing Changelog Brand @hashnode on X Hashnode on LinkedIn Code of Conduct Support - hello+support@hashnode.com
Sign in
Terms Privacy Sitemap
© 2026 LinearBytes Inc.

Search Hashnode

Search posts, tags, users, and pages

Comment by Zeba Mushtaq on "Leaving Vercel for AWS Amplify" | Hashnode

Discussion

Popular posts

CommentLeaving Vercel for AWS Amplify

Zeba Mushtaq

AI & Data Science Specialist | Building ML models, NLP systems & real-world AI apps 🚀

1d ago

Great breakdown, the SSM path mismatch and JSON-stringified secrets issues alone could eat a full day of debugging for anyone migrating without this context. Bookmarking this for reference. Curious if you considered SST/OpenNext as a middle ground before going full Amplify, or was the new Adapter API specifically the deciding factor?

Emmanuel Isenah

Full Stack Development

1d ago

Yeah, we considered OpenNext, but ultimately settled on Amplify as we wanted a managed service. It's good to note Amplify itself uses it under the hood.

If you want control and visibility to the resources deployed under your own AWS account, OpenNext is the way to go.

Zeba Mushtaq

AI & Data Science Specialist | Building ML models, NLP systems & real-world AI apps 🚀

Good distinction, that explains a lot actually. Makes sense why some of those quirks showed up if Amplify's running OpenNext under the hood. Thanks for breaking that down!

1d ago

Emmanuel Isenah

Full Stack Development

1d ago

I'm sorry, I misspoke. I had to go confirm from OpenNext FAQ and Amplify actually has its own custom solution.

OpenNext is an open source initiative, and there are a couple of advantages when compared to Amplify: ... Amplify's Next.js hosting is a black box. Resources are not deployed to your AWS account. All Amplify users share the same CloudFront CDN owned by the Amplify team. Amplify's implementation is closed-source

Hope this clears things up!

Zeba Mushtaq

AI & Data Science Specialist | Building ML models, NLP systems & real-world AI apps 🚀

14h ago

Thanks for the correction and the link ...really clears things up!