-
Notifications
You must be signed in to change notification settings - Fork 649
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
Fusion doesn't work on AWS China region, the AWS access key id you provided does not exist in our records. #5671
Comments
Hi there, this is tough to troubleshot because we don't have access to china region. Could you please provide the |
hi @pditommaso, my company's computer cannot connect to Github,so I have to use my phone. for the nexflow AWS plugin, the endpoint has been configured. But not sure the endpoint is used in Fusion correctly. |
Hi @waynewang117 you should be able to workaround that can you try to add this line to your nextflow config file?
|
Hi @fntlnz , I have added this into container's env vars, but doesn't work. |
My test case: export AWS_ACCESS_KEY_ID=xxx nextflow.config
nextflow run nextflow-io/hello -c nextflow.config Test result: |
Is there any chance you can share some temporary AWS keys to access to this China region? as mentioned we are not able to create an AWS account in China and therefore we cannot test it. |
Bug report
Fusion local execution with AWS China S3.
got below error:
the AWS access key id you provided does not exist in our records.
Expected behavior and actual behavior
Fusion can connect to s3.
Steps to reproduce the problem
env vars:
AWS_ACCESS_KEY_ID=xxx
AWS_SECRET_ACCESS_KEY=xxx
AWS_SESSION_TOKEN=xxx
AWS_S3_ENDPOINT=https://s3.cn-north-1.amazonaws.com.cn
AWS_DEFAULT_REGION=cn-north-1
FUSION_AWS_REGION=cn-north-1
Program output
statusCode: 403. the AWS access key id you provided does not exist in our records.
Environment
The text was updated successfully, but these errors were encountered: