el-client | Arduino client for esp-link 's REST , MQTT , and command | Websocket library

The code running on your local computer is trying to connect directly to the Elasticsearch server without going through the SSH tunnel. The SSH command is opening a tunnel from your local port 9200 to the remote server. The local software trying to connect to Elasticsearch should be connecting to localhost:9200 not vpc-es-domain-20210331-abc123def.us-west-2.es.amazonaws.com/10.0.47.182:443.

The endpoint vpc-es-domain-20210331-abc123def.us-west-2.es.amazonaws.com/10.0.47.182:443 doesn't look valid anyway. It has a hostname and an IP address in there.

You mentioned in the comments:

"I actually launched my bastion host using the same SG as my ES"

However just placing two resources in the same security group does nothing unless that security group also has a rule specifically allowing traffic between the resources within it. Security groups do not have this rule by default, except for the default security group in the default VPC that is created automatically when you first create your AWS account.

So please make sure that the security group has a rule that will allow the bastion host to connect to the Elasticsearch server over port 443.

It's not working because you are using the wrong API Key. 😅

But don't worry: these things happen a lot. It certainly happened to me.

The API Key that you are creating is for you to issue REST requests against Elasticsearch Service — which is the entity that governs your Elasticsearch and Kibana clusters.

To make it work, you need to create an API Key from Elasticsearch specifically. To create one, go to the Dev Tools Console and issue the following request:

You can try to set up a scan for your repository in your SpringBoot Main application like:

Create a computed to return an array of just the 3 slides you want to show:

In the end I didn't find a problem in my configuration/implementation. It seems like a bug in the implementation of Elasticsearch's RestHighLevelClient.

I implemented a retry mechanism that wraps the RestHighLevelClient and retries the query if I get the same error. I used Spring @Retry annotation for this solution.

What you are looking for is not possible, ideally, you should have coherce enabled on your numeric fields so that your index doesn't contain dirty data.

The best solution is that in your application which generated the Elasticsearch query(you should have a check for NumberFormatExcepton if you are searching for numeric fields as your index doesn't contain the dirty data in the first place and reject the query if you get an exception in your application).

Edit: Another interesting approach is to validate the data before inserting into ES, using the Validate API as suggested by @prakash, only thing is that it would add another network call but if your application is not latency-sensitive, it can be used as a workaround.

I don't have a gradle setup to test this, but with maven you need two things:

set the property for the Elasticsearch version and the dependency for Spring Data Elasticsearch:

The problem is that you're running ES server v1.2.2 (extremely old version) with a 6.4.0 client.

So the 6.4.0 client has the geoBoundingBoxQuery() method, however the 1.2.2 client provides the geoBoundingBoxFilter() method, both are incompatible. There has been a big query/filter refactor in ES 2.x.

As a rule of thumb you should always run the same version of ES and the client library. In your case, you have a delta of several versions betweem your server and your client.

You should definitely consider upgrading your ES cluster to at least 6.4.0 or downgrade your client to 1.x.

You are not correctly initializing your elasticsearch client, can you try with below code:

Please note that I am using the version which accepts the host, port and http scheme and it works fine for me and is the standard for creating the client.