# Compatibility Issues with Elasticsearch 2.3.5 and Cloud AWS plugin

**URL:** <https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812>\
**Category:** Elasticsearch\
**Created:** [August 24, 2016, 11:39am UTC](https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812 "2016-08-24T11:39:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohanAgonda](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@JohanAgonda](https://discuss.elastic.co/u/JohanAgonda)\
**Post date:** [August 24, 2016, 11:39am UTC](https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812/1 "2016-08-24T11:39:27Z")

</div>

Trying to install ELK stack on AWS EC2 instance. Latest Elasticsearch (2.3.5) and Cloud-AWS plugin seem to have some problems. I got errors while running **sudo bin/plugin install cloud-aws** and **service elasticsearch start**. The error for the second command is below

Exception in thread "main" java.lang.IllegalArg umentException: No automatic endpoint could be derived from region [ap-south-1]  
at org.elasticsearch.cloud.aws.AwsEc2ServiceImpl.client(AwsEc2ServiceImp l.java:198)  
at org.elasticsearch.discovery.ec2.AwsEc2UnicastHostsProvider.(Aws Ec2UnicastHostsProvider.java:75)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct orAccessorImpl.java:57)  
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:45)  
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)  
at \<\<\>\>  
at org.elasticsearch.node.Node.(Node.java:213)  
at org.elasticsearch.node.Node.(Node.java:140)  
at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:143)  
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178)  
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:270)  
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)

Also chrome browser does not display :9200

Any help is much appreciated.

Johan A

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [August 24, 2016, 12:18pm UTC](https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812/2 "2016-08-24T12:18:13Z")

</div>

Hi @JohanAgonda,

The Cloud-AWS plugin could not derive the endpoint automatically, so you need to specify it explicitly in `elasticsearch.yml` (see also [docs](https://www.elastic.co/guide/en/elasticsearch/plugins/current/cloud-aws-discovery.html#cloud-aws-discovery-endpoint)):

```auto
cloud.aws.ec2.endpoint: ec2.ap-south-1.amazonaws.com

```

Elasticsearch 5 will provide [support for automatically deriving the endpoint for this region](https://github.com/elastic/elasticsearch/pull/19112).

Daniel

---

<div class="post-metadata">

**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 24, 2016, 12:41pm UTC](https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812/3 "2016-08-24T12:41:08Z")

</div>

Yeah. That's bad I didn't backport it in 2.4 branch BTW.

---

<div class="post-metadata">

**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:25pm UTC](https://discuss.elastic.co/t/compatibility-issues-with-elasticsearch-2-3-5-and-cloud-aws-plugin/58812/4 "2017-07-05T22:25:33Z")

</div>