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
{{ message }}
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.
Issue: Cannot connect to AWS Elastic Service due to requiring Signed Requests, and additionally, whitelisting the IP (and thus bypassing authentication and the AWS Signature requirement) is unable to be established due to the Username and Password field being mandatory.
Suggestion: It seems there a number of "Cloud" offerings for Elasticsearch available, specifically for me AWS but looks like there is a GCP requirement too, it would be good if there could be additional variables that could be set e.g:
Username and Password as optional for requests originating from IP access lists
Port number optional e.g. just HTTPS (Yes, :443 works but it's not really required)
Ability to enable AWS Signature v4 on the request, and specify the required Access_Key and Secret_Key to sign the request with
That's all the features I can think of at the moment - I appreciate there hasn't been a release to this in some time but If you don't ask, you don't get!
Thank You!
Oliver
The text was updated successfully, but these errors were encountered:
Issue: Cannot connect to AWS Elastic Service due to requiring Signed Requests, and additionally, whitelisting the IP (and thus bypassing authentication and the AWS Signature requirement) is unable to be established due to the Username and Password field being mandatory.
Suggestion: It seems there a number of "Cloud" offerings for Elasticsearch available, specifically for me AWS but looks like there is a GCP requirement too, it would be good if there could be additional variables that could be set e.g:
That's all the features I can think of at the moment - I appreciate there hasn't been a release to this in some time but If you don't ask, you don't get!
Thank You!
Oliver
The text was updated successfully, but these errors were encountered: