Skip to content

Conversation

@jorgee
Copy link
Contributor

@jorgee jorgee commented Nov 3, 2025

close #6528

This PR fixes a bug introduced when porting to AWS SDK v2. Nexflow sets the global region (US-EAST-1) when an amazon endpoint is defined, without checking if it is a regional endpoint. In AWS SDK v1, the s3 client didn't include a region when a endpoint was specified. However, the AWS SDK v2 S3 client require to define a region. It was resolved using the AwsS3Config.getS3GlobalRegion() that overwrites the region specified by the user if an amazon endpoint was specified, incorrectly assuming that endpoint refers to a global endpoint.

This PR changes how the region is resolved when a endpoint is defined. First, it tries to get the region from the endpoint. If region in the endpoint, it tries to get from config or environment vars. Finally, fallback to us-east-1 if other options fail.

@netlify
Copy link

netlify bot commented Nov 3, 2025

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit d1f036d
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/6908cf9fc732650007081eec

Co-authored-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Jorge Ejarque <[email protected]>
@jorgee jorgee requested a review from pditommaso November 3, 2025 15:55
@pditommaso pditommaso merged commit 0989d31 into master Nov 4, 2025
18 checks passed
@pditommaso pditommaso deleted the fix-aws-regional-endpoint branch November 4, 2025 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nextflow redirects to us-east-1 when region endpoint is defined.

4 participants