# Cannot form cluster of Elasticsearch on EKS

**URL:** <https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [December 30, 2022, 3:25am UTC](https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186 "2022-12-30T03:25:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zeynal\_Hajili](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zeynal_hajili/32/102383_2.png) [@Zeynal\_Hajili](https://discuss.elastic.co/u/Zeynal_Hajili)\
**Post date:** [December 30, 2022, 3:25am UTC](https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186/1 "2022-12-30T03:25:03Z")

</div>

Hello, dear community,  
I am very new to Elasticsearch. I have been asked to deploy the ELK stack on AWS EKS and unfortunately, I am facing some issues.

I am deploying the ELK stack in the following order via Helm chart with the following commands.

```auto
# helm install elasticsearch elastic/elasticsearch -f k8s/value-elasticsearch.yaml -n monitoring
# helm install kibana elastic/kibana -n monitoring
# helm install fluentd bitnami/fluentd -n monitoring

```

After some time I see that all pods and services are running successfully.

```auto
^Czhajili$ kubectl get pods --namespace=monitoring 
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 1/1 Running 0 14m
elasticsearch-master-1 1/1 Running 0 14m
elasticsearch-master-2 1/1 Running 0 14m
fluentd-0 1/1 Running 0 9m22s
fluentd-2j6h4 1/1 Running 4 (8m24s ago) 9m22s
fluentd-4pt44 1/1 Running 4 (8m19s ago) 9m22s
fluentd-8rl4d 1/1 Running 4 (8m24s ago) 9m22s
fluentd-drcmx 1/1 Running 4 (8m33s ago) 9m22s
kibana-kibana-fc8cbfc5d-xx4fc 1/1 Running 0 10m

```

After applying configmap for fluentd ,I am expecting to see some indices created already ,but I dont see.

After checking logs for elasticsearch I see following logs

```auto
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)\n\t... 16 more\n"}
{"@timestamp":"2022-12-30T18:07:14.300Z", "log.level": "WARN", "message":"http client did not trust this server's certificate, closing connection Netty4HttpChannel{localAddress=/127.0.0.1:9200, remoteAddress=/127.0.0.1:52054}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][transport_worker][T#1]","log.logger":"org.elasticsearch.xpack.security.transport.netty4.SecurityNetty4HttpServerTransport","elasticsearch.cluster.uuid":"l-bWntZXReSXSVs_tGQZzQ","elasticsearch.node.id":"BgxN566LQGiHFOv7FXk2kw","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch"}
{"@timestamp":"2022-12-30T18:07:17.750Z", "log.level": "WARN", "message":"http client did not trust this server's certificate, closing connection Netty4HttpChannel{localAddress=/127.0.0.1:9200, remoteAddress=/127.0.0.1:52068}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][transport_worker][T#1]","log.logger":"org.elasticsearch.xpack.security.transport.netty4.SecurityNetty4HttpServerTransport","elasticsearch.cluster.uuid":"l-bWntZXReSXSVs_tGQZzQ","elasticsearch.node.id":"BgxN566LQGiHFOv7FXk2kw","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch"}
{"@timestamp":"2022-12-30T18:09:22.014Z", "log.level": "WARN", "message":"caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/127.0.0.1:9200, remoteAddress=/127.0.0.1:34872}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][transport_worker][T#1]","log.logger":"org.elasticsearch.http.AbstractHttpServerTransport","elasticsearch.cluster.uuid":"l-bWntZXReSXSVs_tGQZzQ","elasticsearch.node.id":"BgxN566LQGiHFOv7FXk2kw","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch","error.type":"io.netty.handler.codec.DecoderException","error.message":"javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca","error.stack_trace":"io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca\n\tat 

```

Could you please kindly help me?

---

<div class="post-metadata">

**Author:** ![MahithaSarala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahithasarala/32/101721_2.png) [@MahithaSarala](https://discuss.elastic.co/u/MahithaSarala)\
**Post date:** [January 5, 2023, 4:03am UTC](https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186/2 "2023-01-05T04:03:09Z")

</div>

Did you resolved this issue?  
Even i'm also facing same issue

---

<div class="post-metadata">

**Author:** ![username1234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/username1234/32/69446_2.png) [@username1234](https://discuss.elastic.co/u/username1234)\
**Post date:** [January 11, 2023, 9:58pm UTC](https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186/3 "2023-01-11T21:58:43Z")

</div>

I am also facing this issue. I am using the default values.yaml files for helm from the elastic helm charts github repo.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 8, 2023, 9:59pm UTC](https://discuss.elastic.co/t/cannot-form-cluster-of-elasticsearch-on-eks/322186/4 "2023-02-08T21:59:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
