Closed Whitebrim closed 1 month ago
I'm not familiar with aws, but why should we use a legacy request style?
For deployment of S3-compatible implementations (e.g. minio, garage, seaweedfs) that do not use or support virtual-host-style requests (i.e. subdomains). For example, with path style requests, the request should be made to s3.brim.su
(with bucket in the URL path instead of being a subdomain) instead of brimworld-api.s3.brim.su
domain. AWS SDKs supports this behavior with force_path_style option. See also https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html
To be clear, this should be a boolean option in the service config since this behavior is legacy only for Amazon-hosted S3 service.
To be clear, this should be a boolean option in the service config
And false
by default, I need it to be true, but Amazon S3 users won't change it.
It's working now, thank you ❤️
Describe your feature request.
Please add https://sdk.amazonaws.com/kotlin/api/latest/s3/aws.sdk.kotlin.services.s3/-s3-client/-config/-builder/force-path-style.html to config
Additional context