-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Path-style S3 access is deprecated #41816
Comments
Pinging @elastic/es-distributed |
Hitting this issue with Alibaba Cloud OSS service (S3 like service), it only supports virtual host style access. |
IMO, as nice as it was to get rid of this config option, we should simply add back the setting to choose between path and DNS style access. |
Adding the config option back would be great. Thanks! |
We discussed this during today's team sync. The fact that AWS will stop supporting the path style access pattern makes the solution build in #34721 not viable long term. I will open a PR (to go into |
* As discussed, added the option to use path style access back again and deprecated it. * Defaulted to `false` * Added warning to docs * Closes elastic#41816
* Provide an Option to Use Path-Style-Access with S3 Repo * As discussed, added the option to use path style access back again and deprecated it. * Defaulted to `false` * Added warning to docs * Closes #41816
* Provide an Option to Use Path-Style-Access with S3 Repo * As discussed, added the option to use path style access back again and deprecated it. * Defaulted to `false` * Added warning to docs * Closes elastic#41816
It was recently announced that path-style access to S3 is deprecated will be rejected by S3 starting 2020-09-30. However, since #34721 (i.e. 7.0), the
repository-s3
plugin exclusively uses path-style access, to make it easier to use Minio-backed repositories. This needs a re-think.The text was updated successfully, but these errors were encountered: