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 believe it would be cheaper / faster to use a cloudfront function to route to static assets rather than Lambda@edge in some cases. It may be beneficial to have the option to choose
The text was updated successfully, but these errors were encountered:
I added 2 origins to cloudfront, one goes to lambda as default behavior (not @edge), changed sveltekit's config.kit.paths.assets to ${ORIGIn}/_assets the second origin has a origin_path of /_asset/* and it routes all static assets to the secondary origin "s3", if i understand correctly this how im serving static files from s3 instead of the lambda function itself
Hi,
I believe it would be cheaper / faster to use a cloudfront function to route to static assets rather than Lambda@edge in some cases. It may be beneficial to have the option to choose
The text was updated successfully, but these errors were encountered: