I haven’t looked at this in a while, but here’s how I’ve dealt with this in the past:
They don’t consider it a bug because they don’t pretend to support every S3-not-so-compatible service on the planet.
I can’t remember just which sites I was doing this for, but I don’t remember changing anything about this recently, so I’m thinking that this is still the “best” workaround.
I think there were some other topics about this when AWS released the new library that broke everyone else’s offerings.