S3 - confused about style, path versus virtual

What is the problem you are having with rclone?

wanted to confirm that rclone with s3, by default, uses path style, virtual host style or something else?

confused about rclone docs.

read from Rclone 1.51 release
"Force path style bucket access to off for AWS deprecation"

that seems to conflict with
"If this is true (the default) then rclone will use path style access"

then aws s3 docs https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/
"Support for the path-style model continues for buckets created on or before September 30, 2020. Buckets created after that date must be referenced using the virtual-hosted model."

yet rclone works fine as is, with aws s3 and wasabi.

What is your rclone version (output from rclone version)

rclone v1.53.3
- os/arch: windows/amd64
- go version: go1.15.5

Which OS you are using and how many bits (eg Windows 7, 64 bit)


Which cloud storage system are you using? (eg Google Drive)

aws and wasabi

The command you were trying to run (eg rclone copy /tmp remote:tmp)

no command, as this is a general question. will provide if requested.

The rclone config contents with secrets removed.

no config, as this is a general question. will provide if requested.

A log from the command with the -vv flag

no log, as this is a general question. will provide if requested.


Rclone chooses a different default depending on the value of the provider setting.

So if you choose aws then path style defaults to false (and also for some other providers) otherwise it defaults to true.

The docs should probably mention this do you think?

yes, that would be helpful.

for now, where can i find the all the default values for wasabi?
i tried at https://github.com/rclone/rclone/tree/master/backend/s3

Here is the override being set

This list does not include Wasabi - maybe it should?

i think so, that wasabi is a major s3 clone provider

tho i am not sure what the value should be.

as per wasabi, https://wasabi.com/wp-content/themes/wasabi/docs/API_Guide/topics/Host_Designation.htm
"Wasabi supports both the path-style and virtual-style requests available with AWS S3. A different host name is required (for example, s3.wasabisys.com versus s3.amazonaws.com). Wasabi recommends using path-style requests as shown in all examples in this Guide (for example, http://s3.wasabisys.com/my-bucket/my-object) because the path-style offers the greatest flexibility in bucket names, avoiding domain name issues"

i am contacting wasabi, and see if that document is up to date.
i will update this post after they reply.

thanks much,

1 Like

Were you having specific problems with wasabi?

tl;dr - no specific problem with rclone and wasabi.

i use s3browser, with aws s3 and wasabi.
it has a nice gui, for IAM and a bucket sharing wizard.
that was not working well with wasabi.

so i have been working with them on a new beta, for better wasabi compatibility.
to get those features working, they want me to use virtual path style.
something i never thought about, so when i checked what rclone was doing, it was using path style.

then you asked about adding wasabi to the list.
so then i went to wasabi.com and found out they still recommend, path style, which is what rclone is using.
but so far s3browser seems to be working with virtual style.

i am concerned about using both styles at the same time for wasabi.

I think either should work. Just like either works with AWS (until a cutoff date)

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.