How to enable elasticsearch access from remote machines


Elasticsearch is one of the most popular open source search platforms available today.

In this post, we will look at how to enable remote access to elastic. Now, what do I mean by remote access? By remote access, I mean ability to access the elastic api endpoints from machines other than where it is setup.

The default elasticsearch installation is localhost only, you can access it only from the machine where it is setup. While this is okay for POC type development work, for most other use cases we need elasticsearch to be installed on a server somewhere and be able to access it from other machines.

Before we get started with the steps needed to configure elasticsearch installation for remote access, do note that these are applicable only for elastic 7.1.x (maybe even 7.x).

Steps:
  1. Navigate to the folder where elasticsearch is installed. It should look something like this screenshot
  2. Open up the config folder. There should be a elasticsearch.yml file. Open it.
  3. In the Network section, find the entry called network.host. It may be commented out, uncomment it and update it to the hostname of your choice.
  4. If the elastic instance is to be enabled for access from other machines within the corp network, then this host name will be the name of your machine or ip address which is accessible from other devices in the network.
  5. Next find the entry in the same file called node.name. Uncomment if it is commented out. The default value here will be node-1, change it to whatever you want to call your elastic node.
  6. Next find the entry called cluster.initial_master_nodes. Again uncomment it and change the value to the name of the node you setup in previous step.
  7. Now, start elasticsearch
  8. Access it using http://myhostnamehere:9200
Note: When you start elasticsearch, if you are using windows firewall, you may see an alert and get an option to allow or deny network access. You will need to allow this for elasticsearch to work in this configuration.

This should be it! Elasticsearch should now be accessible from other devices within the network.

Do note that by default elastic instance is not secured and exposing it even within the network without some type of authentication is not a good idea. We will look at how to do that in one of the upcoming posts.

References:
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#_ipv4_vs_ipv6
https://stackoverflow.com/a/56238134/158589
https://discuss.elastic.co/t/problems-with-access-to-elasticsearch-form-outside-machine/172450


Comments

  1. Anonymous4 December 2022 at 08:12

    Cities and states can use legalized playing to assist specific public companies, corresponding to education. The majority of games are slots but have the ability to|you presumably can} select between loads of desk sport 우리카지노 variants as nicely. For instance, lots of|there are many} totally different blackjack tables and about a dozen roulette wheels.

    ReplyDelete

Post a Comment

Popular posts from this blog

Your project does not reference error!

The error " Your project does not reference ".NETFramework,Version=v4.6.1" framework. Add a reference to ".NETFramework,Version=v4.6.1" in the "TargetFrameworks" property of your project file and then re-run NuGet restore " troubled me a bit at work today. The target framework was set correctly and I had 4.6.1 on my dev machine. IDE was VS 2019. So what was the problem?  Good old fashioned googling helped me to resolve the issue and so adding this note here as a reference for myself. It turns out the solution was to delete the obj folders and just recompile. Just doing a clean and rebuild did not help. I had to delete the obj folder manually and then recompile worked. The link that helped me with this is in the reference below.  It seems like lot of people have come across this same problem. Latest comment on that thread is from Jan 2020 and looks like the issue is still unresolved from VS team. This is at least one of the workarounds t...
Read more

Add co-administrators for your azure subscription

Image
I use my Visual Studio Enterprise subscription at work which gives me a free monthly credit of close to 10,00 INR (around 150 USD). I use it quite extensively to learn about azure services, create proof of concepts and generally play around with azure services. There was a situation recently where I had to let another user manage azure services which I had created and also allow him to use more of azure services, all using my subscription. I was wondering if there was a way to do this and if this would even be allowed, considering that I was only using the free credit obtained from VS enterprise and not really paying anything extra to use Azure. The good news is that there is! Good folks at Microsoft have provided a way to add on additional administrative users for a single subscription. Now that I think about it, for large enterprises, this would be a major requirement. No way that everything that a decent sized company has on azure would be managed by just one admin account. B...
Read more