Preserve file/folder structure in S3 without urn:oid

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

I try to use S3 as a primary object storage, but file names and folder structures are not preserved.
All files in S3 are in urn:oid w/ appended numbers, which seems like a database entry for metadata.

With this limitation, I cannot access files from S3. I always have to go to Nextcloud's console.
File sharing outside of Nextcloud is also way more difficult than local storage case.

Without S3 storage, unless I have a large local storage, it is not easy to extend user base as well.

Describe the solution you'd like

Help us to find the files/folders on S3 bucket, just like it is done in local storage.
Although /data folder in local server is not accessible by default, as a server admin, I can still see what's going on in there.
The same privilege should be reserved for S3.

Describe alternatives you've considered

Not much. I wonder how other people use S3, if this is not supported.

Additional context

If file/folder access is limited to Nextcloud only, I have to look for other solutions for file stroage + team collaboration.
Despite all wonderful functions that I push forward Nextcloud to the team, I think shared external storage is a key for running a server, especially in case of server failure.

No file, test, or entry point is identified in the issue. Start by tracing Nextcloud's S3 primary-storage implementation and how urn:oid names are generated, then compare it with local storage path handling. Done should mean that administrators can find files and folders in S3 with their original structure while Nextcloud continues to access them.