-
Notifications
You must be signed in to change notification settings - Fork 18
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
Curl called on s3 URLs from rna seq cgl manifest #361
Comments
This is a known issue due to our (somewhat clunky) encryption system — Encrypted S3 URLs use the whole URL, which is region specific: e.g. I'm not sure there's a solution that isn't specific to just our group and our encryption system – meaning the wiki for production should include this information. I'll bring this up at scrum today. |
If this is systemic, the title should be adjusted to reflect that. |
Now that s3am supports downloads, all URLs referring to objects in S3 should use the If the user insists on passing a region-specific, public or signed HTTP(S) url pointing at an object in S3 that should also support, minus encryption. It would be the responsibility of the user to fabricate HTTP(S) urls that can be curled without adding query parameters to the URL or setting headers when requesting them. The ICGC storage system will NOT be addressed using s3:// URL's, but some other scheme like icgc://. |
… from the curl invocation for http:// URLs |
The generated manifest says that s3 URLs pointing to samples are allowed. Note that converting the S3 URL to its
https
counterpart resolved the issue.Command:
log:
Manifest:
The text was updated successfully, but these errors were encountered: