# ES in AWS **URL:** \ **Category:** Elasticsearch\ **Created:** [August 9, 2015, 10:50am UTC](https://discuss.elastic.co/t/es-in-aws/27086 "2015-08-09T10:50:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Kiran\_Sriharsha](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@Kiran\_Sriharsha](https://discuss.elastic.co/u/Kiran_Sriharsha)\ **Post date:** [August 9, 2015, 10:50am UTC](https://discuss.elastic.co/t/es-in-aws/27086/1 "2015-08-09T10:50:13Z")
Hi All We have Elasticsearch ES cluster in amazon aws with "Load balancer". These ES nodes are accessed using java code deployed in tomcat using ES Java API. The system is failing randomly. Transport client was initiated with aws load balancer url, and later after these random disconnections between client and nodes, we have replaced with actual IP of the nodes. After this one change the system is looking stable till now. Also, if anyone could suggest ideal tcp keep alive time, that would be awesome. ES: 1.7 version Client OS: Cent OS, EC2 Instances Client JDK: 1.8.0\_25 Client ES: 1.7 Did anyone face this issue with LB as input for transport client param?? Thanks Sri Harsha ---
**Author:** ![joshfurr](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@joshfurr](https://discuss.elastic.co/u/joshfurr)\ **Post date:** [September 16, 2015, 8:43pm UTC](https://discuss.elastic.co/t/es-in-aws/27086/2 "2015-09-16T20:43:02Z")
I am having the same issue. It seems to be when the load balancer has not been contacted in a while via a search or indexing. If I find anything I will forward it on. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:49pm UTC](https://discuss.elastic.co/t/es-in-aws/27086/3 "2017-07-05T23:49:53Z")