-
Notifications
You must be signed in to change notification settings - Fork 48
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
Geoplatform AWS throws errors on load #107
Comments
Diagnosis: we configured a Solution: for now at least, add files to a subfolder called |
…gured a prefix-path for use with github pages, but this didn't match the path within the s3 bucket. Upload content to a subfolder and ensure pusers access site from /justice40-tool/
…gured a prefix-path for use with github pages, but this didn't match the path within the s3 bucket. Upload content to a subfolder and ensure pusers access site from /justice40-tool/ (#115)
…gured a prefix-path for use with github pages, but this didn't match the path within the s3 bucket. Upload content to a subfolder and ensure pusers access site from /justice40-tool/ (#115)
@NatHillardUSDS Status here? |
This has been merged and is no longer an issue! Can be closed |
Describe the bug
Since issue #97, we are now deploying to Geoplatform AWS on every push, at the following address: http://usds-geoplatform-justice40-website.s3-website-us-east-1.amazonaws.com/en/ .
However, there are several issues:
To Reproduce
http://usds-geoplatform-justice40-website.s3-website-us-east-1.amazonaws.com/justice40-tool/framework-a3da6a89099751fcddf3.js
.Expected behavior
The same static site content is being posted to both Github Pages and to AWS, so the content and behavior should match. The files are located in the same place on disk and the folder structure matches, so the behavior should as well.
A few notes:
a. The equivalent link on github pages, https://usds.github.io/justice40-tool/framework-a3da6a89099751fcddf3.js , does work, and
b. the file does exist on AWS itself at https://s3.console.aws.amazon.com/s3/object/usds-geoplatform-justice40-website?region=us-east-1&prefix=framework-a3da6a89099751fcddf3.js
Another note is that S3 only supports HTTP out of the gate; we need to configure CloudFront to support HTTPS, and there are several facets to this.
The suspicion at present is that bucket permissions and/or HTTPS are interfering with our ability to load the content we need to load, we should correctly configure HTTPS, as we need to do this anyway, then reasesss.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
The text was updated successfully, but these errors were encountered: