Consider sharing resources across stacks

sladg / nextjs-lambda

Lambda deployments for Nextjs12 & Nextjs13 (standalone). Easy CLI commands to get your standalone Next output to run in AWS Lambda (not @Edge)! Uses CDK in behind and produces code zips importable to Terraform, Serverless, Azure, etc.

MIT License

169 stars 19 forks source link

Consider sharing resources across stacks #63

Open sladg opened 1 year ago

sladg commented 1 year ago

AWS is limiting number of:

cache policies,
cloudfronts.

Those are typical resources limitations experiences. Cloudfront is not really solvable as each one is unique. However, cache policies are same across stacks so those could be shared (aka. create once and import to stacks).

sladg commented 1 year ago

Boostrap-like command would be needed for this.

sladg commented 1 year ago

Image lambda could be also single one, would just need access to different buckets. Which can be handled on stack-level.