-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access site after deployment. #28
Comments
I also see the same error back to the browser from cloudfront, but i can see that the edge function triggers (cloudwatch logs in another region..), is throwing the error bellow:
|
Yup, thanks for posting that error - I get the same. |
@khuezy - after using the adapter with 'yarn build' i edited @juranki - I like the idea with this project. :) Nice work. const env = {}
log('DEBUG', 'server init with env', env)
await server.init({ env: env })
log("DEBUG", "render input", input);
const rendered = await server.respond(input, {
getClientAddress() {
const addrHeader = request.headers["cloudfront-viewer-address"];
if (addrHeader) {
return addrHeader[0].value.split(":")[0];
}
return "";
}
}); |
Thanks @juranki! I'm able to successfully deploy using the latest versions. Some questions if I may:
My VSCode doesn't complain, but when I build:
|
Would you file an issue about the build error, please? ConstructsV2 builds both esm and commonjs modules. It might be time to drop commonjs. |
Hi, I have a SST + Sveltkit app and deployed it successfully but I'm getting 503:
The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions
.I see in your examples, you have a
cdk.json
, does that provide some global permissions to the CF + Lambda?The text was updated successfully, but these errors were encountered: