#31608 Add S3 Setting to Force Path Type Access (#34721)

* SNAPSHOTS: Use Path Style Access in S3

* Use path style access pattern to fix #31608
* closes #31608
This commit is contained in:
Armin Braun 2018-11-09 05:07:26 +01:00 committed by GitHub
parent bccc99c2be
commit 02b4e28534
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 12 additions and 1 deletions

View File

@ -304,6 +304,9 @@ You may further restrict the permissions by specifying a prefix within the bucke
The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository
registration will fail.
Note: Starting in version 7.0, all bucket operations are using the path style access pattern. In previous versions the decision to use virtual hosted style
or path style access was made by the AWS Java SDK.
[[repository-s3-aws-vpc]]
[float]
==== AWS VPC Bandwidth Settings

View File

@ -22,6 +22,13 @@ must now be specified in the client settings instead.
See {plugins}/repository-gcs-client.html#repository-gcs-client[Google Cloud Storage Client Settings].
[float]
==== S3 Repository Plugin
* The plugin now uses the path style access pattern for all requests.
In previous versions it was automatically determining whether to use virtual hosted style or path style
access.
[float]
==== Analysis Plugin changes

View File

@ -107,7 +107,8 @@ class S3Service extends AbstractComponent implements Closeable {
//
// We do this because directly constructing the client is deprecated (was already deprecated in 1.1.223 too)
// so this change removes that usage of a deprecated API.
builder.withEndpointConfiguration(new AwsClientBuilder.EndpointConfiguration(endpoint, null));
builder.withEndpointConfiguration(new AwsClientBuilder.EndpointConfiguration(endpoint, null))
.enablePathStyleAccess();
return builder.build();
}