Associating on secondary subnet not possible

elastic / elasticsearch-cloud-aws

AWS Cloud Plugin for Elasticsearch

https://github.com/elastic/elasticsearch/tree/master/plugins/discovery-ec2

577 stars 181 forks source link

Associating on secondary subnet not possible #224

Open cthorner opened 9 years ago

cthorner commented 9 years ago

Can someone confirm that it is not possible to use the discovery mechanism to associate with a secondary IP address in EC2?

Turning on logging, it looks like the security groups and tags are used for finding the correct server instances, but then the first IP is used even if it does not belong to the security group or tag specified.