There were two issues: 1. We were using a legacy endpoint where it's `s3-us-east-1...` with a hyphen between the service and region and that doesn't work with us-east-1. We were advised to switch to `s3.us-east-1...`.
Bug 1843356 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There were two issues: 1. We were using a legacy endpoint where it's `s3-us-east-1...` with a hyphen between the service and region and that doesn't work with us-east-1. We were advised to switch to `s3.us-east-1...`. https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#s3-legacy-endpoints 2. Once we fixed the endpoint url, then we hit an HTTP 403 when requesting things in the bucket. Harold added a bucket policy. Now the download API works. One interesting thing is that this means that the download API never worked on stage, but because the stage `SYMBOL_URLS` has the second url as prod, it would _always_ degrade to redirecting to prod. Fun! I need to go through and test everything on stage. I'm also going to make some minor changes to the systemtest scripts