# EC2 VPC Discovery Issues

**URL:** <https://discuss.elastic.co/t/ec2-vpc-discovery-issues/10580>\
**Category:** Elasticsearch\
**Created:** [February 1, 2013, 1:43am UTC](https://discuss.elastic.co/t/ec2-vpc-discovery-issues/10580 "2013-02-01T01:43:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NickHaggmark](https://avatars.discourse-cdn.com/v4/letter/n/5e9695/32.png) [@NickHaggmark](https://discuss.elastic.co/u/NickHaggmark)\
**Post date:** [February 1, 2013, 1:43am UTC](https://discuss.elastic.co/t/ec2-vpc-discovery-issues/10580/1 "2013-02-01T01:43:24Z")

</div>

Hi Guys,

I've recently spun up a new ES cluster (2 nodes) to replace my old stack.  
The new cluster is using the newest ES version (0.20.4) and newest AWS  
plugin (1.10.0) and is backing to S3. I cannot get them to talk to each  
other now and it's making me crazy. I'm using two Ubuntu 12.04 EC2  
instances inside of a VPC. The nodes are in the same region, zone and  
subnet and the security groups for both the LB and EC2 instances both have  
9200 and 9300 open to the world.

Here is a copy of their config files:

------- NODE 1 -------

################################### Cluster  
###################################

cluster.name: wtrsearch  
node.name: node1

#################################### Index  
####################################

index.number\_of\_shards: 6  
index.number\_of\_replicas: 1

#################################### Paths  
####################################

path.data: /usr/local/var/data/elasticsearch  
path.logs: /usr/local/var/log/elasticsearch

################################### Memory  
####################################

bootstrap.mlockall: true

################################## Discovery  
##################################  
discovery.type: ec2  
discovery.ec2.availability\_zones: us-west-1a  
discovery.ec2.ping\_timeout: 30s  
discovery.ec2.tag: wtrsearch\_production

cloud.node.auto\_attributes: true  
cloud.aws.region: us-west-1  
cloud.aws.access\_key: [omitted]  
cloud.aws.secret\_key: [omitted]

################################## Persistence  
##################################  
gateway.type: s3  
gateway.s3.bucket: wtr-search-data-us-west-1-test

------- NODE 2 -------

################################### Cluster  
###################################

cluster.name: wtrsearch  
node.name: node2

#################################### Index  
####################################

index.number\_of\_shards: 6  
index.number\_of\_replicas: 1

#################################### Paths  
####################################

path.data: /usr/local/var/data/elasticsearch  
path.logs: /usr/local/var/log/elasticsearch

################################### Memory  
####################################

bootstrap.mlockall: true

################################## Discovery  
##################################  
discovery.type: ec2  
discovery.ec2.availability\_zones: us-west-1a  
discovery.ec2.ping\_timeout: 30s  
discovery.ec2.tag: wtrsearch\_production

cloud.node.auto\_attributes: true  
cloud.aws.region: us-west-1  
cloud.aws.access\_key: [omitted]  
cloud.aws.secret\_key: [omitted]

################################## Persistence  
##################################  
gateway.type: s3  
gateway.s3.bucket: wtr-search-data-us-west-1-test

* * *

Can anyone think of any reason why these two wouldn't be able to talk to  
one another? I'm absolutely pulling my hair out.

They both have cluster health outputs that look like this:

{

- cluster\_name: wtr\_search\_production
- status: green
- timed\_out: false
- number\_of\_nodes: 1
- number\_of\_data\_nodes: 1
- active\_primary\_shards: 0
- active\_shards: 0
- relocating\_shards: 0
- initializing\_shards: 0
- unassigned\_shards: 0

}

They both have cluster state outputs that look like this:

{

- cluster\_name: wtr\_search\_production
- master\_node: HPscfXXMQNqSIuXA3b6MLQ
- blocks: { }
- nodes: {
  - HPscfXXMQNqSIuXA3b6MLQ: {
    - name: wtr-search-watchtower-i-70776729
    - transport\_address: inet[/10.200.60.18:9300]
    - attributes: {
      - aws\_availability\_zone: us-west-1a  
}  
}  
}

- metadata: {
  - templates: { }
  - indices: { }  
}

- routing\_table: {
  - indices: { }  
}

- routing\_nodes: {
  - unassigned: []
  - nodes: {
    - HPscfXXMQNqSIuXA3b6MLQ: []  
}  
}

- allocations: []

}

Except with (obviously) different addresses, names and master nodes.

Please help!

Thanks!

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 2:53am UTC](https://discuss.elastic.co/t/ec2-vpc-discovery-issues/10580/2 "2017-07-06T02:53:40Z")

</div>