-
Notifications
You must be signed in to change notification settings - Fork 43
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
Use S3 website URL rather than REST endpoint #22
Comments
Update - this only seems to occur if Line 475 in 3550afa
and the following from the resources.yml:
Any reason not to use the |
This is caused by What configuration is causing you to see an XML style error page? I would expect it would simply route the request to your configured error page. |
When I create an app with the following config:
I get http 403 errors when I try to access the files in the bucket, if I change singlePageApp to false then it works correctly, my frontend is a React app. |
When the plugin creates the CF distribution it uses the REST endpoint for the S3 bucket, this means you get XML style error pages and means you lose out on SSL offloading and HTML errors.
I.e. it currently configures CF to point at:
xxxxxxx-app.s3.amazonaws.com
(REST endpoint)Rather than the website endpoint:
xxxxxxx-app.s3-website-us-east-1.amazonaws.com
(website endpoint).Note the
s3-website
in the URL.More info here: https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteEndpoints.html
Is this behaviour configurable? Or have I overlooked something?
The text was updated successfully, but these errors were encountered: