-
Notifications
You must be signed in to change notification settings - Fork 796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AWS Elasticsearch using AWS SDK v2 #597
Conversation
Hmm, for some reason, circleci is not running. |
@SuperQ I am thinking maybe because the base is my fork, not the original one. ? |
@SuperQ I found that forked PRs are not considered trusted by default in Circle CI. To make it happen admin needs to perform certain action mentioned in the images. Source of information - https://circleci.com/blog/triggering-trusted-ci-jobs-on-untrusted-forks. |
@rosspatil build forks has been enabled for this repo since the beginning. |
Signed-off-by: Roshan Patil <[email protected]>
Signed-off-by: Roshan Patil <[email protected]>
@SuperQ Now it seems to be running :) |
@sysadmind Your comments are resolved. Could you please review this PR again :) |
@SuperQ @sysadmind Could you please review this PR again? :) |
Signed-off-by: Roshan Patil <[email protected]>
Signed-off-by: Roshan Patil <[email protected]>
@SuperQ @sysadmind Thanks for reviewing PR and approvals. How could we process further? |
Just need to double check with @sysadmind and I think we're good. We also use this exporter some, and want to roll it out to replace our use of CloudWatch for AWS/ES. |
* [FEATURE] Add metrics collection for data stream statistics #592 * [FEATURE] Support for AWS Elasticsearch using AWS SDK v2 #597 * [BUGFIX] Fix cluster settings collection when max_shards_per_node is manually set. #603 Signed-off-by: SuperQ <[email protected]>
* [FEATURE] Add metrics collection for data stream statistics #592 * [FEATURE] Support for AWS Elasticsearch using AWS SDK v2 #597 * [BUGFIX] Fix cluster settings collection when max_shards_per_node is manually set. #603 Signed-off-by: SuperQ <[email protected]>
* [FEATURE] Add metrics collection for data stream statistics #592 * [FEATURE] Support for AWS Elasticsearch using AWS SDK v2 #597 * [BUGFIX] Fix cluster settings collection when max_shards_per_node is manually set. #603 Signed-off-by: SuperQ <[email protected]>
) * Support for AWS Elasticsearch using AWS SDK v2 (#1) Signed-off-by: Roshan Patil <[email protected]> * Fixes PR comments Signed-off-by: Roshan Patil <[email protected]> * Resolved PR comments Signed-off-by: Roshan Patil <[email protected]> * Fix PR comments Signed-off-by: Roshan Patil <[email protected]>
* [FEATURE] Add metrics collection for data stream statistics prometheus-community#592 * [FEATURE] Support for AWS Elasticsearch using AWS SDK v2 prometheus-community#597 * [BUGFIX] Fix cluster settings collection when max_shards_per_node is manually set. prometheus-community#603 Signed-off-by: SuperQ <[email protected]>
fixes #591
Hey @sysadmind & @SuperQ,
I have added support for AWS-based elasticsearch authentication using AWS SDK v2. I saw other PR opened for the same but I wanted to add support using SDK v2 because it provides enormous benefits related to how we use the authentication. It supports out-of-the-box all type of AWS auth mechanisms like env Variable, shared file or web toke file in K8s.
Could you please review the PR and let me know if anything is not appropriate?
Thanks,
Roshan :)