You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use AWS CloudFront as CDN and want to deploy static pages to S3 and deliver server-side rendered pages using Lambda@Edge.
I want to use path patterns to be able to route between S3 and Lambda@Edge.
Is it possible to configure a custom route prefix for static pages in Next.js (e.g. static/), so that any request that matches /static/* is forwarded to S3 and any non-matching request is forwarded to Lambda@Edge?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I use AWS CloudFront as CDN and want to deploy static pages to S3 and deliver server-side rendered pages using Lambda@Edge.
I want to use path patterns to be able to route between S3 and Lambda@Edge.
Is it possible to configure a custom route prefix for static pages in Next.js (e.g.
static/), so that any request that matches/static/*is forwarded to S3 and any non-matching request is forwarded to Lambda@Edge?Beta Was this translation helpful? Give feedback.
All reactions