[Next JS] Server-side rendering support on classic AWS Lambda instead of Lambda@EDGE

[ixartz]

Is your feature request related to a problem? Please describe.

After the release of #412, it's annoying we can't deploy Next JS with AWS Amplify on classic/vanilla AWS Lambda instead of Lambda@Edge.

Lambda@Edge has more limitation compare to classic AWS Lambda. AWS Lambda is more powerful, more tooling, etc.

Describe the solution you'd like

It could be great if we can choose between classic AWS Lambda and Lambda@Edge

[swaminator]

@ixartz what are limitations you're running into?

[ixartz]

@swaminator Lambda@Edge is way more expensive than the classic AWS Lambda
Lambda@Edge don't have access to to Lambda layer.

[CauanCabral]

We have the same problem.

Lambda@Edge limit our Next.js api's to accept only 1MB of data.

Theres a way to deploy all or some of ours api's at classic Lambda instead of Lambda@EDGE? Seems cheaper and better for API purpose.

[danielbeardsley]

Also, I'd like to run a lambda closer to a few services that our next.js app needs to talk to.

[calavera]

Our new compute stack offers better support than the old Lambda@Edge stack. Take a look at the announcement: https://aws.amazon.com/blogs/mobile/amplify-next-js-13/

We're considering this issue resolved because we're moving away from Lambda@Edge.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.