Skip to main content
  • EN

Thanks for your help and suggestions in advance. I am using Elasticsearch service on AWS the default port for it is 443 not 9200.

 

Unfortunately FME seems to keep wanting to put 9200 at the end and then reporting it cannot reach the service:

 

ELASTICSEARCH writer: Opening index 'https://search-web-elasticsearch-4vxxxxpx2.eu-central-1.es.amazonaws.com/webmapnotes'

ELASTICSEARCH writer: Failed to connect to search-web-elasticsearch-4v3o3xxxpx2znima.eu-central-1.es.amazonaws.com port 9200: Timed out

ELASTICSEARCH writer: Unable to locate or open server 'https://search-web-elasticsearch-4v3xxxznima.eu-central-1.es.amazonaws.com'. Please ensure the server exists and is accessible. 

 

In the writer I put the port https://search-web-elasticsearch-4vxxxxznima.eu-central-1.es.amazonaws.com:443

 

That doesn't seem to work. Any idea how I can change the port away from the default.

 

Many Thanks

 

Oliver

Are you sure it's not (partially) a question of ES versions? As far as I know, FME doesn't support ES 7+, which is what I suspect AWS is provisioning by default. That might be something to verify.

See also https://community.safe.com/s/idea/0874Q000000Tki3QAC/detail

In case you need to use ES 7+, it's not too complicated to do manually using some JSONTemplaters and HTTPCallers.

Are you sure it's not (partially) a question of ES versions? As far as I know, FME doesn't support ES 7+, which is what I suspect AWS is provisioning by default. That might be something to verify.

See also https://community.safe.com/s/idea/0874Q000000Tki3QAC/detail

In case you need to use ES 7+, it's not too complicated to do manually using some JSONTemplaters and HTTPCallers.

Thanks, I am using ES 6 to avoid those issues. Previously it was on 80 but now it is on 443 and it looks like the writer doesn't like it. I may have to go down the HTTPCaller route. Thank you

Reply


Community Stats

30,017
Posts
113,997
Replies
37,636
Members
Terms & ConditionsCookie settings