http-aws-es
http-aws-es copied to clipboard
TheDeveloper
Upgrade to latest es
Is there a reason this still is on ES 15 and hasn't been updated in 2 years?
It seems like if anything, you should update to the code in this fork - https://github.com/minhloi/http-aws-es so you get all the new stuff.
Thoughts?
bummer I was about to use this but it is out of date, can we get a PullRequest from that fork merge in ?
Hi, I'm looking for maintainers to help with this, if anyone is interested please message me.
So you are wanting someone to help you maintain this project? I may be a bit out of it, but what are other people doing who need to make signed requests to AWS Elasticsearch doing? I guess I am surprised this project doesn't have more use and traction. I may be open to helping maintain it.
@mrn3 It's been a while since I looked into the latest. But there still seems to be demand for this module. Perhaps it's only those who wish to query elasticsearch directly from the browser, as server-side you can configure access through vpc or iam roles.
My understanding is that even with iam roles you need to sign the request (didn't work without it for me). In my case it is for a proof of concept but we will go with vpc once we start development and then I should be good without this plugin, so it is a nice to have but I will work with the old version for the poc. thanks for the quick reply
Elasticsearch Services recently added VPC-endpoint support, but I am considering to continue using HTTP-endpoint ES for some reasons, so http-aws-es helps me a lot.
I wish I could contribute to maintaiing this project. I would like to know what are the blocker issues on using http-aws-es with recent Elasticsearch and/or Elasticsearch client for JavaScript.
I don’t know about being able to use the ES node client to communicate with aws ES without applying your own sig4 solution. I tested with http-aws-es and comm works, otherwise I get authorization errors. Also, aws docs for ES mention having to provide a sig4 when talking to ES. I don’t see a way around it?
People are likely using non-IAM authentication to communicate with their ES, if they’re not signing.
Using VPC ES only controls the privacy of the domain, I.e. via IGW or locally within VPC, not related to authorization.. am I misunderstanding?
