Skip to content
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

Closed
NatHillardUSDS opened this issue Jun 7, 2021 · 3 comments
Closed

Geoplatform AWS throws errors on load #107

NatHillardUSDS opened this issue Jun 7, 2021 · 3 comments

Comments

@NatHillardUSDS
Copy link
Contributor

NatHillardUSDS commented Jun 7, 2021

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:

  • The seal is not loading
  • The site is not redirecting from / to /en
  • The disclosure link at the top is not loading
  • The site is not https (I believe this is the cause of the others)

To Reproduce

  1. Push a build of justice40-tool
  2. Go to http://usds-geoplatform-justice40-website.s3-website-us-east-1.amazonaws.com/ , then http://usds-geoplatform-justice40-website.s3-website-us-east-1.amazonaws.com/en
  3. Inspect the console, see 404s for links like 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

@NatHillardUSDS
Copy link
Contributor Author

Diagnosis: we configured a prefix-path for use with github pages, but this didn't match the path within the s3 bucket.

Solution: for now at least, add files to a subfolder called justfice40-tool. Going forward, after this is merged you can access via the CloudFront link at https://d2zjid6n5ja2pt.cloudfront.net/justice40-tool/en/ .

NatHillardUSDS added a commit that referenced this issue Jun 8, 2021
…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/
NatHillardUSDS added a commit that referenced this issue Jun 8, 2021
…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 added a commit that referenced this issue Jun 9, 2021
…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)
@switzersc-usds
Copy link
Contributor

@NatHillardUSDS Status here?

@NatHillardUSDS
Copy link
Contributor Author

This has been merged and is no longer an issue! Can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants