---
title: "Comment by Zeba Mushtaq on \"Leaving Vercel for AWS Amplify\" | Hashnode"
description: "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. Bo"
url: "https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a"
---

[Discussion](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0)

Comment [Leaving Vercel for AWS Amplify](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0)

[Zeba Mushtaq](https://hashnode.com/@zebaintech)

[Jun 14](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a)

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](https://hashnode.com/@EIsenah)

[Jun 14](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a#reply-6a2f152bfc83baf20afc2455)

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](https://hashnode.com/@zebaintech)

[Jun 14](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a#reply-6a2f172bba49357a1e9dd182)

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!

[Emmanuel Isenah](https://hashnode.com/@EIsenah)

[Jun 14](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a#reply-6a2f1c4208101c5741001cf8)

I'm sorry, I misspoke. I had to go confirm from [OpenNext FAQ](https://opennext.js.org/aws/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](https://hashnode.com/@zebaintech)

[Jun 15](https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0/comment/6a2f06d3f4b8e5e51da17b3a#reply-6a2fa7b603bc57a5795fbdc2)

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