S3 Compatibility Improvements

[iglesiasbrandon]

Summary:

One of the main ways we can drive adoption for V3 is to have great s3 compatibility support. The community and our users have pointed out areas we could improve our s3 compatibility which could make it easier to transition from s3 to V3.

Pain Point:

• There are still some s3 features we don't fully support. For example, when doing a list operation the objects are not sorted in lexicographical order which is how s3 sorts objects.

Intended Outcome:

• S3 compatibility shortcomings are fixed so that we have better S3 support for users.

Links

Gateway-MT Milestone: https://github.com/storj/gateway-mt/milestone/3
Gateway-ST Milestone: https://github.com/storj/gateway-st/milestone/1

[jtolio]

Comment from OKR tracking sheet:

Need to better define acceptance criteria.

[shaupt131]

Edge team assembled this excellent resource for what S3 features currently are and are not supported by V3: https://github.com/storj/gateway-st/blob/main/docs/s3-compatibility.md

[ferristocrat]

Closing this issue out since we are not actively working on any S3 compatibility items. For S3 compatibility improvements that get prioritized, we will create individual roadmap items (such as S3 Compatibility - UploadPartCopy #40)

[storjrobot]

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/lets-talk-about-the-elephant-in-the-room-the-storj-economic-model-node-operator-payout-model/20127/367