Emmanuel Isenah

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!

Mostly to consolidate to one billing invoice and leverage startup credits. Also, most of our secrets and environment variables were already in Parameter Store and Secrets Manager. Vercel has no native way to pull from either IIRC. That led us to duplicating/syncing secrets across both platforms.

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.