OpenSearch (ElasticSearch) on devweb #

For access to OpenSearch on devweb, please see the guidance on Requesting Access.

We run a departmental OpenSearch instance, with accounts created upon request. The service is intended to facilitate the completion of class labs and is not meant for storing large (or frequently queried) indexes.

The service runs on devweb2023 but should be accessed as elasticsearch2023 so that the hostname used by your client matches the server names in the certificate.

Using OpenSearch #

Users can read and write indexes prefixed with their username and a dash, e.g. if your username is aab12345 then you can read/write to aab12345, aab12345-test, aab12345-myindex123 but not another user's indexes like xxy98765 or another user's indexes like xxy98765-someonesindex.

You may find the following example queries useful (replacing $username with your username and $password with your OpenSearch password):

Creating your own index: #

curl --user $username:$password -XPUT$username-testindex; echo

Reading your own index: #

curl --user $username:$password -XGET$username-testindex; echo

Accessing OpenSearch from home / off-campus #

In order to access OpenSearch off-campus, you need to either:

  1. Connect to the VPN, or
  2. Tunnel your connection via cafe (ssh) as follows (replacing $username with your DS username)
ssh -L $

You'll then by able to connect your local client or app to localhost:9200 (if using the SSH tunnel), which will be tunnelled to devweb20232023 via cafe, however you may receive certificate warnings as the name localhost doesn't appear on OpenSearch's TLS certificate.

See Remote compute for more details.