[feature] Custom prefix (or subfolder) for s3

[xnuk]

Assume that I have:

• a instance named example.com
• a general media bucket named s3://my-media-bucket
• a CDN named https://media.example.com, pointing the s3://my-media-bucket.

Looks like GoToSocial stores images in like 01AAAAAAAAAA/attachment/original/01BBBBBBBB.png. Let's call it apple.png for short.

So I want:

• media addresses in my posts are shown like https://media.example.com/gotosocial/apple.png
• which points s3://my-media-bucket/gotosocial/apple.png

But actual:

1. Cannot make GoToSocial to save images in bucket's subfolder - /gotosocial/ in this case.
   • tried storage-s3-bucket: my-media-bucket/gotosocial, but GoToSocial says "Bucket name contains invalid characters".
2. Cannot make media addresses to use media.example.com
   • storage-s3-proxy: false -> https://s3.dualstack.ap-northeast-2.amazonaws.com/my-media-bucket/apple.png
   • storage-s3-proxy: true -> https://example.com/fileserver/apple.png

Currently workaround:

1. Make a new bucket s3://my-media-bucket-gotosocial and make the CDN points there
   • https://media.example.com/gotosocial/* -> s3://my-media-bucket-gotosocial/*
   • The problem is: I don't know how
2. storage-s3-proxy: true and make nginx/caddy redirects to CDN

Problem 2 maybe duplicates of #1026.

Feel free to feedback or edit this issue, because I have poor English writing skills.

---

Opened issues related with AWS S3

• [feature] Allow S3 bucket name to be blank to better support CDN with S3 buckets #1026
• [feature] Allow remapping of S3 endpoint to S3_ALIAS_HOST #1632
• [feature] s3: add option to treat bucket as public #1458

[kkbt0]

#1458 mentioning that the reason for using s3 pre-signed instead of CDN is to restrict access to object storage.
Is there a definite plan to implement this feature ? Or will it not?