# ES-2.3.4 Cluster in AWS - Transport Client not able to connect **URL:** \ **Category:** Elasticsearch\ **Created:** [August 3, 2016, 4:28pm UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131 "2016-08-03T16:28:32Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Sree](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sree/32/740_2.png) [@Sree](https://discuss.elastic.co/u/Sree)\ **Post date:** [August 3, 2016, 4:28pm UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131/1 "2016-08-03T16:28:32Z")
I have a 3 node ES cluster setup in AWS. Cluster discovery and REST endpoints are working fine. But when i try with a TransportClient , its unable to connect to the cluster. i am getting No Node available exception. Please see the exception in below gist. > And my AWS configurations here. cloud.aws.access\_key: "XXXXXXXXXXXXXXXX" cloud.aws.secret\_key: "CCCCCCCCCCCCCCCC" plugin.mandatory: "cloud-aws" discovery.type: "ec2" discovery.ec2.groups: "escluster" discovery.ec2.host\_type: "private\_ip" discovery.ec2.ping\_timeout: "30s" discovery.ec2.availability\_zones: "us-east-1a" cloud.aws.region: "us-east" discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.enabled: true discovery.zen.ping.unicast.hosts: ["PRIVATE\_IP","PRIVATE\_IP","PRIVATE\_IP"] network.host: PRIVATE\_IP network.bind\_host: 0 It would be great , if any one can point me any issues with above configuration. I was using above config for my previous cluster ES 1.7 and Transport Client was also working fine then. Now I am migrating to ES 2.3.4. Please suggest and give me some pointers. Thanks ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 3, 2016, 5:16pm UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131/2 "2016-08-03T17:16:30Z")
My guess is that you changed the cluster name on some machines? ```auto [Hobgoblin] node {#transport#-1}{172.30.1.168}{172.30.1.168:9300} not part of the cluster Cluster [elasticsearch] ``` ---
**Author:** ![Sree](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sree/32/740_2.png) [@Sree](https://discuss.elastic.co/u/Sree)\ **Post date:** [August 4, 2016, 4:55am UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131/3 "2016-08-04T04:55:15Z")
Thank you @dadoonet . I confirmed that , all nodes are in same cluster. But from the line which you mentioned , there is a "elasticsearch" default cluster coming up. So that's a good hint. Let me check my Transport Client code and need to check whether [cluster.name](http://cluster.name) is not taking from property file or not. Thanks ---
**Author:** ![Sree](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sree/32/740_2.png) [@Sree](https://discuss.elastic.co/u/Sree)\ **Post date:** [August 4, 2016, 10:03am UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131/4 "2016-08-04T10:03:07Z")
@dadoonet My bad, [cluster.name](http://cluster.name) was not set properly in TransportClient. Its working fine now. Thank you for the pointer. ---
**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, 10:30pm UTC](https://discuss.elastic.co/t/es-2-3-4-cluster-in-aws-transport-client-not-able-to-connect/57131/5 "2017-07-05T22:30:08Z")