From 99a87a31d2b5a56c4f72c118610899dbccbbd65b Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Wed, 27 Apr 2022 14:28:18 -0500
Subject: [PATCH 01/12] Add RPM installation instructions

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 179 +++++++++++++++++++++++++++++++++++++
 1 file changed, 179 insertions(+)
 create mode 100644 _opensearch/install/rpm.md

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
new file mode 100644
index 0000000000..5c3cc426d8
--- /dev/null
+++ b/_opensearch/install/rpm.md
@@ -0,0 +1,179 @@
+---
+layout: default
+title: RPM
+parent: Install OpenSearch
+nav_order: 51
+---
+
+The RPM installation provides everything you need to run OpenSearch inside a Linux distribution. As such, you can also make use of YUM to install a compatible RPM OpenSearch package.
+
+RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in the terminal, macOS works, as well.
+
+There are two methods for installing OpenSearch on RPM:
+
+## Manual method
+
+1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
+
+2. On your host, use `rpm -ivh` to install the package. 
+
+  ```bash
+  rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
+  rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+  ```
+
+3. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+
+  ```bash
+  systemctl start opensearch
+  systemctl start opensearch-dashboards
+  ```
+
+   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
+
+4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
+
+   ```bash
+   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   ```
+
+## YUM method
+
+1. 1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
+
+2. Place the downloaded package manually into your `/etc/yum.repo.d/`. You can also add the OpenSearch package with the yum configuration manager, `yum-config-manager --add-repo`.
+
+3. Use `yum` to install the package.
+
+  ```bash
+  yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
+  yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+  ```
+
+4. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+
+  ```bash
+  systemctl start opensearch
+  systemctl start opensearch-dashboards
+  ```
+
+   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
+
+4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
+
+   ```bash
+   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   ```
+
+### (Optional) Set up Performance Analyzer
+
+In a tarball installation, Performance Analyzer collects data when it is enabled. But in order to read that data using the REST API on port 9600, you must first manually launch the associated reader agent process:
+
+1. Make Performance Analyzer accessible outside of the host machine
+
+   ```bash
+   cd /usr/share/opensearch # navigate to the OpenSearch home directory
+   cd plugins/opensearch_performance_analyzer/pa_config/
+   vi performance-analyzer.properties
+   ```
+
+   Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
+
+   ```
+   # ======================== OpenSearch performance analyzer plugin config =========================
+
+   # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
+
+   # WebService bind host; default to all interfaces
+   webservice-bind-host = 0.0.0.0
+
+   # Metrics data location
+   metrics-location = /dev/shm/performanceanalyzer/
+
+   # Metrics deletion interval (minutes) for metrics data.
+   # Interval should be between 1 to 60.
+   metrics-deletion-interval = 1
+
+   # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
+   # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
+   # the files and wouldn't like for them to be cleaned up.
+   cleanup-metrics-db-files = true
+
+   # WebService exposed by App's port
+   webservice-listener-port = 9600
+
+   # Metric DB File Prefix Path location
+   metrics-db-file-prefix-path = /tmp/metricsdb_
+
+   https-enabled = false
+
+   #Setup the correct path for certificates
+   certificate-file-path = specify_path
+
+   private-key-file-path = specify_path
+
+   # Plugin Stats Metadata file name, expected to be in the same location
+   plugin-stats-metadata = plugin-stats-metadata
+
+   # Agent Stats Metadata file name, expected to be in the same location
+   agent-stats-metadata = agent-stats-metadata
+   ```
+
+1. Make the CLI executable:
+
+   ```bash
+   sudo chmod +x ./bin/performance-analyzer-agent-cli
+   ```
+
+1. Launch the agent CLI:
+
+   ```bash
+   OPENSEARCH_HOME="$PWD" ./bin/performance-analyzer-agent-cli
+   ```
+
+1. In a separate window, enable the Performance Analyzer plugin:
+
+   ```bash
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   ```
+
+   If you receive the `curl: (52) Empty reply from server` error, you are likely protecting your cluster with the security plugin and you need to provide credentials. Modify the following command to use your username and password:
+
+   ```bash
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   ```
+
+1. Finally, enable the Root Cause Analyzer (RCA) framework
+
+   ```bash
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   ```
+
+   Similar to step 4, if you run into `curl: (52) Empty reply from server`, run the command below to enable RCA
+
+   ```bash
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   ```
+
+{% comment %}
+
+### (Optional) Removing Performance Analyzer
+
+See [Clean up Performance Analyzer files]({{site.url}}{{site.baseurl}}/plugins#optional-clean-up-performance-analyzer-files).
+
+{% endcomment %}
+
+## Upgrade RPM
+
+You can upgrade your RPM OpenSearch instance both manually and through YUM. 
+
+
+### Manual 
+
+Download the new version of OpenSearch you want to use, and then use `rmp -Uvh` to upgrade.
+
+### YUM
+
+To upgrade to the latest version of OpenSearch with YUM, use `yum upgrade`. You can also upgrade to a specific OpenSearch version by using `yum upgrade <package-version>`.

From 6bb7bbd8c6629515dec4e1a429b43a818d8b5072 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 09:06:11 -0500
Subject: [PATCH 02/12] Add more accurante instructions

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 185 +++++++++++++++++++++----------------
 1 file changed, 105 insertions(+), 80 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 5c3cc426d8..4438d30516 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -9,7 +9,7 @@ The RPM installation provides everything you need to run OpenSearch inside a Lin
 
 RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in the terminal, macOS works, as well.
 
-There are two methods for installing OpenSearch on RPM:
+There are two methods for installing OpenSearch on RPM. These steps assume that you already have `wget` installed.
 
 ## Manual method
 
@@ -40,130 +40,155 @@ There are two methods for installing OpenSearch on RPM:
 
 ## YUM method
 
-1. 1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
+YUM allows you to pull the RPM package from the YUM repository library. 
 
-2. Place the downloaded package manually into your `/etc/yum.repo.d/`. You can also add the OpenSearch package with the yum configuration manager, `yum-config-manager --add-repo`.
+1. Create a repository file for both OpenSearch and OpenSearch dashboards:
 
-3. Use `yum` to install the package.
+  ```curl
+  sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
+  ```
+
+  ```curl
+  sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/{{site.opensearch_version}}/opensearch-dashboards-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
+  ```
+
+2. Navigate to your YUM repository directory:
 
   ```bash
-  yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
-  yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+  cd /etc/yum.repos.d/
   ```
 
-4. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+3. Clean your YUM cache, to ensure a smooth installation:
 
   ```bash
-  systemctl start opensearch
-  systemctl start opensearch-dashboards
+  sudo yum clean all
   ```
 
-   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
+3. With the repository file downloaded, list all available versions of OpenSearch:
 
-4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
+  ```curl
+  sudo yum list | grep opensearch
+  ```
 
-   ```bash
-   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
-   ```
+3. Chose the version of OpenSearch you want to install: 
 
-### (Optional) Set up Performance Analyzer
+  ```bash
+  yum install opensearch
+  yum install opensearch-dashboards
+  ```
 
-In a tarball installation, Performance Analyzer collects data when it is enabled. But in order to read that data using the REST API on port 9600, you must first manually launch the associated reader agent process:
+  Unless otherwise indicated, the highest minor version of OpenSearch installs.
 
-1. Make Performance Analyzer accessible outside of the host machine
+  To install a specific version of OpenSearch
 
-   ```bash
-   cd /usr/share/opensearch # navigate to the OpenSearch home directory
-   cd plugins/opensearch_performance_analyzer/pa_config/
-   vi performance-analyzer.properties
-   ```
+  ```bash
+  yum install 'opensearch-{{site.opensearch_version}}'
+  ```
 
-   Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
+5. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
 
-   ```
-   # ======================== OpenSearch performance analyzer plugin config =========================
+  ```
+  Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
+  ```
 
-   # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
+  If correct, enter `yes`. The OpenSearch installation continues.
 
-   # WebService bind host; default to all interfaces
-   webservice-bind-host = 0.0.0.0
+6. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
-   # Metrics data location
-   metrics-location = /dev/shm/performanceanalyzer/
+  ```bash
+  systemctl start opensearch.service
+  systemctl start opensearch-dashboards.service
+  ```
 
-   # Metrics deletion interval (minutes) for metrics data.
-   # Interval should be between 1 to 60.
-   metrics-deletion-interval = 1
+  If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
-   # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
-   # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
-   # the files and wouldn't like for them to be cleaned up.
-   cleanup-metrics-db-files = true
+7. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
 
-   # WebService exposed by App's port
-   webservice-listener-port = 9600
+  ```bash
+  curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+  curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+  ```
 
-   # Metric DB File Prefix Path location
-   metrics-db-file-prefix-path = /tmp/metricsdb_
+To stop running OpenSearch, enter:
 
-   https-enabled = false
+```bash
+systemctl stop opensearch.service
+systemctl stop opensearch-dashboards.service
+```
 
-   #Setup the correct path for certificates
-   certificate-file-path = specify_path
 
-   private-key-file-path = specify_path
+## (Optional) Set up Performance Analyzer
 
-   # Plugin Stats Metadata file name, expected to be in the same location
-   plugin-stats-metadata = plugin-stats-metadata
+When enabled, the Performance Analyzer plugin collects data related to the performance of your OpenSearch instance. By default, the Performance Analyzer endpoints are not accessible outside the host machine.
 
-   # Agent Stats Metadata file name, expected to be in the same location
-   agent-stats-metadata = agent-stats-metadata
-   ```
+1. Make Performance Analyzer accessible outside of the host machine
 
-1. Make the CLI executable:
+  ```bash
+  cd /usr/share/opensearch # navigate to the OpenSearch home directory
+  cd plugins/opensearch_performance_analyzer/pa_config/
+  vi performance-analyzer.properties
+  ```
 
-   ```bash
-   sudo chmod +x ./bin/performance-analyzer-agent-cli
-   ```
+  Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
 
-1. Launch the agent CLI:
+  ```
+  # ======================== OpenSearch performance analyzer plugin config =========================
 
-   ```bash
-   OPENSEARCH_HOME="$PWD" ./bin/performance-analyzer-agent-cli
-   ```
+  # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
 
-1. In a separate window, enable the Performance Analyzer plugin:
+  # WebService bind host; default to all interfaces
+  webservice-bind-host = 0.0.0.0
 
-   ```bash
-   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
-   ```
+  # Metrics data location
+  metrics-location = /dev/shm/performanceanalyzer/
 
-   If you receive the `curl: (52) Empty reply from server` error, you are likely protecting your cluster with the security plugin and you need to provide credentials. Modify the following command to use your username and password:
+  # Metrics deletion interval (minutes) for metrics data.
+  # Interval should be between 1 to 60.
+  metrics-deletion-interval = 1
 
-   ```bash
-   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
-   ```
+  # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
+  # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
+  # the files and wouldn't like for them to be cleaned up.
+  cleanup-metrics-db-files = true
 
-1. Finally, enable the Root Cause Analyzer (RCA) framework
+  # WebService exposed by App's port
+  webservice-listener-port = 9600
 
-   ```bash
-   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
-   ```
+  # Metric DB File Prefix Path location
+  metrics-db-file-prefix-path = /tmp/metricsdb_
 
-   Similar to step 4, if you run into `curl: (52) Empty reply from server`, run the command below to enable RCA
+  https-enabled = false
 
-   ```bash
-   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
-   ```
+  #Setup the correct path for certificates
+  certificate-file-path = specify_path
+
+  private-key-file-path = specify_path
+
+  # Plugin Stats Metadata file name, expected to be in the same location
+  plugin-stats-metadata = plugin-stats-metadata
+
+  # Agent Stats Metadata file name, expected to be in the same location
+  agent-stats-metadata = agent-stats-metadata
+  ```
+
+2. Restart the OpenSearch service:
+
+  ```bash
+  systemctl restart opensearch.service
+  ```
+
+3. After OpenSearch is running, start the Performance Analyzer plugin:
 
-{% comment %}
+ ```bash
+ sudo systemctl start opensearch-performance-analyzer.service
+ ```
 
-### (Optional) Removing Performance Analyzer
+ To stop the Performance Analyzer, enter:
 
-See [Clean up Performance Analyzer files]({{site.url}}{{site.baseurl}}/plugins#optional-clean-up-performance-analyzer-files).
+ ```
+ sudo systemctl stop opensearch-performance-analyzer.service
+ ```
 
-{% endcomment %}
 
 ## Upgrade RPM
 
@@ -176,4 +201,4 @@ Download the new version of OpenSearch you want to use, and then use `rmp -Uvh`
 
 ### YUM
 
-To upgrade to the latest version of OpenSearch with YUM, use `yum upgrade`. You can also upgrade to a specific OpenSearch version by using `yum upgrade <package-version>`.
+To upgrade to the latest version of OpenSearch with YUM, use `yum upgrade`. You can also upgrade to a specific OpenSearch version by using `yum upgrade opensearch-<version-number>`.

From 0ba789a7c6e4faf385cf9b672c4b85c21b46aac7 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 09:56:54 -0500
Subject: [PATCH 03/12] fix typo

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 4438d30516..5f2f7d660e 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -9,13 +9,19 @@ The RPM installation provides everything you need to run OpenSearch inside a Lin
 
 RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in the terminal, macOS works, as well.
 
-There are two methods for installing OpenSearch on RPM. These steps assume that you already have `wget` installed.
+There are two methods for installing OpenSearch on RPM. 
 
 ## Manual method
 
+
 1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
 
-2. On your host, use `rpm -ivh` to install the package. 
+2. On your host, use `yum install` or `rpm -ivh` to install the package. We recommend using `yum install`, so that the required dependecies can be pulled from the YUM library. 
+
+  ```bash
+  yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
+  yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+  ```
 
   ```bash
   rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
@@ -29,14 +35,14 @@ There are two methods for installing OpenSearch on RPM. These steps assume that
   systemctl start opensearch-dashboards
   ```
 
-   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
+  If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
 4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
 
-   ```bash
-   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
-   ```
+  ```bash
+  curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+  curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+  ```
 
 ## YUM method
 

From 82e642a3d8d11f3dc03ea98a2ef1c10332919b98 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 11:27:16 -0500
Subject: [PATCH 04/12] Fix typos, part deux

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 5f2f7d660e..9a437ac6a4 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -5,11 +5,11 @@ parent: Install OpenSearch
 nav_order: 51
 ---
 
-The RPM installation provides everything you need to run OpenSearch inside a Linux distribution. As such, you can also make use of YUM to install a compatible RPM OpenSearch package.
+The RPM installation provides everything you need to run OpenSearch inside a RHEL distribution. 
 
-RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in the terminal, macOS works, as well.
+RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in your terminal application, macOS works, as well.
 
-There are two methods for installing OpenSearch on RPM. 
+There are two methods for installing OpenSearch on RPM: 
 
 ## Manual method
 
@@ -70,13 +70,13 @@ YUM allows you to pull the RPM package from the YUM repository library.
   sudo yum clean all
   ```
 
-3. With the repository file downloaded, list all available versions of OpenSearch:
+4. With the repository file downloaded, list all available versions of OpenSearch:
 
   ```curl
   sudo yum list | grep opensearch
   ```
 
-3. Chose the version of OpenSearch you want to install: 
+5. Chose the version of OpenSearch you want to install: 
 
   ```bash
   yum install opensearch
@@ -91,7 +91,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
   yum install 'opensearch-{{site.opensearch_version}}'
   ```
 
-5. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
+6. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
 
   ```
   Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
@@ -99,7 +99,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
 
   If correct, enter `yes`. The OpenSearch installation continues.
 
-6. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+7. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
   ```bash
   systemctl start opensearch.service
@@ -108,7 +108,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
 
   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
-7. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
+8. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
 
   ```bash
   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure

From 6f2b8b90c3639d37eed869e213936412644a01f3 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 11:29:43 -0500
Subject: [PATCH 05/12] Add more specific intro

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 9a437ac6a4..edf97a6b48 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -5,7 +5,7 @@ parent: Install OpenSearch
 nav_order: 51
 ---
 
-The RPM installation provides everything you need to run OpenSearch inside a RHEL distribution. 
+The RPM Package Manager (RPM) installation provides everything you need to run OpenSearch inside Red Hat or CentOS Linux distributions. 
 
 RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in your terminal application, macOS works, as well.
 

From 64741ac25884822d978b7e257d742f50ba006c95 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 11:53:30 -0500
Subject: [PATCH 06/12] Fix formatting

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 204 +++++++++++++++++++------------------
 1 file changed, 103 insertions(+), 101 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index edf97a6b48..08f5a059f8 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -5,6 +5,8 @@ parent: Install OpenSearch
 nav_order: 51
 ---
 
+# RPM
+
 The RPM Package Manager (RPM) installation provides everything you need to run OpenSearch inside Red Hat or CentOS Linux distributions. 
 
 RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in your terminal application, macOS works, as well.
@@ -18,31 +20,31 @@ There are two methods for installing OpenSearch on RPM:
 
 2. On your host, use `yum install` or `rpm -ivh` to install the package. We recommend using `yum install`, so that the required dependecies can be pulled from the YUM library. 
 
-  ```bash
-  yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
-  yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
-  ```
+   ```bash
+   yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+   ```
 
-  ```bash
-  rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
-  rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
-  ```
+   ```bash
+   rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+   ```
 
 3. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
-  ```bash
-  systemctl start opensearch
-  systemctl start opensearch-dashboards
-  ```
+   ```bash
+   systemctl start opensearch
+   systemctl start opensearch-dashboards
+   ```
 
-  If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
+   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
 4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
 
-  ```bash
-  curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-  curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
-  ```
+   ```bash
+   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   ```
 
 ## YUM method
 
@@ -50,77 +52,77 @@ YUM allows you to pull the RPM package from the YUM repository library.
 
 1. Create a repository file for both OpenSearch and OpenSearch dashboards:
 
-  ```curl
-  sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
-  ```
+   ```bash
+   sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
+   ```
 
-  ```curl
-  sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/{{site.opensearch_version}}/opensearch-dashboards-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
-  ```
+   ```bash
+   sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/{{site.opensearch_version}}/opensearch-dashboards-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
+   ```
 
 2. Navigate to your YUM repository directory:
 
-  ```bash
-  cd /etc/yum.repos.d/
-  ```
+   ```bash
+   cd /etc/yum.repos.d/
+   ```
 
 3. Clean your YUM cache, to ensure a smooth installation:
 
-  ```bash
-  sudo yum clean all
-  ```
+   ```bash
+   sudo yum clean all
+   ```
 
 4. With the repository file downloaded, list all available versions of OpenSearch:
 
-  ```curl
-  sudo yum list | grep opensearch
-  ```
+   ```bash
+   sudo yum list | grep opensearch
+   ```
 
 5. Chose the version of OpenSearch you want to install: 
 
-  ```bash
-  yum install opensearch
-  yum install opensearch-dashboards
-  ```
+   ```bash
+   yum install opensearch
+   yum install opensearch-dashboards
+   ```
 
-  Unless otherwise indicated, the highest minor version of OpenSearch installs.
+   Unless otherwise indicated, the highest minor version of OpenSearch installs.
 
-  To install a specific version of OpenSearch
+   To install a specific version of OpenSearch
 
-  ```bash
-  yum install 'opensearch-{{site.opensearch_version}}'
-  ```
+   ```bash
+   yum install 'opensearch-{{site.opensearch_version}}'
+   ```
 
 6. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
 
-  ```
-  Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
-  ```
+   ```bash
+   Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
+   ```
 
-  If correct, enter `yes`. The OpenSearch installation continues.
+   If correct, enter `yes`. The OpenSearch installation continues.
 
 7. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
-  ```bash
-  systemctl start opensearch.service
-  systemctl start opensearch-dashboards.service
-  ```
+   ```bash
+   systemctl start opensearch.service
+   systemctl start opensearch-dashboards.service
+   ```
 
   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
 8. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
 
-  ```bash
-  curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-  curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
-  ```
+   ```bash
+   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
+   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   ```
 
-To stop running OpenSearch, enter:
+   To stop running OpenSearch, enter:
 
-```bash
-systemctl stop opensearch.service
-systemctl stop opensearch-dashboards.service
-```
+   ```bash
+   systemctl stop opensearch.service
+   systemctl stop opensearch-dashboards.service
+   ```
 
 
 ## (Optional) Set up Performance Analyzer
@@ -129,71 +131,71 @@ When enabled, the Performance Analyzer plugin collects data related to the perfo
 
 1. Make Performance Analyzer accessible outside of the host machine
 
-  ```bash
-  cd /usr/share/opensearch # navigate to the OpenSearch home directory
-  cd plugins/opensearch_performance_analyzer/pa_config/
-  vi performance-analyzer.properties
-  ```
+   ```bash
+   cd /usr/share/opensearch # navigate to the OpenSearch home directory
+   cd plugins/opensearch_performance_analyzer/pa_config/
+   vi performance-analyzer.properties
+   ```
 
-  Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
+   Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
 
-  ```
-  # ======================== OpenSearch performance analyzer plugin config =========================
+   ```
+   # ======================== OpenSearch performance analyzer plugin config =========================
 
-  # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
+   # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
 
-  # WebService bind host; default to all interfaces
-  webservice-bind-host = 0.0.0.0
+   # WebService bind host; default to all interfaces
+   webservice-bind-host = 0.0.0.0
 
-  # Metrics data location
-  metrics-location = /dev/shm/performanceanalyzer/
+   # Metrics data location
+   metrics-location = /dev/shm/performanceanalyzer/
 
-  # Metrics deletion interval (minutes) for metrics data.
-  # Interval should be between 1 to 60.
-  metrics-deletion-interval = 1
+   # Metrics deletion interval (minutes) for metrics data.
+   # Interval should be between 1 to 60.
+   metrics-deletion-interval = 1
 
-  # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
-  # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
-  # the files and wouldn't like for them to be cleaned up.
-  cleanup-metrics-db-files = true
+   # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
+   # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
+   # the files and wouldn't like for them to be cleaned up.
+   cleanup-metrics-db-files = true
 
-  # WebService exposed by App's port
-  webservice-listener-port = 9600
+   # WebService exposed by App's port
+   webservice-listener-port = 9600
 
-  # Metric DB File Prefix Path location
-  metrics-db-file-prefix-path = /tmp/metricsdb_
+   # Metric DB File Prefix Path location
+   metrics-db-file-prefix-path = /tmp/metricsdb_
 
-  https-enabled = false
+   https-enabled = false
 
-  #Setup the correct path for certificates
-  certificate-file-path = specify_path
+   #Setup the correct path for certificates
+   certificate-file-path = specify_path
 
-  private-key-file-path = specify_path
+   private-key-file-path = specify_path
 
-  # Plugin Stats Metadata file name, expected to be in the same location
-  plugin-stats-metadata = plugin-stats-metadata
+   # Plugin Stats Metadata file name, expected to be in the same location
+   plugin-stats-metadata = plugin-stats-metadata
 
-  # Agent Stats Metadata file name, expected to be in the same location
-  agent-stats-metadata = agent-stats-metadata
-  ```
+   # Agent Stats Metadata file name, expected to be in the same location
+   agent-stats-metadata = agent-stats-metadata
+   ```
 
 2. Restart the OpenSearch service:
 
-  ```bash
-  systemctl restart opensearch.service
-  ```
+   ```bash
+   systemctl restart opensearch.service
+   ```
 
 3. After OpenSearch is running, start the Performance Analyzer plugin:
 
- ```bash
- sudo systemctl start opensearch-performance-analyzer.service
- ```
+  ```bash
+  sudo systemctl start opensearch-performance-analyzer.service
+  ```
 
- To stop the Performance Analyzer, enter:
+  To stop the Performance Analyzer, enter:
 
- ```
- sudo systemctl stop opensearch-performance-analyzer.service
- ```
+  ```bash
+  sudo systemctl stop opensearch-performance-analyzer.service
+  ```
 
 
 ## Upgrade RPM

From 4a7d99aaf6437cf63426a41352fba601cb695a2b Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 13:07:52 -0500
Subject: [PATCH 07/12] Add Peter's feedback

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 08f5a059f8..91eabb2996 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -7,7 +7,7 @@ nav_order: 51
 
 # RPM
 
-The RPM Package Manager (RPM) installation provides everything you need to run OpenSearch inside Red Hat or CentOS Linux distributions. 
+The RPM Package Manager (RPM) installation provides everything you need to run OpenSearch inside Red Hat or Red Hat-based Linux Distributions.  
 
 RPM supports CentOS 7 and 8, and Amazon Linux 2. If you have your own Java installation and set `JAVA_HOME` in your terminal application, macOS works, as well.
 
@@ -18,7 +18,13 @@ There are two methods for installing OpenSearch on RPM:
 
 1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
 
-2. On your host, use `yum install` or `rpm -ivh` to install the package. We recommend using `yum install`, so that the required dependecies can be pulled from the YUM library. 
+2. Import the public GPG key. This key verifies that the your OpenSearch instance is signed.
+
+   ```bash
+   sudo rpm --import https://artifacts.opensearch.org/publickeys/opensearch.pgp
+   ```
+
+3. On your host, use `sudo yum install` or `sudo rpm -ivh` to install the package. 
 
    ```bash
    yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
@@ -30,7 +36,7 @@ There are two methods for installing OpenSearch on RPM:
    rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
    ```
 
-3. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+4. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
    ```bash
    systemctl start opensearch
@@ -50,7 +56,7 @@ There are two methods for installing OpenSearch on RPM:
 
 YUM allows you to pull the RPM package from the YUM repository library. 
 
-1. Create a repository file for both OpenSearch and OpenSearch dashboards:
+1. Create a repository file for both OpenSearch and OpenSearch Dashboards:
 
    ```bash
    sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
@@ -110,7 +116,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
 
   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
-8. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
+8. Send requests to the server to verify that OpenSearch is running:
 
    ```bash
    curl -XGET https://localhost:9200 -u 'admin:admin' --insecure

From 3b6e10533b55c7a734406a0ac333c09e6ddf6daa Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 13:29:11 -0500
Subject: [PATCH 08/12] Add sudo to commands. Remove PA custom section

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 129 +++++++++----------------------------
 1 file changed, 30 insertions(+), 99 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 91eabb2996..075ce87ee6 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -27,30 +27,16 @@ There are two methods for installing OpenSearch on RPM:
 3. On your host, use `sudo yum install` or `sudo rpm -ivh` to install the package. 
 
    ```bash
-   yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
-   yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
+   sudo yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   sudo yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
    ```
 
    ```bash
-   rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
-   rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
-   ```
-
-4. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
-
-   ```bash
-   systemctl start opensearch
-   systemctl start opensearch-dashboards
-   ```
-
-   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
-
-4. Open a second terminal session, and send requests to the server to verify that OpenSearch is running:
-
-   ```bash
-   curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   sudo rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   sudo rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
    ```
+  
+   Once complete, you can run OpenSearch inside your distribution.
 
 ## YUM method
 
@@ -87,8 +73,8 @@ YUM allows you to pull the RPM package from the YUM repository library.
 5. Chose the version of OpenSearch you want to install: 
 
    ```bash
-   yum install opensearch
-   yum install opensearch-dashboards
+   sudo yum install opensearch
+   sudo yum install opensearch-dashboards
    ```
 
    Unless otherwise indicated, the highest minor version of OpenSearch installs.
@@ -96,7 +82,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
    To install a specific version of OpenSearch
 
    ```bash
-   yum install 'opensearch-{{site.opensearch_version}}'
+   sudo yum install 'opensearch-{{site.opensearch_version}}'
    ```
 
 6. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
@@ -105,104 +91,49 @@ YUM allows you to pull the RPM package from the YUM repository library.
    Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
    ```
 
-   If correct, enter `yes`. The OpenSearch installation continues.
+   If correct, enter `yes` or `y`. The OpenSearch installation continues.
+  
+   Once complete, you can run OpenSearch inside your distribution. 
 
-7. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
+## Run OpenSearch
+
+1. Run OpenSearch and OpenSearch Dashboards using `systemctl`.
 
    ```bash
-   systemctl start opensearch.service
-   systemctl start opensearch-dashboards.service
+   sudo systemctl start opensearch.service
+   sudo systemctl start opensearch-dashboards.service
    ```
 
   If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
 
-8. Send requests to the server to verify that OpenSearch is running:
+2. Send requests to the server to verify that OpenSearch is running:
 
    ```bash
    curl -XGET https://localhost:9200 -u 'admin:admin' --insecure
-   curl -XGET https://localhost:9200/_cat/plugins?v -u 'admin:admin' --insecure
+   curl -XGET https://localhost:9200/_cat/config?v -u 'admin:admin' --insecure
    ```
 
-   To stop running OpenSearch, enter:
+3. To stop running OpenSearch, enter:
 
    ```bash
-   systemctl stop opensearch.service
-   systemctl stop opensearch-dashboards.service
+   sudo systemctl stop opensearch.service
+   sudo systemctl stop opensearch-dashboards.service
    ```
 
 
 ## (Optional) Set up Performance Analyzer
 
-When enabled, the Performance Analyzer plugin collects data related to the performance of your OpenSearch instance. By default, the Performance Analyzer endpoints are not accessible outside the host machine.
-
-1. Make Performance Analyzer accessible outside of the host machine
-
-   ```bash
-   cd /usr/share/opensearch # navigate to the OpenSearch home directory
-   cd plugins/opensearch_performance_analyzer/pa_config/
-   vi performance-analyzer.properties
-   ```
-
-   Uncomment the line `#webservice-bind-host` and set it to `0.0.0.0`:
-
-   ```
-   # ======================== OpenSearch performance analyzer plugin config =========================
-
-   # NOTE: this is an example for Linux. Please modify the config accordingly if you are using it under other OS.
-
-   # WebService bind host; default to all interfaces
-   webservice-bind-host = 0.0.0.0
-
-   # Metrics data location
-   metrics-location = /dev/shm/performanceanalyzer/
-
-   # Metrics deletion interval (minutes) for metrics data.
-   # Interval should be between 1 to 60.
-   metrics-deletion-interval = 1
-
-   # If set to true, the system cleans up the files behind it. So at any point, we should expect only 2
-   # metrics-db-file-prefix-path files. If set to false, no files are cleaned up. This can be useful, if you are archiving
-   # the files and wouldn't like for them to be cleaned up.
-   cleanup-metrics-db-files = true
-
-   # WebService exposed by App's port
-   webservice-listener-port = 9600
-
-   # Metric DB File Prefix Path location
-   metrics-db-file-prefix-path = /tmp/metricsdb_
-
-   https-enabled = false
-
-   #Setup the correct path for certificates
-   certificate-file-path = specify_path
-
-   private-key-file-path = specify_path
-
-   # Plugin Stats Metadata file name, expected to be in the same location
-   plugin-stats-metadata = plugin-stats-metadata
-
-   # Agent Stats Metadata file name, expected to be in the same location
-   agent-stats-metadata = agent-stats-metadata
-   ```
-
-2. Restart the OpenSearch service:
-
-   ```bash
-   systemctl restart opensearch.service
-   ```
-
-3. After OpenSearch is running, start the Performance Analyzer plugin:
-
-  ```bash
-  sudo systemctl start opensearch-performance-analyzer.service
-  ```
+When enabled, the Performance Analyzer plugin collects data related to the performance of your OpenSearch instance. To start the Performance Analyzer plugin, enter:
 
-  To stop the Performance Analyzer, enter:
+```bash
+sudo systemctl start opensearch-performance-analyzer.service
+```
 
-  ```bash
-  sudo systemctl stop opensearch-performance-analyzer.service
-  ```
+To stop the Performance Analyzer, enter:
 
+```bash
+sudo systemctl stop opensearch-performance-analyzer.service
+```
 
 ## Upgrade RPM
 

From a6cc676cada20189fc070fe3defd4cf1a70d5ec9 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 13:37:36 -0500
Subject: [PATCH 09/12] More review feedback

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 34 +++++++++++++++++++++-------------
 1 file changed, 21 insertions(+), 13 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 075ce87ee6..798decca41 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -16,7 +16,7 @@ There are two methods for installing OpenSearch on RPM:
 ## Manual method
 
 
-1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}.
+1. Download the RPM package directly from the [OpenSearch downloads page](https://opensearch.org/downloads.html){:target='\_blank'}. The RPM package can be download both as `x64` and `arm64`. 
 
 2. Import the public GPG key. This key verifies that the your OpenSearch instance is signed.
 
@@ -26,6 +26,8 @@ There are two methods for installing OpenSearch on RPM:
 
 3. On your host, use `sudo yum install` or `sudo rpm -ivh` to install the package. 
 
+   **x64**
+
    ```bash
    sudo yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
    sudo yum install opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
@@ -36,6 +38,18 @@ There are two methods for installing OpenSearch on RPM:
    sudo rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-x64.rpm
    ```
   
+   **arm64**
+
+   ```bash
+   sudo yum install opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   sudo yum install opensearch-dashboards-{{site.opensearch_version}}-linux-arm64.rpm
+   ```
+
+   ```bash
+   sudo rpm -ivh opensearch-{{site.opensearch_version}}-linux-x64.rpm
+   sudo rpm -ivh opensearch-dashboards-{{site.opensearch_version}}-linux-arm64.rpm
+   ```
+  
    Once complete, you can run OpenSearch inside your distribution.
 
 ## YUM method
@@ -51,26 +65,22 @@ YUM allows you to pull the RPM package from the YUM repository library.
    ```bash
    sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/{{site.opensearch_version}}/opensearch-dashboards-{{site.opensearch_version}}.repo -o /etc/yum.repos.d/{{site.opensearch_version}}.repo
    ```
+  
+   To verify that the repos appear in your repo list, use `sudo yum repolist`.
 
-2. Navigate to your YUM repository directory:
-
-   ```bash
-   cd /etc/yum.repos.d/
-   ```
-
-3. Clean your YUM cache, to ensure a smooth installation:
+2. Clean your YUM cache, to ensure a smooth installation:
 
    ```bash
    sudo yum clean all
    ```
 
-4. With the repository file downloaded, list all available versions of OpenSearch:
+3. With the repository file downloaded, list all available versions of OpenSearch:
 
    ```bash
    sudo yum list | grep opensearch
    ```
 
-5. Chose the version of OpenSearch you want to install: 
+4. Chose the version of OpenSearch you want to install: 
 
    ```bash
    sudo yum install opensearch
@@ -85,7 +95,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
    sudo yum install 'opensearch-{{site.opensearch_version}}'
    ```
 
-6. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
+5. During installation, the installer stops to see if the GPG key matches the OpenSearch project. Verify that the `Fingerprint` matches the following:
 
    ```bash
    Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
@@ -104,8 +114,6 @@ YUM allows you to pull the RPM package from the YUM repository library.
    sudo systemctl start opensearch-dashboards.service
    ```
 
-  If you configure the security plugin for production use (or disable it), you can run OpenSearch using `./bin/opensearch`.
-
 2. Send requests to the server to verify that OpenSearch is running:
 
    ```bash

From f683c019567957d8dce8fec78e5bee69a687066f Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 16:03:30 -0500
Subject: [PATCH 10/12] Add additional feedback.

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 798decca41..89504563a1 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -54,7 +54,7 @@ There are two methods for installing OpenSearch on RPM:
 
 ## YUM method
 
-YUM allows you to pull the RPM package from the YUM repository library. 
+YUM, an RPM package management tool, allows you to pull the RPM package from the YUM repository library. 
 
 1. Create a repository file for both OpenSearch and OpenSearch Dashboards:
 
@@ -89,7 +89,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
 
    Unless otherwise indicated, the highest minor version of OpenSearch installs.
 
-   To install a specific version of OpenSearch
+   To install a specific version of OpenSearch:
 
    ```bash
    sudo yum install 'opensearch-{{site.opensearch_version}}'
@@ -129,7 +129,7 @@ YUM allows you to pull the RPM package from the YUM repository library.
    ```
 
 
-## (Optional) Set up Performance Analyzer
+## *(Optional)* Set up Performance Analyzer
 
 When enabled, the Performance Analyzer plugin collects data related to the performance of your OpenSearch instance. To start the Performance Analyzer plugin, enter:
 
@@ -154,4 +154,4 @@ Download the new version of OpenSearch you want to use, and then use `rmp -Uvh`
 
 ### YUM
 
-To upgrade to the latest version of OpenSearch with YUM, use `yum upgrade`. You can also upgrade to a specific OpenSearch version by using `yum upgrade opensearch-<version-number>`.
+To upgrade to the latest version of OpenSearch with YUM, use `sudo yum update`. You can also upgrade to a specific OpenSearch version by using `sudo yum upgrade opensearch-<version-number>`.

From 33656ea276e6ba98ec5249ec8addc5435eb2e5e8 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 16:07:46 -0500
Subject: [PATCH 11/12] Last update

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 89504563a1..1e94a1c5cc 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -154,4 +154,4 @@ Download the new version of OpenSearch you want to use, and then use `rmp -Uvh`
 
 ### YUM
 
-To upgrade to the latest version of OpenSearch with YUM, use `sudo yum update`. You can also upgrade to a specific OpenSearch version by using `sudo yum upgrade opensearch-<version-number>`.
+To upgrade to the latest version of OpenSearch with YUM, use `sudo yum update`. You can also upgrade to a specific OpenSearch version by using `sudo yum update opensearch-<version-number>`.

From 6c7a814b3d477e8209cb124c75e9437bbefcbe1c Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <naarcha@amazon.com>
Date: Tue, 3 May 2022 16:53:35 -0500
Subject: [PATCH 12/12] One last typo

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
---
 _opensearch/install/rpm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_opensearch/install/rpm.md b/_opensearch/install/rpm.md
index 1e94a1c5cc..fd57955d47 100644
--- a/_opensearch/install/rpm.md
+++ b/_opensearch/install/rpm.md
@@ -80,7 +80,7 @@ YUM, an RPM package management tool, allows you to pull the RPM package from the
    sudo yum list | grep opensearch
    ```
 
-4. Chose the version of OpenSearch you want to install: 
+4. Choose the version of OpenSearch you want to install: 
 
    ```bash
    sudo yum install opensearch