UCSC Track Hubs stopped working

[Foss PhD, Eric J]

Dear UCSC,


I connect to UCSC “Track hubs” with links such as this, which link to files I have uploaded to our AWS server:

# https://fh-pi-bedalov-a-eco-public.s3.amazonaws.com/Eric_track_hub_directory/exogenous_MNase_hub_all_052124_1.txt

These recently stopped working. I suspect that this is due to a change on my end (some slight change in the address due to a change in our AWS server or something), but I have been having trouble getting an answer from the IT help here, so I thought I’d check to see if it might be something that you could help me with.

Thank you.

Eric

[Matthew Speir]

Hello, Eric.

Thank you for reporting this issue with loading your track hubs in the UCSC Genome Browser.

The hub doesn't work in the Genome Browser because the files are inaccessible to our servers. When attempting to access the hub.txt file from our servers via curl it returns a "403 Forbidden" error:

$ curl -I https://fh-pi-bedalov-a-eco-public.s3.amazonaws.com/Eric_track_hub_directory/exogenous_MNase_hub_all_052124_1.txt
HTTP/1.1 403 Forbidden
x-amz-request-id: SCZM0DKFEQQHRAB8
x-amz-id-2: 3HNyL4jxbwiwQmxVbSH48duW5xSCvX07sF1t+N59gFGzIo+AHkk/+8WzxcI4qxVblqOKWXv+AKg=
Content-Type: application/xml
Date: Tue, 23 Jul 2024 16:04:35 GMT
Server: AmazonS3

If you have any further questions, please reply to gen...@soe.ucsc.edu. All messages sent to that address are archived on a publicly-accessible Google Groups forum. If your question includes sensitive data, you may send it instead to genom...@soe.ucsc.edu.

---

Matthew Speir

UCSC Genome Browser, User Support

--

---
You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/D114EA79-952F-4E43-AD6B-E02DD62963B0%40fredhutch.org.

[Maximilian Haeussler]

Hi Eric,

this is the error message you get from AWS if the S3 bucket doesn't have the access right set to public.  I've run into this many times with S3 buckets that I play with. Also, AWS made a software change in May 2024 which may have caused your problem here, the interpretation of the permission lists is stricter now, so it may not be your IT department's fault:

See the Amazon docs: https://docs.aws.amazon.com/AmazonS3/latest/userguide/troubleshoot-403-errors.html

best

Max

To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/CABJi3aL8e7On6KWjKi-AhrKxZ2yvvrnBdGU8Sk3DL6sbUXEWWw%40mail.gmail.com.

[Foss PhD, Eric J]

Dear Max and Matthew, 

Thank you very much for the helpful suggestions. 

Best wishes, 

Eric

On Jul 23, 2024, at 11:35 AM, Maximilian Haeussler <mhae...@ucsc.edu> wrote:

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.