S3 sink connector fails with "invalid version id specified" error

I have a s3 sink connector (10.0.0) configured to basically make a golden copy of my messages on our pure storage system. It runs but after a while it fails with the error

„invalid version id specified (Service: S3, Status Code: 400, Request ID: null).

Is this implying that the bucket must have versioning activated?

In the connector documentation I didn‘t find any information that this might be a requirement or is the error related to something totally different ?