I'm trying to reindex from a remote from Self Manged instance to an Elastic cloud instance.
But I'm getting a timeout error:
{"error":{"root_cause":[{"type":"connect_exception","reason":"Timeout connecting to [XXXX.elb.eu-north-1.amazonaws.com/XX.XX.XX.XXX:9200]","status":500}]
I have confirmed that connectivity to cluster to using the elb dns name can recieve a connection on the specified port but using curl, and this is succeding without any problem.
I have even disabled all authentication in case that the problem was originated by it. The connection setup is using http but regardless of this I also have disabled the ssl verification and whitelisted all incoming domains in an attempt to exclude some issues on that front applying.
reindex.remote.whitelist: ["*:*"]
reindex.ssl.verification_mode: none
The error suggest that there is a connectivity problem from the Elastic cloud towards our instance. But I cannot see any connection error on the logs that give me any more details, and since I can stablish a connection succesfully from internet I'm a bit stuck.
I have tried using different IP and locations to rule out we have some firewall that is blocking Internet access but this doesn't seem to be the case (as I expected).
Any suggestion on how to perform further connectivity tests originating from the Elastic Cloud would be highly appreciated, or perhaps a way to pull some detailed logs on the error apart of a 500.
Extra information:
- Origin request:
curl --location 'https://XXXXX.eu-north-1.aws.elastic-cloud.com:9243/_reindex' \ ─╯
--header 'Content-Type: application/json' \
--header 'Authorization: ApiKey XXXXXXX' \
--data '{
"max_docs": 1,
"source": {
"remote": {
"host": "http://XXXXXXX.elb.eu-north-1.amazonaws.com:9200"
},
"index": "test.staging"
},
"dest": {
"index": "reindex.tes.dev"
}
}'
- Curl request to validate connection to Self hosted:
curl -v -XGET http://XXXXX.elb.eu-north-1.amazonaws.com:9200
curl -v -XGET http://XXXXX.elb.eu-north-1.amazonaws.com:9200/_cluster/state
Both succesful
More data:
We have also validated that our self manage instance can connect directly by performing the same GET request to the ES Cloud, and the connectivity is indeed successful.