# AWS Elastiseach
**URL:** https://discuss.elastic.co/t/aws-elastiseach/80182
**Category:** Elasticsearch
**Created:** [March 27, 2017, 6:14pm UTC](https://discuss.elastic.co/t/aws-elastiseach/80182 "2017-03-27T18:14:45Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Mukrram](https://discuss.elastic.co/u/Mukrram)
#### Post date: [March 27, 2017, 6:14pm UTC](https://discuss.elastic.co/t/aws-elastiseach/80182/1 "2017-03-27T18:14:45Z")
I am having a problem with AWS Elasticsearch 5.1.1.
Firstly, I setup manual cluster with 2 nodes with Elasticsearch 5.1.1 on local machines and I used Elasticseach client 5.1.1 and Spark connector and everything was working fine. But when I switched to AWS Elasticsearch 5.1.1 and tried the same thing, it starts giving me errors like Cluster not accessible. e.t.c I found that it's because AWS Elasticsearch does not support transport port. So, I am limited to use only HTTP port 80. When I try rest API it works fine but it's slow because I am ingesting massive data.
Secondly, I tried to ingest directly from Spark using DataFrames it again gave me the error.
Cannot detect ES version - typically this happens if the network/Elasticsearch cluster is not accessible or when targeting a WAN/Cloud instance without the proper setting 'es.nodes.wan.only'
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 27, 2017, 7:21pm UTC](https://discuss.elastic.co/t/aws-elastiseach/80182/2 "2017-03-27T19:21:21Z")
FYI elastic #cloud supports transport protocol in case it helps.
Moving in #elasticsearch-and-hadoop forum might be better may be to get help about this?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 24, 2017, 7:21pm UTC](https://discuss.elastic.co/t/aws-elastiseach/80182/3 "2017-04-24T19:21:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.