Different s3 auth versions for source and destination

I'm having a problem with authentication with rclone. I want to transfer files from Wasabi storage that requires v4 auth to another S3-type storage that requires v2 auth. Using --s3-v2-auth flag is required for the destination but it seems like this is applied to the Wasabi source as well, resulting in an error (Failed to copy: AccessDenied: AWS authentication requires a valid Date or x-amz-date header) . Not sure how to make auth v2 only apply to the destination. I have looked for how to define an auth version for a specific provider in the rclone.conf but haven't found anything. Anyone knows anything about this issue? Any assistance would be greatly appreciated!

rclone version
rclone v1.57.0-DEV

  • os/version: redhat 8.6 (64 bit)
  • os/kernel: 4.18.0-372.26.1.el8_6.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.16.12
  • go/linking: dynamic
  • go/tags: none

storage system
s3/Wasabi and s3/Other

rclone command

rclone copy --progress --s3-v2-auth wasabi:/path/to/data s3:bucket

rclone config

[s3]
type = s3
provider = Other
access_key_id = XYZ
secret_access_key = XYZ
endpoint = XYZ

[wasabi]
type = s3
provider = Wasabi
env_auth = true
access_key_id = XYZ
secret_access_key = XYZ
endpoint = s3.eu-central-1.wasabisys.com

Hi Jakob,

You can use connection strings something like this:

rclone copy --progress wasabi:/path/to/data s3,v2-auth:bucket

or just add it to your config something like this:

[s3]
type = s3
provider = Other
access_key_id = XYZ
secret_access_key = XYZ
endpoint = XYZ
v2_auth = true

More info here:
https://rclone.org/docs/#connection-strings
https://rclone.org/s3/#s3-v2-auth

PS: I suggest you update to the latest version from here: https://rclone.org/downloads/

Thank you so much, Ole! This was exactly what I was looking for and now it works. :raised_hands:

1 Like

You are welcome Jakob, happy copying :slight_smile: