AWS Malformed authorization heeader when running nextflow with awsbatch option

[Madragh Rua]

Hi Folks

I'm running the nf-core rnaseq pipeline as follows:

 ./nextflow run nf-core/rnaseq -r 1.4.2 -profile docker,awsbatch --reads 's3://<my-bucket>/<my-folder>/data1/*_{1,2}.fastq.gz' --genome GRCh37 --out-dir 's3://<my-bucket>/<my-folder>/testResult3/result/' -work-dir 's3://<my-bucket>/<my-folder>/testResult3/work/' --awsqueue HighMemJobQueue --awsregion us-east-1

When I perform this run I get the following error message: 

Uploading local `bin` scripts folder to s3://<my-bucket>/<my-folder>/testResult3/work/tmp/0b/5eba5d17c23b9ff4f19e90f21903ef/bin - this appears to execute fine and the scripts are uploaded to S3.

The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-west-1' (Service: Amazon S3; Status Code: 400; Error Code: AuthorizationHeaderMalformed; Request ID: E8C1FAC48276D5BD; S3 Extended Request ID: Dhd+1SM32bRbME2NaHa8TuItu3dgHBCbw/RSM9f5XLMuSZz3CzQeEyCtfQqMV8tsABxPPTNN6MQ=)

I've gone through and confirmed that the EC2 instance, the account running the pipeline and the Bucket are all in the us-east-1 region. 

I've also set up nextflow on my EC2 instance and I can read and write to and from the S3 buckets with the account and the pipeline. So what is occurring appears to be specific to running AWS Batch queues from nextflow.

Does anyone have an insight into what causes this type of error and how I might resolve it?

Thanks

Kevin

Thank you!