I’ve had same issue, and I can confirm that Amazon S3 version 2.3.11 solved it.
One thing worth mention is pay attention to the Amazon S3 Host
settings, in my case I had to change that part in the extension settings from us-east-2
to us-east-1
, and that did the trick.
I hope this helps someone.