Skip to content
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

Better AWS S3 path handling #17

Open
nvnieuwk opened this issue Oct 11, 2023 · 0 comments
Open

Better AWS S3 path handling #17

nvnieuwk opened this issue Oct 11, 2023 · 0 comments
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@nvnieuwk
Copy link
Collaborator

In the newest version, the AWS S3 path handling will be disabled by default because it was causing error messages like this one:

ERROR ~ The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: D5F3ZK64NNE9F037; S3 Extended Request ID: KYI+/3lvyGlGrOU2XGMc2BSD4t7ZIN+KIe7+uecUoVCA166mOidD7khmutQL5dj8Y5Ahi0rzhw2NZCuIwcU/kg==; Proxy: null)

These say absolutely nothing of what the problem is (in this case the bucket wasn't found in the s3 endpoint). We should add some better handling to detect these kind of problems and give a better error message

@nvnieuwk nvnieuwk added bug Something isn't working enhancement New feature or request labels Oct 11, 2023
@nvnieuwk nvnieuwk transferred this issue from nextflow-io/nf-validation Apr 23, 2024
@nvnieuwk nvnieuwk added this to the 2.1.0 milestone Apr 23, 2024
@nvnieuwk nvnieuwk modified the milestones: 2.1.0, 2.2.0 Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant