Setting AWS Snapshot Repository Fails For VirtualHost


(Steven Arnott) #1

ES 5.6.3

When setting up a S3 snapshot repository, using the default endpoint works

{ "type" : "s3", "settings" : { "bucket" : "a-bucket", "region" : "us-east-1" } } 

However, as we are using a proxy to get to AWS, we want to use Virtual Host based so our proxy rules do not need to allow all of S3.

This does not work:

{ "type" : "s3", "settings" : { "bucket" : "a-bucket", "endpoint" : "a-bucket.s3.amazonaws.com"} } 
{"type":"amazon_s3_exception",
"reason":"amazon_s3_exception: The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: E3472D6FCF883CCE)"
}}},

Is there a way to enable more debuging logs for the S3 plugin, so we can dig further?

Any suggestions?


(David Pilato) #2

endpoint should be us-east-1.s3.amazonaws.com I think.


(Steven Arnott) #3

Only if your using path based access.. this is using virtual host based where the bucket name forms part of the host.

EDIT: Oh wait your saying that having a end point means the code adds bucket to endpoint to create the host?


(Steven Arnott) #4

OK can confirm that

    "type" : "s3",
    "settings" : {
      "bucket" : "a-bucket",
      "endpoint" : "s3.amazonaws.com"
    }
  }

works... I'd suggest that maybe a guided example be added to the documentation


(system) #6

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