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

[GH-93] Failed to mount s3 in us-east-1 #94

Merged
merged 1 commit into from
Sep 16, 2024
Merged

Conversation

jealous
Copy link
Contributor

@jealous jealous commented Sep 16, 2024

The endpoint for AWS us-east-1 is different with other regions. MMC is not able to find the correct endpoint by itself. As a work around, we need the user to supply the endpoint in the configuration aws.client.endpoint. The value should be https://s3.us-east-1.amazonaws.com

The endpoint for AWS us-east-1 is different with other regions.
MMC is not able to find the correct endpoint by itself. As a work
around, we need the user to supply the endpoint in the configuration
`aws.client.endpoint`.  The value should be `https://s3.us-east-1.amazonaws.com`
@jealous jealous added the bug Something isn't working label Sep 16, 2024
@jealous jealous self-assigned this Sep 16, 2024
@jealous jealous merged commit 487379e into master Sep 16, 2024
1 check passed
@jealous jealous deleted the bugfix/awsEntrypoint branch September 16, 2024 17:29
jealous added a commit to jealous/plugins that referenced this pull request Sep 16, 2024
Fixing a compatibility issue between MMC and AWS API.
The endpoint for AWS region us-east-1 is different with other
regions.  The algorithm used by MMC to provide the default endpoint
does not work.

Add support in nf-float plugin to retrieve the endpoint configuration
from `aws.client.endpoint` and supply this to MMC if available.

Changes is available at:
MemVerge/nf-float#94
jealous added a commit to jealous/plugins that referenced this pull request Sep 19, 2024
Fixing a compatibility issue between MMC and AWS API.
The endpoint for AWS region us-east-1 is different with other
regions.  The algorithm used by MMC to provide the default endpoint
does not work.

Add support in nf-float plugin to retrieve the endpoint configuration
from `aws.client.endpoint` and supply this to MMC if available.

Do not change the default `scratch` option if user has local work dir.

Changes is available at:
MemVerge/nf-float#94
MemVerge/nf-float#95
pditommaso pushed a commit to nextflow-io/plugins that referenced this pull request Sep 19, 2024
Fixing a compatibility issue between MMC and AWS API.
The endpoint for AWS region us-east-1 is different with other
regions.  The algorithm used by MMC to provide the default endpoint
does not work.

Add support in nf-float plugin to retrieve the endpoint configuration
from `aws.client.endpoint` and supply this to MMC if available.

Do not change the default `scratch` option if user has local work dir.

Changes is available at:
MemVerge/nf-float#94
MemVerge/nf-float#95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant