@lovasoa I think I will need to test it with something like MinIO and make some docs.
Do you miss anything related with this?

Also, I would appreciate if you check the commit for the test "run_all_sql_test_files" commit1 commit2

Hi !
Thanks for taking a stab at this !
This is a large PR and I am currently quite busy so it may take some time, but here are my initial remarks:

• we need a single well tested and well documented feature per PR
  • in this case we need tests that exercise upload / download against an open source s3 implementation
  • the ci times should not increase too much
• adding new dependencies is costly, we need some reassurance about: compiled binary size increase, compile time increase, how well the dependencies are maintained
• the documentation needs to be available on the official site
• i'm not a huge fan of interpreting the same argument as either a file path or a base64 string. If a file has a name that is a valid base64 string, it can get uploaded instead of base64 data.
• no custom bespoke security rules. I don't think we should forbid uploading files outside the web root. On the contrary it should be encouraged.
• I think the user should be able to upload to different buckets let them provide s3://{bucket}/{key}, not just key.

Hi @a-gonzalo

Instead of MinIO (MinIO just move in maintenance mode ) , maybe we can use RustFS

Regards,

I'm not sure RustFS is production-ready...