@nebulon said in S3 Storage Support:
Do you have more background info on this? Are there any specific errors or hints what those missing S3 transports are? The more info we get the more likely it is to add it to the package.
For example, I've access to Hetzner's BETA for its new S3 API Compatible storage, and when I try to implement it I use "S3 API Compatible (v4)" and when I try to save it I get this error message:
Error listing objects. Message: null HTTP Code: NoSuchKeyCould that be the problem, or alt least this could be another 'bug', is this ringing a bell for you?