# Elasticsearch can't recognise \_ec2\_

**URL:** <https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [February 24, 2022, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128 "2022-02-24T08:18:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rachit\_upadhyay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rachit_upadhyay/32/102263_2.png) [@rachit\_upadhyay](https://discuss.elastic.co/u/rachit_upadhyay)\
**Post date:** [February 24, 2022, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/1 "2022-02-24T08:18:38Z")

</div>

Getting the following error "org.Elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: Failed to parse value [_ec2_] for setting [transport.publish\_port]".

This is where in the Elasticsearch.yml, the error is coming up.

```auto
network.publish_host: _ec2_
transport.publish_port: _ec2_

```

Dockerfile where I am installing the plugin.  
`RUN bin/elasticsearch-plugin install -b discovery-ec2`

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [February 24, 2022, 9:15am UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/2 "2022-02-24T09:15:12Z")

</div>

those values are for the host not the port setting IIRC.

---

<div class="post-metadata">

**Author:** ![rachit\_upadhyay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rachit_upadhyay/32/102263_2.png) [@rachit\_upadhyay](https://discuss.elastic.co/u/rachit_upadhyay)\
**Post date:** [February 24, 2022, 9:27am UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/3 "2022-02-24T09:27:46Z")

</div>

So, what can I put here for the value of the internal ipv4. I need the network.publish\_host to be the internal ipv4 of the ec2 instance.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [February 24, 2022, 1:44pm UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/4 "2022-02-24T13:44:08Z")

</div>

It's a port, so why not keep the default? The discovery is about finding the right ip addresses, not ports.

---

<div class="post-metadata">

**Author:** ![rachit\_upadhyay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rachit_upadhyay/32/102263_2.png) [@rachit\_upadhyay](https://discuss.elastic.co/u/rachit_upadhyay)\
**Post date:** [February 24, 2022, 8:19pm UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/5 "2022-02-24T20:19:38Z")

</div>

I see . Thanks for the help.

---

<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:** [March 24, 2022, 8:19pm UTC](https://discuss.elastic.co/t/elasticsearch-cant-recognise-ec2/298128/6 "2022-03-24T20:19:45Z")

</div>

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