You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I am currently using elastigo with Amazon ElasticSearch, and it indeed works. The only problem is, Amazon ElasticSearch is highly limited in how it can be authenticated with; it supports hardcoding IPs, OR using Amazon signed requests. (For those familiar with AWS, it does not even support limiting things via VPC, as Amazon ElasticSearch does not support VPC at all.)
So, I am creating this issue to track the idea of adding support for these signed requests. It would probably be trivial, but to make sure it's done correctly it'd be smart to delegate the actual implementation to another library. Matt Holt created go-aws-auth for this purpose and it would probably be the most minimal way to make this work.
I plan on implementing this in a fork shortly regardless of whether or not it gets merged.
The text was updated successfully, but these errors were encountered:
Hi. I am currently using elastigo with Amazon ElasticSearch, and it indeed works. The only problem is, Amazon ElasticSearch is highly limited in how it can be authenticated with; it supports hardcoding IPs, OR using Amazon signed requests. (For those familiar with AWS, it does not even support limiting things via VPC, as Amazon ElasticSearch does not support VPC at all.)
So, I am creating this issue to track the idea of adding support for these signed requests. It would probably be trivial, but to make sure it's done correctly it'd be smart to delegate the actual implementation to another library. Matt Holt created go-aws-auth for this purpose and it would probably be the most minimal way to make this work.
I plan on implementing this in a fork shortly regardless of whether or not it gets merged.
The text was updated successfully, but these errors were encountered: