You're viewing version 2.3 of the OpenSearch documentation. This version is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.

Tarball

Installing OpenSearch from a tarball, also known as a tar archive, may appeal to users who want granular control over installation details like file permissions and installation paths.

Generally speaking, the installation of OpenSearch from a tarball can be broken down into a few steps:

Download and unpack OpenSearch.
Configure important system settings.
- These settings are applied to the host before modifying any OpenSearch files.
(Optional) Test OpenSearch.
- Confirm that OpenSearch is able to run before you apply any custom configuration.
- This can be done without any security (no password, no certificates) or with a demo security configuration that can be applied by a packaged script.
Configure OpenSearch for your environment.
- Apply basic settings to OpenSearch and start using it in your environment.

The tarball is a self-contained directory with everything needed to run OpenSearch, including an integrated Java Development Kit (JDK). This installation method is compatible with most Linux distributions, including CentOS 7, Amazon Linux 2, and Ubuntu 18.04. If you have your own Java installation and set the environment variable JAVA_HOME in the terminal, macOS works as well.

This guide assumes that you are comfortable working from the Linux command line interface (CLI). You should understand how to input commands, navigate between directories, and edit text files. Some example commands reference the vi text editor, but you may use any text editor available.

Step 1: Download and unpack OpenSearch

Download the appropriate tar.gz archive from the OpenSearch downloads page or by using the command line (such as with wget).

# x64
wget https://artifacts.opensearch.org/releases/bundle/opensearch/2.3.0/opensearch-2.3.0-linux-x64.tar.gz

# ARM64
wget https://artifacts.opensearch.org/releases/bundle/opensearch/2.3.0/opensearch-2.3.0-linux-arm64.tar.gz

Extract the contents of the tarball.

# x64
tar -xvf opensearch-2.3.0-linux-x64.tar.gz
   
# ARM64
tar -xvf opensearch-2.3.0-linux-arm64.tar.gz

Step 2: Configure important system settings

Before launching OpenSearch you should review some important system settings.

Disable memory paging and swapping performance on the host to improve performance.
```
sudo swapoff -a
```

Increase the number of memory maps available to OpenSearch.

# Edit the sysctl config file
sudo vi /etc/sysctl.conf

# Add a line to define the desired value
# or change the value if the key exists,
# and then save your changes.
vm.max_map_count=262144

# Reload the kernel parameters using sysctl
sudo sysctl -p

# Verify that the change was applied by checking the value
cat /proc/sys/vm/max_map_count

Step 3: (Optional) Test OpenSearch

Before proceeding you should test your installation of OpenSearch. Otherwise, it can be difficult to determine whether future problems are due to installation issues or custom settings you applied after installation. There are two quick methods for testing OpenSearch at this stage:

(Security enabled) Apply a generic configuration using the demo security script included in the tar archive.
(Security disabled) Manually disable the security plugin and test the instance before applying your own custom security settings.

The demo security script will apply a generic configuration to your instance of OpenSearch. This configuration defines some environment variables and also applies self-signed TLS certificates. If you would like to configure these yourself, see Step 4: Set up OpenSearch in your environment.

If you only want to verify that the service is properly configured and you intend to configure security settings yourself, then you may want to disable the security plugin and launch the service without encryption or authentication.

An OpenSearch node configured by the demo security script is not suitable for a production environment. If you plan to use the node in a production environment after running opensearch-tar-install.sh, you should, at a minimum, replace the demo TLS certificates with your own TLS certificates and update the list of internal users and passwords. See Security configuration for additional guidance to ensure that your nodes are configured according to your security requirements.

Option 1: Test your Opensearch settings with security enabled

Change to the top directory of your OpenSearch installation.
```
cd /path/to/opensearch-2.3.0
```
Run the demo security script.
```
./opensearch-tar-install.sh
```

Open another terminal session and send requests to the server to verify that OpenSearch is running. Note the use of the --insecure flag, which is required because the TLS certificates are self-signed.

Send a request to port 9200:

 curl -X GET https://localhost:9200 -u 'admin:admin' --insecure

You should get a response that looks like this:

 {
    "name" : "hostname",
    "cluster_name" : "opensearch",
    "cluster_uuid" : "6XNc9m2gTUSIoKDqJit0PA",
    "version" : {
       "distribution" : "opensearch",
       "number" : <version>,
       "build_type" : <build-type>,
       "build_hash" : <build-hash>,
       "build_date" : <build-date>,
       "build_snapshot" : false,
       "lucene_version" : <lucene-version>,
       "minimum_wire_compatibility_version" : "7.10.0",
       "minimum_index_compatibility_version" : "7.0.0"
    },
    "tagline" : "The OpenSearch Project: https://opensearch.org/"
 }

Query the plugins endpoint:

 curl -X GET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure

The response should look like this:

 name     component                            version
 hostname opensearch-alerting                  2.3.0
 hostname opensearch-anomaly-detection         2.3.0
 hostname opensearch-asynchronous-search       2.3.0
 hostname opensearch-cross-cluster-replication 2.3.0
 hostname opensearch-index-management          2.3.0
 hostname opensearch-job-scheduler             2.3.0
 hostname opensearch-knn                       2.3.0
 hostname opensearch-ml                        2.3.0
 hostname opensearch-notifications             2.3.0
 hostname opensearch-notifications-core        2.3.0
 hostname opensearch-observability             2.3.0
 hostname opensearch-performance-analyzer      2.3.0
 hostname opensearch-reports-scheduler         2.3.0
 hostname opensearch-security                  2.3.0
 hostname opensearch-sql                       2.3.0

Return to the original terminal session and stop the process by pressing CTRL + C.

Option 2: Test your OpenSearch settings with security disabled

Open the configuration file.

vi /path/to/opensearch-2.3.0/config/opensearch.yml

Add the following line to disable the Security plugin:
```
plugins.security.disabled: true
```
Save the change and close the file.

Open another terminal session and send requests to the server to verify that OpenSearch is running. Because the security plugin has been disabled, you will be sending commands using HTTP rather than HTTPS.

Send a request to port 9200.

 curl -X GET http://localhost:9200

You should get a response that looks like this:

 {
    "name" : "hostname",
    "cluster_name" : "opensearch",
    "cluster_uuid" : "6XNc9m2gTUSIoKDqJit0PA",
    "version" : {
       "distribution" : "opensearch",
       "number" : <version>,
       "build_type" : <build-type>,
       "build_hash" : <build-hash>,
       "build_date" : <build-date>,
       "build_snapshot" : false,
       "lucene_version" : <lucene-version>,
       "minimum_wire_compatibility_version" : "7.10.0",
       "minimum_index_compatibility_version" : "7.0.0"
    },
    "tagline" : "The OpenSearch Project: https://opensearch.org/"
 }

Query the plugins endpoint.

 curl -X GET http://localhost:9200/_cat/plugins?v

The response should look like this:

 name     component                            version
 hostname opensearch-alerting                  2.3.0
 hostname opensearch-anomaly-detection         2.3.0
 hostname opensearch-asynchronous-search       2.3.0
 hostname opensearch-cross-cluster-replication 2.3.0
 hostname opensearch-index-management          2.3.0
 hostname opensearch-job-scheduler             2.3.0
 hostname opensearch-knn                       2.3.0
 hostname opensearch-ml                        2.3.0
 hostname opensearch-notifications             2.3.0
 hostname opensearch-notifications-core        2.3.0
 hostname opensearch-observability             2.3.0
 hostname opensearch-performance-analyzer      2.3.0
 hostname opensearch-reports-scheduler         2.3.0
 hostname opensearch-security                  2.3.0
 hostname opensearch-sql                       2.3.0

Step 4: Set up OpenSearch in your environment

Users who do not have prior experience with OpenSearch may want a list of recommended settings in order to get started with the service. By default, OpenSearch is not bound to a network interface and cannot be reached by external hosts. Additionally, security settings are either undefined (greenfield install) or populated by default usernames and passwords if you ran the security demo script by invoking opensearch-tar-install.sh. The following recommendations will enable a user to bind OpenSearch to a network interface, create and sign TLS certificates, and configure basic authentication.

The following recommended settings will allow you to:

Bind OpenSearch to an IP or network interface on the host.
Set initial and maximum JVM heap sizes.
Define an environment variable that points to the bundled JDK.
Configure your own TLS certificates - no third-party certificate authority (CA) is required.
Create an admin user with a custom password.

If you ran the security demo script, then you will need to manually reconfigure settings that were modified. Refer to Security configuration for guidance before proceeding.

Before modifying any configuration files, it’s always a good idea to save a backup copy before making changes. The backup file can be used to revert any issues caused by a bad configuration.

Open opensearch.yml.

vi /path/to/opensearch-2.3.0/config/opensearch.yml

Add the following lines.

# Bind OpenSearch to the correct network interface. Use 0.0.0.0
# to include all available interfaces or specify an IP address
# assigned to a specific interface.
network.host: 0.0.0.0

# Unless you have already configured a cluster, you should set
# discovery.type to single-node, or the bootstrap checks will
# fail when you try to start the service.
discovery.type: single-node

# If you previously disabled the security plugin in opensearch.yml,
# be sure to re-enable it. Otherwise you can skip this setting.
plugins.security.disabled: false

Save your changes and close the file.
Specify initial and maximum JVM heap sizes.
1. Open jvm.options.
```
  vi /path/to/opensearch-2.3.0/config/jvm.options
```
2. Modify the values for initial and maximum heap sizes. As a starting point, you should set these values to half of the available system memory. For dedicated hosts this value can be increased based on your workflow requirements.
  - As an example, if the host machine has 8 GB of memory then you might want to set the initial and maximum heap sizes to 4 GB:
    -Xms4g -Xmx4g
3. Save your changes and close the file.

Specify the location of the included JDK.

export OPENSEARCH_JAVA_HOME=/path/to/opensearch-2.3.0/jdk

Configure TLS

TLS certificates provide additional security for your cluster by allowing clients to confirm the identity of hosts and encrypt traffic between the client and host. For more information, refer to Configure TLS Certificates and Generate Certificates, which are included in the Security Plugin documentation. For work performed in a development environment, self-signed certificates are usually adequate. This section will guide you through the basic steps required to generate your own TLS certificates and apply them to your OpenSearch host.

Navigate to the OpenSearch config directory. This is where the certificates will be stored.
```
cd /path/to/opensearch-2.3.0/config/
```

Generate a root certificate. This is what you will use to sign your other certificates.

# Create a private key for the root certificate
openssl genrsa -out root-ca-key.pem 2048
   
# Use the private key to create a self-signed root certificate. Be sure to
# replace the arguments passed to -subj so they reflect your specific host.
openssl req -new -x509 -sha256 -key root-ca-key.pem -subj "/C=CA/ST=ONTARIO/L=TORONTO/O=ORG/OU=UNIT/CN=ROOT" -out root-ca.pem -days 730

Next, create the admin certificate. This certificate is used to gain elevated rights for performing administrative tasks relating to the security plugin.

# Create a private key for the admin certificate.
openssl genrsa -out admin-key-temp.pem 2048

# Convert the private key to PKCS#8.
openssl pkcs8 -inform PEM -outform PEM -in admin-key-temp.pem -topk8 -nocrypt -v1 PBE-SHA1-3DES -out admin-key.pem
   
# Create the CSR. A common name (CN) of "A" is acceptable because this certificate is
# used for authenticating elevated access and is not tied to a host.
openssl req -new -key admin-key.pem -subj "/C=CA/ST=ONTARIO/L=TORONTO/O=ORG/OU=UNIT/CN=A" -out admin.csr
   
# Sign the admin certificate with the root certificate and private key you created earlier.
openssl x509 -req -in admin.csr -CA root-ca.pem -CAkey root-ca-key.pem -CAcreateserial -sha256 -out admin.pem -days 730

Create a certificate for the node being configured.

# Create a private key for the node certificate.
openssl genrsa -out node1-key-temp.pem 2048
   
# Convert the private key to PKCS#8.
openssl pkcs8 -inform PEM -outform PEM -in node1-key-temp.pem -topk8 -nocrypt -v1 PBE-SHA1-3DES -out node1-key.pem
   
# Create the CSR and replace the arguments passed to -subj so they reflect your specific host.
# The CN should match a DNS A record for the host--do not use the hostname.
openssl req -new -key node1-key.pem -subj "/C=CA/ST=ONTARIO/L=TORONTO/O=ORG/OU=UNIT/CN=node1.dns.a-record" -out node1.csr
   
# Create an extension file that defines a SAN DNS name for the host. This
# should match the DNS A record of the host.
echo 'subjectAltName=DNS:node1.dns.a-record' > node1.ext
   
# Sign the node certificate with the root certificate and private key that you created earlier.
openssl x509 -req -in node1.csr -CA root-ca.pem -CAkey root-ca-key.pem -CAcreateserial -sha256 -out node1.pem -days 730 -extfile node1.ext

Remove temporary files that are no longer required.
```
rm *temp.pem *csr *ext
```

Add these certificates to opensearch.yml as described in Generate Certificates. Advanced users might also choose to append the settings using a script:

#! /bin/bash

# Before running this script, make sure to replace the /path/to your OpenSearch directory,
# and remember to replace the CN in the node's distinguished name with a real
# DNS A record.

echo "plugins.security.ssl.transport.pemcert_filepath: /path/to/opensearch-2.3.0/config/node1.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.transport.pemkey_filepath: /path/to/opensearch-2.3.0/config/node1-key.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.transport.pemtrustedcas_filepath: /path/to/opensearch-2.3.0/config/root-ca.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.http.enabled: true" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.http.pemcert_filepath: /path/to/opensearch-2.3.0/config/node1.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.http.pemkey_filepath: /path/to/opensearch-2.3.0/config/node1-key.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.ssl.http.pemtrustedcas_filepath: /path/to/opensearch-2.3.0/config/root-ca.pem" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.allow_default_init_securityindex: true" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.authcz.admin_dn:" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "  - 'CN=A,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA'" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.nodes_dn:" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "  - 'CN=node1.dns.a-record,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA'" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.audit.type: internal_opensearch" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.enable_snapshot_restore_privilege: true" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.check_snapshot_restore_write_privileges: true" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml
echo "plugins.security.restapi.roles_enabled: [\"all_access\", \"security_rest_api_access\"]" | sudo tee -a /path/to/opensearch-2.3.0/config/opensearch.yml

(Optional) Add trust for the self-signed root certificate.

# Copy the root certificate to the correct directory
sudo cp /path/to/opensearch-2.3.0/config/root-ca.pem /etc/pki/ca-trust/source/anchors/

# Add trust
sudo update-ca-trust

Configure a user

Users are defined and authenticated by OpenSearch in a variety of ways. One method, which does not require additional backend infrastructure, is to manually configure users in internal_users.yml. See YAML files for more information about configuring users. The following steps explain how to remove all demo users except for the admin user and how to replace the admin default password using a script.

Make the security plugin scripts executable.

chmod 755 /path/to/opensearch-2.3.0/plugins/opensearch-security/tools/*.sh

Run hash.sh to generate a new password.

This script will fail if a path to the JDK has not been defined.

 # Example output if a JDK isn't found...
 $ ./hash.sh
 **************************************************************************
 ** This tool will be deprecated in the next major release of OpenSearch **
 ** https://github.com/opensearch-project/security/issues/1755           **
 **************************************************************************
 which: no java in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/user/.local/bin:/home/user/bin)
 WARNING: nor OPENSEARCH_JAVA_HOME nor JAVA_HOME is set, will use 
 ./hash.sh: line 35: java: command not found

Declare an environment variable when you invoke the script in order to avoid issues:
```
 OPENSEARCH_JAVA_HOME=/path/to/opensearch-2.3.0/jdk ./hash.sh
```
Enter the desired password at the prompt and make a note of the output hash.

Open internal_users.yml.

vi /path/to/opensearch-2.3.0/config/opensearch-security/internal_users.yml

Remove all demo users except for admin and replace the hash with the output provided by hash.sh in a previous step. The file should look similar to the following example:

---
# This is the internal user database
# The hash value is a bcrypt hash and can be generated with plugin/tools/hash.sh

_meta:
   type: "internalusers"
   config_version: 2

# Define your internal users here

admin:
   hash: "$2y$1EXAMPLEQqwS8TUcoEXAMPLEeZ3lEHvkEXAMPLERqjyh1icEXAMPLE."
   reserved: true
   backend_roles:
   - "admin"
   description: "Admin user"

Apply changes

Now that TLS certificates are installed and demo users were removed or assigned new passwords, the last step is to apply the configuration changes. This last configuration step requires invoking securityadmin.sh while OpenSearch is running on the host.

Start OpenSearch. It must be running for securityadmin.sh to apply changes.

# Change directories
cd /path/to/opensearch-2.3.0/bin

# Run the service in the foreground
./opensearch

Open a separate terminal session with the host and navigate to the directory containing securityadmin.sh.
```
# Change to the correct directory
cd /path/to/opensearch-2.3.0/plugins/opensearch-security/tools
```

Invoke the script. See Apply changes using securityadmin.sh for definitions of the arguments you must pass.

# You can omit the environment variable if you declared this in your $PATH.
OPENSEARCH_JAVA_HOME=/path/to/opensearch-2.3.0/jdk ./securityadmin.sh -cd /path/to/opensearch-2.3.0/config/opensearch-security/ -cacert /path/to/opensearch-2.3.0/config/root-ca.pem -cert /path/to/opensearch-2.3.0/config/admin.pem -key /path/to/opensearch-2.3.0/config/admin-key.pem -icl -nhnv

Stop and restart the running OpenSearch process to apply the changes.

Verify that the service is running

OpenSearch is now running on your host with custom TLS certificates and a secure user for basic authentication. You can verify external connectivity by sending an API request to your OpenSearch node from another host.

During previous tests you directed requests to localhost. Now that TLS certificates have been applied and the new certificates reference your host’s actual DNS record, requests to localhost will fail the CN check and the certificate will be considered invalid. Instead, requests should be sent to the address you specified while generating the certificate.

You should add trust for the root certificate to your client before sending requests. If you do not add trust, then you must use the -k option so that cURL ignores CN and root certificate validation.

$ curl https://your.host.address:9200 -u admin:yournewpassword -k
{
  "name" : "hostname-here",
  "cluster_name" : "opensearch",
  "cluster_uuid" : "efC0ANNMQlGQ5TbhNflVPg",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.1.0",
    "build_type" : "tar",
    "build_hash" : "388c80ad94529b1d9aad0a735c4740dce2932a32",
    "build_date" : "2022-06-30T21:31:04.823801692Z",
    "build_snapshot" : false,
    "lucene_version" : "9.2.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

Run OpenSearch as a service with systemd

This section will guide you through creating a service for OpenSearch and registering it with systemd. After the service has been defined, you can enable, start, and stop the OpenSearch service using systemctl commands. The commands in this section reflect an environment where OpenSearch has been installed to /opt/opensearch and should be changed depending on your installation path.

The following configuration is only suitable for testing in a non-production environment. We do not recommend using the following configuration in a production environment. You should install OpenSearch with the RPM distribution if you want to run OpenSearch as a systemd-managed service on your host. The tarball installation does not define a specific installation path, users, roles, or permissions. Failure to properly secure your host environment can result in unexpected behavior.

Create a user for the OpenSearch service.

sudo adduser --system --shell /bin/bash -U --no-create-home opensearch

Add your user to the opensearch user group.
```
sudo usermod -aG opensearch $USER
```
Change the file owner to opensearch. Make sure to change the path if your OpenSearch files are in a different directory.
```
sudo chown -R opensearch /opt/opensearch/
```
Create the service file and open it for editing.
```
sudo vi /etc/systemd/system/opensearch.service
```

Enter the following example service configuration. Make sure to change references to the path if your OpenSearch files are in a different directory.

[Unit]
Description=OpenSearch
Wants=network-online.target
After=network-online.target

[Service]
Type=forking
RuntimeDirectory=data

WorkingDirectory=/opt/opensearch
ExecStart=/opt/opensearch/bin/opensearch -d

User=opensearch
Group=opensearch
StandardOutput=journal
StandardError=inherit
LimitNOFILE=65535
LimitNPROC=4096
LimitAS=infinity
LimitFSIZE=infinity
TimeoutStopSec=0
KillSignal=SIGTERM
KillMode=process
SendSIGKILL=no
SuccessExitStatus=143
TimeoutStartSec=75

[Install]
WantedBy=multi-user.target

Reload systemd manager configuration.
```
sudo systemctl daemon-reload
```

Enable the OpenSearch service.

sudo systemctl enable opensearch.service

Start the OpenSearch service.
```
sudo systemctl start opensearch
```
Verify that the service is running.
```
sudo systemctl status opensearch
```

Step 1: Download and unpack OpenSearch
Step 2: Configure important system settings
Step 3: (Optional) Test OpenSearch
- Option 1: Test your Opensearch settings with security enabled
- Option 2: Test your OpenSearch settings with security disabled
Step 4: Set up OpenSearch in your environment
Related links

WAS THIS PAGE HELPFUL?

✔ Yes ✖ No

Tell us why

350 characters left

Have a question? Ask us on the OpenSearch forum.

Want to contribute? Edit this page or create an issue.

Tarball

Step 1: Download and unpack OpenSearch

Step 2: Configure important system settings

Step 3: (Optional) Test OpenSearch

Option 1: Test your Opensearch settings with security enabled

Option 2: Test your OpenSearch settings with security disabled

Step 4: Set up OpenSearch in your environment

Configure TLS

Configure a user

Apply changes

Verify that the service is running

Run OpenSearch as a service with systemd

OpenSearch Links

Get Involved

Resources

Contact Us

Tarball

Step 1: Download and unpack OpenSearch

Step 2: Configure important system settings

Step 3: (Optional) Test OpenSearch

Option 1: Test your Opensearch settings with security enabled

Option 2: Test your OpenSearch settings with security disabled

Step 4: Set up OpenSearch in your environment

Configure TLS

Configure a user

Apply changes

Verify that the service is running

Run OpenSearch as a service with systemd

Related links