ES 6.4.0 repository S3 issue

[theMike (mike)]

Hi,
I'm trying to use repository-s3 to snapshot a single node ELK instance to our StorageGrid via S3 api.

{
 "type": "s3",
 "settings": {
   "endpoint": "objectstore.xxxx.xxx:xxxx",
   "bucket": "our-elk-backup"
 }
}

bin/elasticsearch-keystore add s3.client.default.access_key
bin/elasticsearch-keystore add s3.client.default.secret_key

All user groups have full access permissions

{
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": "urn:sgws:s3:::*"
        }
    ]
}

Using the latest aws-cli from the ELK server I'm able to read and write to all buckets however when trying to register a snapshot the following error is returned:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_verification_exception",
        "reason" : "[elk-backup] path  is not accessible on master node"
      }
    ],
    "type" : "repository_verification_exception",
    "reason" : "[elk-backup] path  is not accessible on master node",
    "caused_by" : {
      "type" : "i_o_exception",
      "reason" : "Unable to upload object [tests-NXVHCLNAQx-BL554v1CyUA/master.dat] using a single upload",
      "caused_by" : {
        "type" : "amazon_s3_exception",
        "reason" : "Method Not Allowed (Service: Amazon S3; Status Code: 405; Error Code: 405 Method Not Allowed; Request ID: null; S3 Extended Request ID: null)"
      }
    }
  },
  "status" : 500
}

From similar threads, there is the suggestion that this may be an API compatibility issue however how does that explain why the latest aws-cli works?

If all else fails, would using S3FS be an alternative here?

Thanks.

[dadoonet (David Pilato)]

I'd start a 7.14.1 cluster and try to register the repository on that test cluster.

You can also try with 6.8.x.

Then I'd recommend to at least upgrade to 6.8 but better to 7.14.

[theMike (mike)]

Thanks, tried it with 7.9.1 and it worked.