# Master not discovered yet, this node has not previously joined a bootstrapped **URL:** \ **Category:** Elasticsearch\ **Created:** [April 1, 2023, 3:13am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped/329093 "2023-04-01T03:13:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![williamsun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/williamsun/32/119245_2.png) [@williamsun](https://discuss.elastic.co/u/williamsun)\ **Post date:** [April 1, 2023, 3:13am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped/329093/1 "2023-04-01T03:13:28Z")
My issue is related to the last post. # [Master not discovered yet, this node has not previously joined a bootstrapped](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped/289075) ====== I installed Elasticsearch 8.7.0 on AWS EKS 1.23 with three master Pods, three Data Pods and two ingest Pods. I got the following error. Can I use the same solution as [Maks\_7v](https://discuss.elastic.co/u/Maks_7v) pointed out? If yes, how can I put the Elasticsearch configuration into the EKS Elastic pod? Thank you very much for your help in advance! {"@timestamp":"2023-04-01T03:00:31.503Z", "log.level": "WARN", "message":"master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [quickstart-es-default-0, quickstart-es-default-1, quickstart-es-default-2] to bootstrap a cluster: have discovered [{quickstart-es-default-0}{4zuvGo1NSb-uTFXYGe93zw}{A\_tUkXuIRLyMByS9g-A-MA}{quickstart-es-default-0}{10.0.80.153}{10.0.80.153:9300}{m}{8.7.0}]; discovery will continue using [10.0.19.103:9300, 10.0.50.34:9300] from hosts providers and [{quickstart-es-default-0}{4zuvGo1NSb-uTFXYGe93zw}{A\_tUkXuIRLyMByS9g-A-MA}{quickstart-es-default-0}{10.0.80.153}{10.0.80.153:9300}{m}{8.7.0}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see [Troubleshooting discovery | Elasticsearch Guide [8.7] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.7/discovery-troubleshooting.html)", "ecs.version": "1.2.0","service.name":"ES\_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[quickstart-es-default-0][cluster\_coordination][T#1]","log.logger":"org.elasticsearch.cluster.coordination.ClusterFormationFailureHelper","elasticsearch.node.name":"quickstart-es-default-0","elasticsearch.cluster.name":"quickstart"} ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 1, 2023, 6:20am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped/329093/2 "2023-04-01T06:20:37Z")
Perhaps you should look at this if you want a well-configured cluster set up quickly and easily on EKS. > **[GitHub - sunileman/1ClickECK: 1Click Automation of Elastic Cloud on Kubernetes](https://github.com/sunileman/1ClickECK)** > > 1Click Automation of Elastic Cloud on Kubernetes. Contribute to sunileman/1ClickECK development by creating an account on GitHub. This is written/guided by one of our most advanced team members in this area @Sunile_Manjee ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 29, 2023, 6:21am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped/329093/3 "2023-04-29T06:21:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.