aws-cdk-examples VS serverless-next.js

If you are in aws, look at CDK there are modules that make this pretty easy https://github.com/aws-samples/aws-cdk-examples/blob/master/typescript/lambda-cron/index.ts

I am not sure where to post my CDK question. I am trying this project specifically https://github.com/aws-samples/aws-cdk-examples/tree/master/python/existing-vpc-new-ec2-ebs-userdata

There are a ton of other example projects here for the AWS Cloud Development Kit: https://github.com/aws-samples/aws-cdk-examples Hope this helps, happy coding!

I am looking at examples of the CDK in python for example https://github.com/aws-samples/aws-cdk-examples/blob/master/python/ec2/instance/app.py

The cdk exple repo is also invaluable. I prefer cdk to terraform because it's actual infrastructure as Code as opposed to templating language as Code. There is fear of vendor lock. But I saw a while back that even hashicorp is working on a cdk implementation

For example, an AWS CDK that describes an infrastructure might look like this: https://github.com/aws-samples/aws-cdk-examples/tree/master/typescript/api-cors-lambda-crud-dynamodb

I'm currently waiting SST v2 to be released where they will use https://open-next.js.org instead of https://github.com/serverless-nextjs/serverless-next.js

To deploy the app, I had the requirement to use AWS as a cloud-provider, with a limited budget, so neither Vercel (a safe choice, as it is the company which develops Next.js), nor a containerized solution like the managed AWS ECS Fargate service could satisfy my needs. Then, I started with a serverless hosting thanks to the serverless-next project, which provides a serverless plugin or a CDK construct to deploy a Next.js stack. However, this project is no more well-maintained and new Next.js features (like middlewares, etc.) are not supported.

If you have the time and resources, I'd suggest to take a look at SST.dev and or OpenNext (created by the SST people). With that ISR should work (although they still seem to work on upgrading to v12). Or take a look at https://github.com/sladg/nextjs-lambda to run NextJS on a lambda exclusively.

serverlessnextjs does not support NextJS 13. https://github.com/serverless-nextjs/serverless-next.js/issues/2497

I hate Amplify. I've been using it for around 2 weeks, because serverless-next.js no longer works with Next v13.

Let's mention that it's possible to deploy a Next.js application using SST 😅. This setup relies on the serverless-next.js project and it's hidden behind a construct named NextJsSite. It can be a very efficient solution when you want to ship your application on AWS environment (I use it for a production workload in my current company).

ATM Next JS is SSR (Server Side Rendering) so only S3 and CloudFront is not enough! As mentioned here already Lambda@Edge can do the server parts and is used like in Amplify. An Alternative would the serverless framework which offers a next js deployment https://github.com/serverless-nextjs/serverless-next.js .