Signs requests to AWS endpoints (using Signature Version 4 signing process)
- (2020-11-18) Muhammad Owais Ahmed: After upgrading to latest version of chrome, this plugin stopped working
- (2017-10-20) Jenn: Useful but just make sure that you remember to add '=' after get vars (e.g. http://elasticsearch.host/_cluster/stats?v&pretty will not get signed correctly).
- (2016-07-06) David Ascher: It works, which is really helpful for debugging elasticsearch services which have access policies enabled. Only quibble I have is that it's a bit of a pain to configure because the modal dialog keeps disappearing in between copy/paste operations that require tabbing away from the browser. Still, thanks!
- (2020-03-17, v:1.0.5) Walter Vargas-Pena: Error when attempting
Has anyone experienced the following?: "This site can’t be reached" error from chrome when this is enabled?
- (2018-02-01, v:1.0.5) I can my acceskey and secret key in editbox
My suggestion is hide characters of the access key, secret key and token in editbox of the chrome extension. (Other person can to see the keys if he clicks in extension icon). thank you very much
- (2017-11-15, v:1.0.5) Andrey Agibalov: Kibana started to complain
About 2 weeks ago AWS Request Signer helped me a lot to access Kibana. Tried it today and Kibana complains: "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details." It's the same machine, same AWS account and I didn't change the credentials. ES installation is different, though. Any ideas?
- (2016-08-18, v:1.0.2) Ryan Gross: Where does Instance Profile read from?
Does the Instance Profile extension read from ~/.aws/credentials, or only from EC2 instance metadata?
- (2016-08-17, v:1.0.2) John Owen: View the signature
Is there a way to view the calculated signature?