kiwigrid/helm-charts

Help Connecting to Managed AWS ES

Closed this issue · 2 comments

Deleted user commented

Version of Helm and Kubernetes:
Helm: 2.14.3
Kubernetes: 1.13.5

Which chart in which version:
Fluentd-elasticsearch

What happened:

2020-02-11 21:46:59 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached
2020-02-11 21:46:59 +0000 [warn]: [elasticsearch] Remaining retry: 14. Retry to communicate after 2 second(s).
2020-02-11 21:47:08 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached
2020-02-11 21:47:08 +0000 [warn]: [elasticsearch] Remaining retry: 13. Retry to communicate after 4 second(s).
2020-02-11 21:47:21 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached
2020-02-11 21:47:21 +0000 [warn]: [elasticsearch] Remaining retry: 12. Retry to communicate after 8 second(s).
2020-02-11 21:47:38 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. end of file reached (EOFError)
2020-02-11 21:47:38 +0000 [warn]: [elasticsearch] Remaining retry: 11. Retry to communicate after 16 second(s).
2020-02-11 21:48:15 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached
2020-02-11 21:48:15 +0000 [warn]: [elasticsearch] Remaining retry: 10. Retry to communicate after 32 second(s).
2020-02-11 21:49:19 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. Cannot assign requested address - connect(2) for [::1]:8080 (Errno::EADDRNOTAVAIL)
2020-02-11 21:49:19 +0000 [warn]: [elasticsearch] Remaining retry: 9. Retry to communicate after 64 second(s).
2020-02-11 21:51:32 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached
2020-02-11 21:51:32 +0000 [warn]: [elasticsearch] Remaining retry: 8. Retry to communicate after 128 second(s).

What you expected to happen:

Connect to ES

How to reproduce it (as minimally and precisely as possible):

enabled aws signing sidecar
added host endpoint
installed helm chart

Anything else we need to know:

monotek commented

Sorry, we're not using AWS and therefore can't support you here.

In fact the aws support was added by @SandyChapman as a community contribution.
Maybe he can give you some advice.

tony-kerz commented

@james-knott @SandyChapman i'm experiencing similar, any tips or tricks?

  • i verified that i can connect from worker-node to aws-elk endpoint with net-cat
  • my basic auth user has all_access privs
2020-08-11 17:12:11 +0000 [warn]: [elasticsearch] Remaining retry: 8. Retry to communicate after 128 second(s).
2020-08-11 17:16:32 +0000 [warn]: [elasticsearch] Could not communicate to Elasticsearch, resetting connection and trying again. read timeout reached