S3: Rclone v.1.52.0 or after: permission denied

[ncw (Nick Craig-Wood)]

What happened is that I fixed a bug in the s3 backend which wasn't reporting errors on bucket creation properly.

This then surfaced the fact that people like yourself had been depending on that bug!

The no_check_bucket = true means that rclone won't attempt to see if the bucket really exists or try to create it.

@carles

It worked! I see that then rclone puts the credentials, etc. in the PUT path instead of the different HTTP header.

That is to work around a limitation of the SDK, but it shouldn't make any difference.

@carles

Are we missing some permissions on the Amazon S3 side that rclone expects? I had the same ones as other buckets but the other buckets were created long time ago (probably before the Amazon S3 path changes?)

If you don't want to use that flag, then rclone would like to be able to create buckets. If you don't want that then no_check_bucket = true is the workaround.