# EC2 Configuration **URL:** \ **Category:** Elasticsearch\ **Created:** [August 31, 2010, 5:05pm UTC](https://discuss.elastic.co/t/ec2-configuration/3285 "2010-08-31T17:05:03Z")\ **Posts on this page:** 5\ **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:** [August 31, 2010, 5:05pm UTC](https://discuss.elastic.co/t/ec2-configuration/3285/1 "2010-08-31T17:05:03Z")
I have been using Hazelcast in a dev environment (local laptop) for a couple months while we develop our application. It is now the point where I want to bring HC to a QA environment which will be on EC2. Are there any best practices for configuration on EC2. I've come across this post which has an EC2 config. It relies on a custom token being defined when the config is created. I would like to avoid this. [http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1](http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1) Thanks. ---
**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:** [August 31, 2010, 6:26pm UTC](https://discuss.elastic.co/t/ec2-configuration/3285/2 "2010-08-31T18:26:36Z")
Not sure about Hazelcrast, but discovery in elasticsearch is very simple using the cloud plugin. Regarding what type of machines, it really depends on the load you are after, but I would probably say the large instances are a minimum just because of the poor IO on small instances (from what I heard). -shay.banon On Tue, Aug 31, 2010 at 8:05 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > I have been using Hazelcast in a dev environment (local laptop) for a > couple months while we develop our application. It is now the point where I > want to bring HC to a QA environment which will be on EC2. Are there any > best practices for configuration on EC2. > > I've come across this post which has an EC2 config. It relies on a custom > token being defined when the config is created. I would like to avoid this. > [http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1](http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1) > > Thanks. ---
**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:** [August 31, 2010, 6:42pm UTC](https://discuss.elastic.co/t/ec2-configuration/3285/3 "2010-08-31T18:42:36Z")
Hi Shay, Sorry, I posted to the wrong group. :\*) Although I would also like to get info regarding best practices for ES as well. My proposed EC2 config is here: ``` node.data = true network.host = 127.0.0.1 transport.tcp.port = 9310 http.enabled = false cloud.aws.access_key = XXX cloud.aws.secret_key = XXX discovery.type = ec2 gateway.type = s3 s3.bucket = nep_qa/es_gateway index.store.memory.direct=true ``` I know each of these will depend on the particular application. I am looking to have a set of scalable instances that will shrink/grow between 2 and 10 instances. That upper limit is just a guess at this point until we can perform real load testing. The only question that leaps to my mind is whether there is any benefit to using a file-based index on servers which take their hard drive with them when they are shutdown gracefully or disappear unexpectedly. On Tue, Aug 31, 2010 at 2:26 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > Not sure about Hazelcrast, but discovery in elasticsearch is very simple > using the cloud plugin. Regarding what type of machines, it really depends > on the load you are after, but I would probably say the large instances are > a minimum just because of the poor IO on small instances (from what I > heard). > > -shay.banon > > On Tue, Aug 31, 2010 at 8:05 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > > > I have been using Hazelcast in a dev environment (local laptop) for a > > couple months while we develop our application. It is now the point where I > > want to bring HC to a QA environment which will be on EC2. Are there any > > best practices for configuration on EC2. > > > > I've come across this post which has an EC2 config. It relies on a custom > > token being defined when the config is created. I would like to avoid this. > > [http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1](http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1) > > > > Thanks. ---
**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:** [August 31, 2010, 8:33pm UTC](https://discuss.elastic.co/t/ec2-configuration/3285/4 "2010-08-31T20:33:50Z")
Of course the network.host setting will not work, since its will only use localhost. You should simply not set it when running on ec2. file based indices make sense, especially when running on ec2 with s3 gateway, since they can then be reused when performing full recovery (done automatically by elasticsearch). -shay.banon On Tue, Aug 31, 2010 at 9:42 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com) wrote: > Hi Shay, > > Sorry, I posted to the wrong group. :\*) > > Although I would also like to get info regarding best practices for ES as > well. > > My proposed EC2 config is here: > > ``` > node.data = true > network.host = 127.0.0.1 > transport.tcp.port = 9310 > http.enabled = false > > cloud.aws.access_key = XXX > cloud.aws.secret_key = XXX > discovery.type = ec2 > > gateway.type = s3 > s3.bucket = nep_qa/es_gateway > > index.store.memory.direct=true > > ``` > > I know each of these will depend on the particular application. I am > looking to have a set of scalable instances that will shrink/grow between 2 > and 10 instances. That upper limit is just a guess at this point until we > can perform real load testing. > > The only question that leaps to my mind is whether there is any benefit to > using a file-based index on servers which take their hard drive with them > when they are shutdown gracefully or disappear unexpectedly. > > On Tue, Aug 31, 2010 at 2:26 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > > > Not sure about Hazelcrast, but discovery in elasticsearch is very simple > > using the cloud plugin. Regarding what type of machines, it really depends > > on the load you are after, but I would probably say the large instances are > > a minimum just because of the poor IO on small instances (from what I > > heard). > > > > -shay.banon > > > > On Tue, Aug 31, 2010 at 8:05 PM, James Cook [jcook@tracermedia.com](mailto:jcook@tracermedia.com)wrote: > > > > > I have been using Hazelcast in a dev environment (local laptop) for a > > > couple months while we develop our application. It is now the point where I > > > want to bring HC to a QA environment which will be on EC2. Are there any > > > best practices for configuration on EC2. > > > > > > I've come across this post which has an EC2 config. It relies on a custom > > > token being defined when the config is created. I would like to avoid this. > > > [http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1](http://groups.google.com/group/hazelcast/msg/69204fd1025d95e7?pli=1) > > > > > > Thanks. ---
**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:19am UTC](https://discuss.elastic.co/t/ec2-configuration/3285/5 "2017-07-06T04:19:58Z")