# EC2 Discovery **URL:** \ **Category:** Elasticsearch\ **Created:** [May 17, 2011, 7:04pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427 "2011-05-17T19:04:23Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\ **Post date:** [May 17, 2011, 7:04pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/1 "2011-05-17T19:04:23Z")
I have two identically configured Elastic Search nodes embedded in a web app which is deployed to two different EC2 nodes. However the EC2 servers do not discover each other. This gist includes the log files and the ES discovery Http results. I see both servers in the resulting DescribeInstances logs, but something must be keeping ES from associating them? > The gist also begins with a dump of all the ES properties I am using. Anyone see anything? ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [May 17, 2011, 7:44pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/2 "2011-05-17T19:44:33Z")
Looking at this line: [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] Looks like you're binding to ipv6 address, but the addresses you're getting back from EC2 are ipv4: [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] So that you get no ping responses back for the ipv4 addresses: [Lorelei II] ping responses: {none} I think you may need to set your host correctly in the config. On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > I have two identically configured Elastic Search nodes embedded in a web > app which is deployed to two different EC2 nodes. However the EC2 servers do > not discover each other. > > This gist includes the log files and the ES discovery Http results. I see > both servers in the resulting DescribeInstances logs, but something must be > keeping ES from associating them? > [977123’s gists · GitHub](https://gist.github.com/977123) > > The gist also begins with a dump of all the ES properties I am using. > > Anyone see anything? ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 17, 2011, 8:35pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/3 "2011-05-17T20:35:32Z")
Good catch Paul, I also think that might be the issue. Note in the network page you can set descriptive names like _en0:ipv4_ so you won't have to set it explicitly for each node. On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > Looking at this line: > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > Looks like you're binding to ipv6 address, but the addresses you're getting back from EC2 are ipv4: > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > So that you get no ping responses back for the ipv4 addresses: > > [Lorelei II] ping responses: {none} > I think you may need to set your host correctly in the config. > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > > I have two identically configured Elastic Search nodes embedded in a web app which is deployed to two different EC2 nodes. However the EC2 servers do not discover each other. > > > > This gist includes the log files and the ES discovery Http results. I see both servers in the resulting DescribeInstances logs, but something must be keeping ES from associating them? > > [977123’s gists · GitHub](https://gist.github.com/977123) > > > > The gist also begins with a dump of all the ES properties I am using. > > > > Anyone see anything? > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\ **Post date:** [May 17, 2011, 8:58pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/4 "2011-05-17T20:58:56Z")
This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? \*-- jim \* On Tue, May 17, 2011 at 4:35 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > Good catch Paul, I also think that might be the issue. Note in the > network page you can set descriptive names like _en0:ipv4_ so you won't have > to set it explicitly for each node. > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > Looking at this line: > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > Looks like you're binding to ipv6 address, but the addresses you're getting > back from EC2 are ipv4: > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > So that you get no ping responses back for the ipv4 addresses: > > [Lorelei II] ping responses: {none} > > I think you may need to set your host correctly in the config. > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > I have two identically configured Elastic Search nodes embedded in a web > app which is deployed to two different EC2 nodes. However the EC2 servers do > not discover each other. > > This gist includes the log files and the ES discovery Http results. I see > both servers in the resulting DescribeInstances logs, but something must be > keeping ES from associating them? > [977123’s gists · GitHub](https://gist.github.com/977123) > > The gist also begins with a dump of all the ES properties I am using. > > Anyone see anything? > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 17, 2011, 9:00pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/5 "2011-05-17T21:00:14Z")
You want it to use the private ip address, so it depends which one the non loopback will be picked up. On Tuesday, May 17, 2011 at 11:58 PM, James Cook wrote: > This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? > > -- jim > > On Tue, May 17, 2011 at 4:35 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote: > > > Good catch Paul, I also think that might be the issue. Note in the network page you can set descriptive names like _en0:ipv4_ so you won't have to set it explicitly for each node. > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > > > > Looking at this line: > > > > > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > > > > > Looks like you're binding to ipv6 address, but the addresses you're getting back from EC2 are ipv4: > > > > > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > > So that you get no ping responses back for the ipv4 addresses: > > > > > > [Lorelei II] ping responses: {none} > > > I think you may need to set your host correctly in the config. > > > > > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > > > > > > I have two identically configured Elastic Search nodes embedded in a web app which is deployed to two different EC2 nodes. However the EC2 servers do not discover each other. > > > > > > > > This gist includes the log files and the ES discovery Http results. I see both servers in the resulting DescribeInstances logs, but something must be keeping ES from associating them? > > > > [977123’s gists · GitHub](https://gist.github.com/977123) > > > > > > > > The gist also begins with a dump of all the ES properties I am using. > > > > > > > > Anyone see anything? > > > > > > ## -- > > > > > > Paul Loy > > > [paul@keteracel.com](mailto:paul@keteracel.com) > > > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [May 17, 2011, 9:06pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/6 "2011-05-17T21:06:54Z")
Shay, could an enhancement to the cloud module also set your tcp host to the private ipv4 and your http host to the public dns using _[http://169.254.169.254/latest/meta-data/XXX](http://169.254.169.254/latest/meta-data/XXX)_ as this is what the cloud discovery is expecting. These could still, of course, be overidded in conf. If you like, that sounds like something I could possibly contrib (with a few pointers from you as to where it's best to hook it in). Cheers, Paul. On Tue, May 17, 2011 at 10:00 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > You want it to use the private ip address, so it depends which one the non > loopback will be picked up. > > On Tuesday, May 17, 2011 at 11:58 PM, James Cook wrote: > > This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? > > \*-- jim > \* > > On Tue, May 17, 2011 at 4:35 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > > Good catch Paul, I also think that might be the issue. Note in the > network page you can set descriptive names like _en0:ipv4_ so you won't have > to set it explicitly for each node. > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > Looking at this line: > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > Looks like you're binding to ipv6 address, but the addresses you're getting > back from EC2 are ipv4: > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > So that you get no ping responses back for the ipv4 addresses: > > [Lorelei II] ping responses: {none} > > I think you may need to set your host correctly in the config. > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > I have two identically configured Elastic Search nodes embedded in a web > app which is deployed to two different EC2 nodes. However the EC2 servers do > not discover each other. > > This gist includes the log files and the ES discovery Http results. I see > both servers in the resulting DescribeInstances logs, but something must be > keeping ES from associating them? > [977123’s gists · GitHub](https://gist.github.com/977123) > > The gist also begins with a dump of all the ES properties I am using. > > Anyone see anything? > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 17, 2011, 9:09pm UTC](https://discuss.elastic.co/t/ec2-discovery/4427/7 "2011-05-17T21:09:20Z")
Yea, sounds like a good enhancement!. Happy for the contrib. And now that you are going to contribute 🙂 : I am not sure defaulting HTTP to the public IP is a good default. And, in terms of implementation, it can get a bit tricky, but once you are up to it, we can discuss how best to implement it. On Wednesday, May 18, 2011 at 12:06 AM, Paul Loy wrote: > Shay, > > could an enhancement to the cloud module also set your tcp host to the private ipv4 and your http host to the public dns using > [http://169.254.169.254/latest/meta-data/XXX](http://169.254.169.254/latest/meta-data/XXX) > as this is what the cloud discovery is expecting. > > These could still, of course, be overidded in conf. > > If you like, that sounds like something I could possibly contrib (with a few pointers from you as to where it's best to hook it in). > > Cheers, > > Paul. > > On Tue, May 17, 2011 at 10:00 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote: > > > You want it to use the private ip address, so it depends which one the non loopback will be picked up. > > On Tuesday, May 17, 2011 at 11:58 PM, James Cook wrote: > > > > > This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? > > > > > > -- jim > > > > > > On Tue, May 17, 2011 at 4:35 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote: > > > > > > > Good catch Paul, I also think that might be the issue. Note in the network page you can set descriptive names like _en0:ipv4_ so you won't have to set it explicitly for each node. > > > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > > > > > > > > Looking at this line: > > > > > > > > > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > > > > > > > > > Looks like you're binding to ipv6 address, but the addresses you're getting back from EC2 are ipv4: > > > > > > > > > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > > > > So that you get no ping responses back for the ipv4 addresses: > > > > > > > > > > [Lorelei II] ping responses: {none} > > > > > I think you may need to set your host correctly in the config. > > > > > > > > > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > > > > > > > > > > I have two identically configured Elastic Search nodes embedded in a web app which is deployed to two different EC2 nodes. However the EC2 servers do not discover each other. > > > > > > > > > > > > This gist includes the log files and the ES discovery Http results. I see both servers in the resulting DescribeInstances logs, but something must be keeping ES from associating them? > > > > > > [977123’s gists · GitHub](https://gist.github.com/977123) > > > > > > > > > > > > The gist also begins with a dump of all the ES properties I am using. > > > > > > > > > > > > Anyone see anything? > > > > > > > > > > ## -- > > > > > > > > > > Paul Loy > > > > > [paul@keteracel.com](mailto:paul@keteracel.com) > > > > > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [May 18, 2011, 12:47am UTC](https://discuss.elastic.co/t/ec2-discovery/4427/8 "2011-05-18T00:47:16Z")
Cool, I'll start a ticket and we can discuss there. On Tue, May 17, 2011 at 2:09 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > Yea, sounds like a good enhancement!. Happy for the contrib. > > And now that you are going to contribute 🙂 : > > I am not sure defaulting HTTP to the public IP is a good default. And, in > terms of implementation, it can get a bit tricky, but once you are up to it, > we can discuss how best to implement it. > > On Wednesday, May 18, 2011 at 12:06 AM, Paul Loy wrote: > > Shay, > > could an enhancement to the cloud module also set your tcp host to the > private ipv4 and your http host to the public dns using > > _[http://169.254.169.254/latest/meta-data/XXX](http://169.254.169.254/latest/meta-data/XXX)_ > > as this is what the cloud discovery is expecting. > > These could still, of course, be overidded in conf. > > If you like, that sounds like something I could possibly contrib (with a > few pointers from you as to where it's best to hook it in). > > Cheers, > > Paul. > > On Tue, May 17, 2011 at 10:00 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) > > > wrote: > > You want it to use the private ip address, so it depends which one the non > loopback will be picked up. > > On Tuesday, May 17, 2011 at 11:58 PM, James Cook wrote: > > This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? > > \*-- jim > \* > > On Tue, May 17, 2011 at 4:35 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > > Good catch Paul, I also think that might be the issue. Note in the > network page you can set descriptive names like _en0:ipv4_ so you won't have > to set it explicitly for each node. > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > Looking at this line: > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > Looks like you're binding to ipv6 address, but the addresses you're getting > back from EC2 are ipv4: > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > So that you get no ping responses back for the ipv4 addresses: > > [Lorelei II] ping responses: {none} > > I think you may need to set your host correctly in the config. > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > I have two identically configured Elastic Search nodes embedded in a web > app which is deployed to two different EC2 nodes. However the EC2 servers do > not discover each other. > > This gist includes the log files and the ES discovery Http results. I see > both servers in the resulting DescribeInstances logs, but something must be > keeping ES from associating them? > [977123’s gists · GitHub](https://gist.github.com/977123) > > The gist also begins with a dump of all the ES properties I am using. > > Anyone see anything? > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\ **Post date:** [May 18, 2011, 12:53am UTC](https://discuss.elastic.co/t/ec2-discovery/4427/9 "2011-05-18T00:53:13Z")
[https://github.com/elasticsearch/elasticsearch/issues/940](https://github.com/elasticsearch/elasticsearch/issues/940) On Tue, May 17, 2011 at 5:47 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote: > Cool, I'll start a ticket and we can discuss there. > > On Tue, May 17, 2011 at 2:09 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > > > Yea, sounds like a good enhancement!. Happy for the contrib. > > > > And now that you are going to contribute 🙂 : > > > > I am not sure defaulting HTTP to the public IP is a good default. And, in > > terms of implementation, it can get a bit tricky, but once you are up to it, > > we can discuss how best to implement it. > > > > On Wednesday, May 18, 2011 at 12:06 AM, Paul Loy wrote: > > > > Shay, > > > > could an enhancement to the cloud module also set your tcp host to the > > private ipv4 and your http host to the public dns using > > > > _[http://169.254.169.254/latest/meta-data/XXX](http://169.254.169.254/latest/meta-data/XXX)_ > > > > as this is what the cloud discovery is expecting. > > > > These could still, of course, be overidded in conf. > > > > If you like, that sounds like something I could possibly contrib (with a > > few pointers from you as to where it's best to hook it in). > > > > Cheers, > > > > Paul. > > > > On Tue, May 17, 2011 at 10:00 PM, Shay Banon \< > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote: > > > > You want it to use the private ip address, so it depends which one the > > non loopback will be picked up. > > > > On Tuesday, May 17, 2011 at 11:58 PM, James Cook wrote: > > > > This is Amazon EC2, so would it be better to use _non\_loopback:ipv4_? > > > > \*-- jim > > \* > > > > On Tue, May 17, 2011 at 4:35 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) > > > > > wrote: > > > > Good catch Paul, I also think that might be the issue. Note in the > > network page you can set descriptive names like _en0:ipv4_ so you won't have > > to set it explicitly for each node. > > > > On Tuesday, May 17, 2011 at 10:44 PM, Paul Loy wrote: > > > > Looking at this line: > > > > [Lorelei II] Bound to address [/fe80:0:0:0:1031:38ff:fe0d:a457:9310] > > > > Looks like you're binding to ipv6 address, but the addresses you're > > getting back from EC2 are ipv4: > > > > [Lorelei II] using dynamic discovery nodes [[#cloud-i-5f37ca31-0][inet[/10.124.135.165:9310]], [#cloud-i-cfd02ea1-0][inet[/10.124.243.93:9310]]] > > > > So that you get no ping responses back for the ipv4 addresses: > > > > [Lorelei II] ping responses: {none} > > > > I think you may need to set your host correctly in the config. > > > > On Tue, May 17, 2011 at 8:04 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com)wrote: > > > > I have two identically configured Elastic Search nodes embedded in a web > > app which is deployed to two different EC2 nodes. However the EC2 servers do > > not discover each other. > > > > This gist includes the log files and the ES discovery Http results. I see > > both servers in the resulting DescribeInstances logs, but something must be > > keeping ES from associating them? > > [977123’s gists · GitHub](https://gist.github.com/977123) > > > > The gist also begins with a dump of all the ES properties I am using. > > > > Anyone see anything? > > > > ## -- > > > > Paul Loy > > [paul@keteracel.com](mailto:paul@keteracel.com) > > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) > > > > ## -- > > > > Paul Loy > > [paul@keteracel.com](mailto:paul@keteracel.com) > > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) > > ## -- > > Paul Loy > [paul@keteracel.com](mailto:paul@keteracel.com) > [Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy) ## -- Paul Loy [paul@keteracel.com](mailto:paul@keteracel.com) [http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy) ---
**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, 4:05am UTC](https://discuss.elastic.co/t/ec2-discovery/4427/10 "2017-07-06T04:05:53Z")