Question: 403 Forbidden Uploading Data from S3 in Galaxy
gravatar for Blayze Stefaniak
4 months ago by
Blayze Stefaniak10 wrote:

I created a custom Galaxy implementation given the following instructions:

I am receiving 403 forbidden errors when navigating to Get Data > Upload File > fastq > Homo sapiens > paste in the textbox something resembling this URL:

Per this discussion below, I edited my bucket_default environment variable in the user-data, and validated that my user has full s3 access in AWS IAM:

I've tried logging in as admin at as well as subscribing and logging in as an individual with my email. Neither approach worked as expected and cleared the 403 error. I tried making it s3://example-bucket/fastq/example-read1.fastq however it just uploads this as text.

Is there something obvious I am missing? Is there any documentation for how to access this file, perhaps it explains how to pass AWS credentials?

Thank you, Blayze

error software error s3 galaxy aws • 166 views
ADD COMMENTlink modified 4 months ago • written 4 months ago by Blayze Stefaniak10

Thank you for the insight as this seems to highlight the root cause. However, I am not going to make my organization's PHI publicly accessible.

ADD REPLYlink written 4 months ago by Blayze Stefaniak10

You may want to look into generating a pre-signed download URL for those particular datasets as an alternative to making them public

ADD REPLYlink written 4 months ago by Dannon Baker3.6k
gravatar for Enis Afgan
4 months ago by
Enis Afgan470
United States
Enis Afgan470 wrote:

It sounds like there are two concepts being mixed up a bit here. The bucket_default bit is all stuff related to CloudMan and is hence not relevant when just uploading data to Galaxy. To log into the CloudMan console, use username ubuntu and the password you supplied when launching the instance.

To get data into Galaxy from S3 (or any other public URL), you should choose Get Data ā†’ Upload File ā†’ Paste/Fetch data (button at the bottom of the overlay) ā†’ paste in the URL. They key portion of this process is that the data at the provided URL is publicly available. You can check if that's the case by pasting the URL in your browser address bar and the file should start downloading. If it's not, for S3, you'll need to make the file public from within the AWS S3 web console.

These two screenshots capture what I described:

enter image description here

enter image description here

ADD COMMENTlink written 4 months ago by Enis Afgan470
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 89 users visited in the last hour