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?
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!
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
Zeba Mushtaq
AI & Data Science Specialist | Building ML models, NLP systems & real-world AI apps 🚀
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?