Skip to content

Latest commit

 

History

History
548 lines (434 loc) · 26.6 KB

rpm.md

File metadata and controls

548 lines (434 loc) · 26.6 KB
Raw
layout title parent redirect_from nav_order canonical_url
default
RPM
Installing OpenSearch
/opensearch/install/rpm/
51

{% comment %} The following liquid syntax declares a variable, major_version_mask, which is transformed into "N.x" where "N" is the major version number. This is required for proper versioning references to the Yum repo. {% endcomment %} {% assign version_parts = site.opensearch_major_minor_version | split: "." %} {% assign major_version_mask = version_parts[0] | append: ".x" %}

RPM

Installing OpenSearch using RPM Package Manager (RPM) simplifies the process considerably compared to the Tarball method. Several technical considerations, such as the installation path, location of configuration files, and creation of a service managed by systemd, as examples, are handled automatically by the package manager.

Generally speaking, installing OpenSearch from the RPM distribution can be broken down into a few steps:

  1. Download and install OpenSearch.
    • Install manually from an RPM package or from a YUM repository.
  2. (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.
  3. Configure OpenSearch for your environment.
    • Apply basic settings to OpenSearch and start using it in your environment.

The RPM distribution provides everything you need to run OpenSearch inside Red Hat or Red Hat–based Linux Distributions. For a list of supported operating systems, see Operating system compatibility.

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. {:.note}

Step 1: Download and install OpenSearch

Install OpenSearch from a package

  1. Download the RPM package for the desired version directly from the OpenSearch downloads page{:target='_blank'}. The RPM package can be downloaded for both x64 and arm64 architectures.

  2. Import the public GNU Privacy Guard (GPG) key. This key verifies that your OpenSearch instance is signed.

    sudo rpm --import https://artifacts.opensearch.org/publickeys/opensearch.pgp

    {% include copy.html %}

  3. From the CLI, you can install the package with rpm or yum:

    # For new installations of OpenSearch 2.12 and later, you must define a custom admin password in order to set up a demo security configuration.
# Use one of the following commands to define a custom admin password:

## Install the x64 package using yum.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm

## Install the x64 package using rpm.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm

## Install the arm64 package using yum.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install opensearch-{{site.opensearch_version}}-linux-arm64.rpm

## Install the arm64 package using rpm.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> rpm -ivh opensearch-{{site.opensearch_version}}-linux-arm64.rpm

# Use the following command for OpenSearch versions 2.11 and earlier:

## Install the x64 package using yum.
sudo yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm

## Install the x64 package using rpm.
sudo rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm

## Install the arm64 package using yum.
sudo yum install opensearch-{{site.opensearch_version}}-linux-arm64.rpm

## Install the arm64 package using rpm.
sudo rpm -ivh opensearch-{{site.opensearch_version}}-linux-arm64.rpm

  4. After the installation succeeds, enable OpenSearch as a service.

    sudo systemctl enable opensearch

    {% include copy.html %}

  5. Start OpenSearch.

    sudo systemctl start opensearch

    {% include copy.html %}

  6. Verify that OpenSearch launched correctly:

    sudo systemctl status opensearch

    {% include copy.html %}

Install OpenSearch from a YUM repository

YUM, the primary package management tool for Red Hat–based operating systems, allows you to download and install the RPM package from the YUM repository.

  1. Create a local repository file for OpenSearch:

    sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/{{major_version_mask}}/opensearch-{{major_version_mask}}.repo -o /etc/yum.repos.d/opensearch-{{major_version_mask}}.repo

    {% include copy.html %}

  2. Clean your YUM cache to ensure a smooth installation:

    sudo yum clean all

    {% include copy.html %}

  3. Verify that the repository was created successfully.

    sudo yum repolist

    {% include copy.html %}

  4. With the repository file downloaded, list all available versions of OpenSearch:

    sudo yum list opensearch --showduplicates

    {% include copy.html %}

  5. Choose the version of OpenSearch you want to install:

    • Unless otherwise indicated, the latest available version of OpenSearch is installed.
    # For OpenSearch versions 2.12 and later, a custom admin password is required in order to set up a demo security configuration for a new installation.
# To set a custom admin password, use the following commands:
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install opensearch

# Use the following command for OpenSearch versions 2.11 and earlier:
sudo yum install opensearch

    {% include copy.html %}

    • To install a specific version of OpenSearch:
    # For OpenSearch versions 2.12 and later, a custom admin password is required in order to set up a demo security configuration for a new installation.
# To set a custom admin password, use the following commands:
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install 'opensearch-{{site.opensearch_version}}'

# Use the following command for OpenSearch versions 2.11 and earlier:
sudo yum install 'opensearch-{{site.opensearch_version}}'

    {% include copy.html %}

  6. During installation, the installer will present you with the GPG key fingerprint. Verify that the information matches the following:

    Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc

    {% include copy.html %}

    • If correct, enter yes or y. The OpenSearch installation continues.

  7. Once complete, you can run OpenSearch.

    sudo systemctl start opensearch

    {% include copy.html %}

  8. Verify that OpenSearch launched correctly.

    sudo systemctl status opensearch

    {% include copy.html %}

Step 2: (Optional) Test OpenSearch

Before proceeding with any configuration, 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.

When OpenSearch is installed using the RPM package, some demo security settings are automatically applied. This includes self-signed TLS certificates and several users and roles. If you would like to configure these yourself, see Set up OpenSearch in your environment.

An OpenSearch node in its default configuration (with demo certificates and users with default passwords) is not suitable for a production environment. If you plan to use the node in a production environment, 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. {: .warning}

  1. 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:<custom-admin-password>' --insecure

      {% include copy.html %}

      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:<custom-admin-password>' --insecure

      {% include copy.html %}

      The response should look like this:

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

Step 3: 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 populated by default user names and passwords. 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. {:.note}

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 mitigate any issues caused by a bad configuration. {:.tip}

  1. Open opensearch.yml.

    sudo vi /etc/opensearch/opensearch.yml

    {% include copy.html %}

  2. 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

    {% include copy.html %}

  3. Save your changes and close the file.

  4. Specify initial and maximum JVM heap sizes.

    1. Open jvm.options.

      vi /etc/opensearch/jvm.options

      {% include copy.html %}

    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
        {% include copy.html %}

    3. Save your changes and close the file.

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.

  1. Navigate to the directory where the certificates will be stored.

    cd /etc/opensearch

    {% include copy.html %}

  2. Delete the demo certificates.

    sudo rm -f *pem

    {% include copy.html %}

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

    # Create a private key for the root certificate
sudo 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.
sudo 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

  4. 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.
sudo openssl genrsa -out admin-key-temp.pem 2048

# Convert the private key to PKCS#8.
sudo openssl pkcs8 -inform PEM -outform PEM -in admin-key-temp.pem -topk8 -nocrypt -v1 PBE-SHA1-3DES -out admin-key.pem

# Create the certficiate signing request (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.
sudo 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.
sudo openssl x509 -req -in admin.csr -CA root-ca.pem -CAkey root-ca-key.pem -CAcreateserial -sha256 -out admin.pem -days 730

  5. Create a certificate for the node being configured.

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

# Convert the private key to PKCS#8.
sudo 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.
sudo 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.
sudo sh -c 'echo subjectAltName=DNS:node1.dns.a-record > node1.ext'

# Sign the node certificate with the root certificate and private key that you created earlier.
sudo 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

  6. Remove temporary files that are no longer required.

    sudo rm -f *temp.pem *csr *ext

    {% include copy.html %}

  7. Make sure the remaining certificates are owned by the opensearch user.

    sudo chown opensearch:opensearch admin-key.pem admin.pem node1-key.pem node1.pem root-ca-key.pem root-ca.pem root-ca.srl

    {% include copy.html %}

  8. 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 CN in the 
# node's distinguished name with a real DNS A record.

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

    {% include copy.html %}

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

    # Copy the root certificate to the correct directory
sudo cp /etc/opensearch/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 that 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.

  1. Navigate to the Security plugins tools directory.

    cd /usr/share/opensearch/plugins/opensearch-security/tools

    {% include copy.html %}

  2. 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=/usr/share/opensearch/jdk ./hash.sh

      {% include copy.html %}

    • Enter the desired password at the prompt and make a note of the output hash.

  3. Open internal_users.yml.

    sudo vi /etc/opensearch/opensearch-security/internal_users.yml

    {% include copy.html %}

  4. 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"

    {% include copy.html %}

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.

  1. OpenSearch must be running for securityadmin.sh to apply changes. If you made changes to opensearch.yml, restart OpenSearch.

    sudo systemctl restart opensearch

  2. Open a separate terminal session with the host and navigate to the directory containing securityadmin.sh.

    # Change to the correct directory
cd /usr/share/opensearch/plugins/opensearch-security/tools

  3. 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=/usr/share/opensearch/jdk ./securityadmin.sh -cd /etc/opensearch/opensearch-security/ -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/admin.pem -key /etc/opensearch/admin-key.pem -icl -nhnv

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 the previous test 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. {:.tip}

$ curl https://your.host.address:9200 -u admin:yournewpassword -k
{
  "name" : "hostname-here",
  "cluster_name" : "opensearch",
  "cluster_uuid" : "efC0ANNMQlGQ5TbhNflVPg",
  "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/"
}

Upgrade to a newer version

OpenSearch instances installed using RPM or YUM can be easily upgraded to a newer version. We recommend updating with YUM, but you can also upgrade using RPM.

Manual upgrade with RPM

Download the RPM package for the desired upgrade version directly from the OpenSearch Project downloads page{:target='_blank'}.

Navigate to the directory containing the distribution and run the following command:

rpm -Uvh opensearch-{{site.opensearch_version}}-linux-x64.rpm

{% include copy.html %}

YUM

To upgrade to the latest version of OpenSearch using YUM:

sudo yum update opensearch

{% include copy.html %}

You can also upgrade to a specific OpenSearch version:

sudo yum update opensearch-<version-number>

{% include copy.html %}

Automatically restart the service after a package upgrade

The OpenSearch RPM package does not currently support automatically restarting the service after a package upgrade.

Related links