Issue with S3-repository with two different elasticsearch cluster

Hello,

I am having a configuration problem on two different elasticsearch cluster.
I follow this documentation about s3-repository
https://www.elastic.co/guide/en/elasticsearch/plugins/6.8/repository-s3-repository.html

The context is that I have a cluster in version 5.6.x with which I configured the s3-repository in this way:

PUT _snapshot/test
{
"type": "s3",
"settings": {
"bucket": "test",
"endpoint": "endpoint.test.com",
"protocol": "https",
"compress" : "true",
"path_style_access": "true",
"access_key": "xxxxxxx",
"secret_key": "xxxxxxxxxxxxx"
}
}

with success :

{
"acknowledged" : true
}

Then, I make several snapshot with success status.

On the other hand, I have a cluster in version 6.8.x with which I want to restore the snapshot of the previous cluster.

I have set access_key and secret_key with elasticsearch-keystore tools and I have set in elasticsearch.yml the endpoint.
A important note is that our S3 endpoint is a compatible-S3 storage.

Here is the command launched:

PUT _snapshot/test
{
"type": "s3",
"settings": {
"bucket": "test",
"protocol": "https",
"compress": "true",
"path_style_access": "true"
}
}

However, when creating the repository, I receive an error.

{
"error": {
"root_cause": [
{
"type": "repository_verification_exception",
"reason": "[test] path is not accessible on master node"
}
],
"type": "repository_verification_exception",
"reason": "[test] path is not accessible on master node",
"caused_by": {
"type": "i_o_exception",
"reason": "Unable to upload object [tests-Z1PZYXBaT1-Asddv5ebkgA/master.dat] using a single upload",
"caused_by": {
"type": "amazon_s3_exception",
"reason": "amazon_s3_exception: The specified bucket does not exist (Service: Amazon S3; Status Code: 404; Error Code: NoSuchBucket; Request ID: 0a582f0b:1704226f066:369a8:2ce8; S3 Extended Request ID: null)"
}
}
},
"status": 500
}

But the bucket exist in the s3 because I can browse it with aws cli s3 ls command:

#sudo aws --endpoint-url https://endpoint.test.com/ s3 ls "test"
PRE indices/
2020-04-09 16:10:18 29 incompatible-snapshots
2020-04-10 21:26:04 813 index-2
2020-04-10 21:26:51 929 index-3
2020-04-10 21:26:52 8 index.latest
2020-04-09 21:44:40 103 meta-IczDAurFQ46ih3hHp7gilA.dat
2020-04-09 16:06:41 103 meta-JIY6iTVdQy-GbEhbyqSvjQ.dat
2020-04-10 21:26:48 103 meta-Zxj_xYA3TP2alhTG59HBpw.dat
2020-04-10 21:24:32 103 meta-b1vx1Fn4RSmzzF-bEgmzRw.dat
2020-04-09 21:46:14 239 snap-IczDAurFQ46ih3hHp7gilA.dat
2020-04-09 16:08:16 236 snap-JIY6iTVdQy-GbEhbyqSvjQ.dat
2020-04-10 21:26:51 235 snap-Zxj_xYA3TP2alhTG59HBpw.dat
2020-04-10 21:26:03 236 snap-b1vx1Fn4RSmzzF-bEgmzRw.dat

There is a permission access issue ?
I don't understand why in 5.6.x cluster this s3 repository work and not in 6.8...?
If someone can help me ?
Thanks

Hi all,
For this issue, it's resolve .
For 6.8.x , to connect S3 repository for snapshot, it must be format the bucket name with an older name style like put an underscore in the name .

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.