Setting up GCE Discoveryedit


Before starting, you need:

If you did not set it yet, you can define your default project you will work on:

gcloud config set project es-cloud

Login to Google Cloudedit

If you haven’t already, login to Google Cloud

gcloud auth login

This will open your browser. You will be asked to sign-in to a Google account and authorize access to the Google Cloud SDK.

Creating your first instanceedit

gcloud compute instances create myesnode1 \
       --zone <your-zone> \
       --scopes compute-rw

When done, a report like this one should appears:

Created [].
myesnode1 us-central1-f n1-standard-1    RUNNING

You can now connect to your instance:

# Connect using google cloud SDK
gcloud compute ssh myesnode1 --zone europe-west1-a

# Or using SSH with external IP address
ssh -i ~/.ssh/google_compute_engine

Service Account Permissions

It’s important when creating an instance that the correct permissions are set. At a minimum, you must ensure you have:


Failing to set this will result in unauthorized messages when starting Elasticsearch. See Machine Permissions.

Once connected, install Elasticsearch:

Install Elasticsearch discovery gce pluginedit

Install the plugin:

# Use Plugin Manager to install it
sudo bin/elasticsearch-plugin install discovery-gce

Open the elasticsearch.yml file:

sudo vi /etc/elasticsearch/elasticsearch.yml

And add the following lines:

      project_id: es-cloud
      zone: europe-west1-a
      seed_providers: gce

Start Elasticsearch:

sudo /etc/init.d/elasticsearch start

If anything goes wrong, you should check logs:

tail -f /var/log/elasticsearch/elasticsearch.log

If needed, you can change log level to trace by opening

sudo vi /etc/elasticsearch/

and adding the following line:

# discovery = discovery.gce
logger.discovery_gce.level = trace