Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iI suggest introducing absolute path access for S3 storage. #3740

Closed
duckgun13476 opened this issue Jul 25, 2024 · 5 comments
Closed

iI suggest introducing absolute path access for S3 storage. #3740

duckgun13476 opened this issue Jul 25, 2024 · 5 comments
Labels
enhancement New feature or request Stale

Comments

@duckgun13476
Copy link

duckgun13476 commented Jul 25, 2024

The S3 protocol uses Vhost mode in this project to meet most storage needs. However, when using S3-compatible storage, there are many compatibility issues with Vhost mode. While it ensures the separation of bucket access and user security, establishing a usable Vhost storage bucket is relatively cumbersome for S3-compatible storage due to the need for resolution settings. On the other hand, absolute path access can solve this problem; it does not require setting up resolution records and has strong compatibility. It is also the access method used by most S3 storage solutions.


Suggested modifications for the author:
You just need to add a button to decide whether to use S3 storage path style, and change the way to access the bucket from bucket.IP:port to IP:port/bucket.

Type of feature

API

Additional context

Reference source, issue source #3655

@WyInnovate
Copy link

Seconded
Normally, the Amazon S3 SDK allows for the selection of Addressing
You can add an Addressing option in the S3 settings, which includes
1.Virtual-hosted-style
2.Path-style

@Gavincent1
Copy link

It seems that in version 0.21 and earlier versions, it is accessed in the way you suggested, but I don't know why the later update was cancelled. There is not even a compatibility option switch, which is a replacement update. I still use version 0.21 in my official environment.

@github-actions github-actions bot added the Stale label Aug 9, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
@jinnatar
Copy link

jinnatar commented Dec 9, 2024

This is still an issue and should be re-opened, but sadly the stale bot got to it first.

S3 path mode would open up compatibility to many more S3 compatible storage sources that choose not to implement host mode.

@johnnyjoygh
Copy link
Collaborator

Currently, Amazon S3 supports both virtual-hosted–style and path-style URL access in all AWS Regions. However, path-style URLs will be discontinued in the future.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#path-style-access

@jinnatar The path-style URL is already deprecated since 2020, so there's no reason to support it.

@jinnatar
Copy link

If you are using Amazon, yes. There are however a plethora of other providers and since path style is trivial to implement, vs the setup required to provide vhosts, some opt to not support vhosts. In my case Ceph does support them, but this is the first service where I finally need to go set it all up, which is far from trivial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

5 participants