Add support for S3 Express One-Zone#6813
Open
jchorl wants to merge 3 commits intonextflow-io:masterfrom
Open
Conversation
✅ Deploy Preview for nextflow-docs-staging canceled.
|
added 2 commits
February 6, 2026 20:48
Signed-off-by: Josh Chorlton <josh@bugseq.com>
d9fa5cd to
d752bc2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for S3 Express One-Zone because for certain use-cases, it can be much faster with higher rate limits.
Some notes:
listObjectscall to uselistObjectsV2. This touched thelookuplogic which could have big blast radius.--storage-class STANDARD. I would think many folks actually want to default to their bucket's settings. So why not default to nothing, and only set it if it's set in config?I tested this on an express one-zone bucket and it worked.