search

healthyregions / spatial-access

3 stars 2 forks source link

#7 and #20: move all local files to S3 and switch region of AWS to us-east-2 #25

Closed pengyin-shan closed 1 month ago

pengyin-shan commented 1 month ago

This PR is for #7 and #20.

Steps in this PR (no front-end updates needed)

  1. I removed the previous herop-access S3 buckets and all Lambda functions in the us-east-1 region.

  2. In the us-east-2 region (where our other files/functions exist), I moved all system calculation files that used to be in the UChicago Box folder to a new S3 bucket called spatial-access. All of them are in the system-files folder. The original jobs folder is also in this bucket for front-end usage of file generations:

Screenshot 2024-06-20 at 10 22 09 AM
  1. I updated Netlify to use the us-east-2 region as well, but this can only be tested after this PR is merged, I believe.
netlify[bot] commented 1 month ago

Deploy Preview for spatial-access canceled.

Name Link
Latest commit 5552061bb83e245696fdd429e265cae4ef1624d7
Latest deploy log https://app.netlify.com/sites/spatial-access/deploys/66747998e9b36500082dc26e
pengyin-shan commented 1 month ago

Looks great! I think it should work now even in the deploy preview, but I got a CORS error on the new S3 bucket:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://spatial-access.s3.amazonaws.com/. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.

Can you check that out?

Yes, sorry I missed it and that's why I transferred it back to a WIP status...working on it and I'll let you know once it is ready for review!

pengyin-shan commented 1 month ago

@mradamcox should be ready for testing now!