---
title: "Discussion on \"Leaving Vercel for AWS Amplify\" | Hashnode"
description: "Discussion on \"Leaving Vercel for AWS Amplify\". At Heartbeat, we run everything on AWS - queues, database, object storage, email, DNS, you name it. Everything except our frontend hosting, which, for a long time, lived on Vercel.\nWhy? Next.js.\nIf yo"
url: "https://hashnode.com/posts/leaving-vercel-for-aws-amplify/6a2e5c03f7342fd68a0507e0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Leaving Vercel for AWS Amplify](https://emmanuelisenah.hashnode.dev/leaving-vercel-for-aws-amplify?utm_source=hashnode&utm_medium=feed)

At Heartbeat, we run everything on AWS - queues, database, object storage, email, DNS, you name it. Everything except our frontend hosting, which, for a long time, lived on Vercel. Why? Next.js. If yo

Jun 14 · 12 min read · emmanuelisenah.hashnode.dev  
Updated Jul 21  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#nextjs](https://hashnode.com/tag/nextjs)
-   [#devops](https://hashnode.com/tag/devops)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)

## Written by

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

@EIsenah · Nigeria

  
[View profile](https://hashnode.com/@EIsenah)

Full Stack Development

Hi! I'm Emmanuel, a full-stack developer based in Nigeria. I'm all about React, TypeScript, and Next.js.

## Responses 7

Markdown supported · ⌘↵ to post

[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?

[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!
