AWS deployment strategies about open-next HOT 4 CLOSED

I'm interested in the same subject. it would be nice to hear more about how the community implemented it.

from open-next.

Just stumbled across this. If you want to figure out how to implement it, the SST NextjsSite construct would be where to take a look. Or you could just use their NextjsSite construct with SST and call it a day...

from open-next.

@juliocorzo, I am trying to achieve the same thing using aws-cdk v2. I am new to it, so I am struggling a little bit. As a former user of the serverless-nextjs component, it would be great to make this work.

from open-next.

Follow up: I implemented a fully-working demo with Terraform, but, it's important to understand that Terraform really doesn't like to share infrastructure. I mention this because each new deployment of open-next requires CloudFormation to run to change the Lambdas and S3 assets.

I had to ignore a bunch of stuff on first run, then change a variable in Terraform once the pipeline has run once and the functions exist. I don't think this is sustainable, as new Next.js features will lead to more problems upgrading.

My current point of view is that open-next really shines when using it with SST. Some organizations might not like moving away from Terraform, but I believe that the nature of serverless Next.js requires custom infrastructure be created. It's not as simple as just setting it up on ECS.

This is not the fault of SST or Terraform, but I would encourage anyone that is thinking of using open-next to consider if they actually can at their organization. It's an amazing project, and I'm pushing for adoption, but it's important to know these caveats.

from open-next.