diff --git a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx
index 4c7480d24b2..41aa90ec8fb 100644
--- a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx
+++ b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
 
 navigation:
   - requirements
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - windows
   - macos
@@ -27,16 +27,14 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/postgresql_rhel_9), [RHEL 8](linux_x86_64/postgresql_rhel_8), [RHEL 7](linux_x86_64/postgresql_rhel_7)
+- [RHEL 9](linux_x86_64/postgresql_rhel_9), [RHEL 8](linux_x86_64/postgresql_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/postgresql_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/postgresql_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/postgresql_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/postgresql_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/postgresql_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/postgresql_other_linux_9), [Rocky Linux 8](linux_x86_64/postgresql_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/postgresql_other_linux_9), [AlmaLinux 8](linux_x86_64/postgresql_other_linux_8)
 
-- [CentOS 7](linux_x86_64/postgresql_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](linux_x86_64/postgresql_sles_15), [SLES 12](linux_x86_64/postgresql_sles_12)
@@ -45,7 +43,7 @@ Select a link to access the applicable installation instructions:
 
 - [Ubuntu 22.04](linux_x86_64/postgresql_ubuntu_22), [Ubuntu 20.04](linux_x86_64/postgresql_ubuntu_20)
 
-- [Debian 12](linux_x86_64/postgresql_debian_12), [Debian 11](linux_x86_64/postgresql_debian_11), [Debian 10](linux_x86_64/postgresql_debian_10)
+- [Debian 12](linux_x86_64/postgresql_debian_12), [Debian 11](linux_x86_64/postgresql_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx
index abc801c92f9..03e4cc81418 100644
--- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx
+++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx
@@ -6,17 +6,14 @@ indexCards: none
 navigation:
   - postgresql_rhel_9
   - postgresql_rhel_8
-  - postgresql_rhel_7
   - postgresql_other_linux_9
   - postgresql_other_linux_8
-  - postgresql_centos_7
   - postgresql_sles_15
   - postgresql_sles_12
   - postgresql_ubuntu_22
   - postgresql_ubuntu_20
   - postgresql_debian_12
   - postgresql_debian_11
-  - postgresql_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,14 +24,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](postgresql_rhel_8)
 
-- [RHEL 7](postgresql_rhel_7)
-
 - [Oracle Linux (OL) 9](postgresql_rhel_9)
 
 - [Oracle Linux (OL) 8](postgresql_rhel_8)
 
-- [Oracle Linux (OL) 7](postgresql_rhel_7)
-
 - [Rocky Linux 9](postgresql_other_linux_9)
 
 - [Rocky Linux 8](postgresql_other_linux_8)
@@ -43,8 +36,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](postgresql_other_linux_8)
 
-- [CentOS 7](postgresql_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](postgresql_sles_15)
@@ -60,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](postgresql_debian_12)
 
 - [Debian 11](postgresql_debian_11)
-
-- [Debian 10](postgresql_debian_10)
diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx
deleted file mode 100644
index a44073dd5c7..00000000000
--- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_centos_7.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing PostgreSQL on CentOS 7 x86_64
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  !!! Note
-  Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/).
-  !!!
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install postgresql<xx>-server postgresql<xx>-contrib
-```
-
-Where `<xx>` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`.
diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx
deleted file mode 100644
index c370c33a3c7..00000000000
--- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_10.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-navTitle: Debian 10
-title: Installing PostgreSQL on Debian 10 x86_64
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  !!! Note
-  Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/).
-  !!!
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install postgresql-<xx>
-```
-
-Where `<xx>` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`.
diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx
deleted file mode 100644
index 0480542fcee..00000000000
--- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_7.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing PostgreSQL on RHEL 7 or OL 7 x86_64
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  !!! Note
-  Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/).
-  !!!
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install postgresql<xx>-server postgresql<xx>-contrib
-```
-
-Where `<xx>` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`.
diff --git a/advocacy_docs/supported-open-source/postgresql/postgresql_v_documentation.pdf b/advocacy_docs/supported-open-source/postgresql/postgresql_v_documentation.pdf
new file mode 100644
index 00000000000..8b4196229bf
Binary files /dev/null and b/advocacy_docs/supported-open-source/postgresql/postgresql_v_documentation.pdf differ
diff --git a/install_template/config.yaml b/install_template/config.yaml
index ecb22b2b957..fc153d1db70 100644
--- a/install_template/config.yaml
+++ b/install_template/config.yaml
@@ -1,18 +1,12 @@
 products:
   - name: EDB JDBC Connector
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [42.5.4.2]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [42.5.4.2]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [42.5.4.2]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [42.5.4.2]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [42.5.4.2]
@@ -25,9 +19,6 @@ products:
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [42.5.4.2]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [42.5.4.2]
       - name: Debian 11
         arch: x86_64
         supported versions: [42.5.4.2]
@@ -43,18 +34,18 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [42.5.4.2]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [42.5.4.2]
       - name: SLES 12
-        arch: ppc64le
-        supported versions: [42.5.4.2]
-      - name: SLES 15
         arch: x86_64
         supported versions: [42.5.4.2]
       - name: SLES 15
         arch: ppc64le
         supported versions: [42.5.4.2]
+      - name: SLES 12
+        arch: ppc64le
+        supported versions: [42.5.4.2]
   - name: Migration Toolkit
     platforms:
       - name: RHEL 8 or OL 8
@@ -69,18 +60,6 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [55]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [55]
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [55]
-      - name: SLES 15
-        arch: x86_64
-        supported versions: [55]
-      - name: SLES 12
-        arch: ppc64le
-        supported versions: [55]
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [55]
@@ -90,26 +69,26 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [55]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [55]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [55]
       - name: RHEL 9
         arch: ppc64le
         supported versions: [55]
+      - name: SLES 15
+        arch: x86_64
+        supported versions: [55]
       - name: SLES 15
         arch: ppc64le
         supported versions: [55]
       - name: SLES 12
         arch: x86_64
         supported versions: [55]
+      - name: SLES 12
+        arch: ppc64le
+        supported versions: [55]
   - name: EDB OCL Connector
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [14, 15, 16]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [14, 15, 16]
@@ -122,18 +101,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [14, 15, 16]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [14, 15, 16]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [14, 15, 16]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [14, 15, 16]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [14, 15, 16]
       - name: Debian 11
         arch: x86_64
         supported versions: [14, 15, 16]
@@ -149,23 +122,20 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [15, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [14, 15, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [14, 15, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [14, 15, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [14, 15, 16]
   - name: EDB ODBC Connector
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [13, 16]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [13, 16]
@@ -178,18 +148,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [13, 16]      
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [13, 16]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [13, 16]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [13, 16]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [13, 16]
       - name: Debian 11
         arch: x86_64
         supported versions: [13, 16]
@@ -205,23 +169,20 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [13, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [13, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [13, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [13, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [13, 16]
   - name: EDB pgBouncer
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [1]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [1]
@@ -234,18 +195,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [1]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [1]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [1]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [1]      
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [1]
       - name: Debian 11
         arch: x86_64
         supported versions: [1]
@@ -261,23 +216,20 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [1]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [1]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [1]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [1]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [1]
   - name: EDB Pgpool-II
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [4]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [4]
@@ -290,18 +242,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [4]      
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [4]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [4]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [4]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [4]
       - name: Debian 11
         arch: x86_64
         supported versions: [4]
@@ -317,23 +263,20 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [4]
   - name: EDB Pgpool-II Extensions
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [4]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [4]
@@ -346,18 +289,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [4]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [4]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [4]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [4]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [4]
       - name: Debian 11
         arch: x86_64
         supported versions: [4]
@@ -373,32 +310,26 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [4]
   - name: EDB Postgres Advanced Server
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
@@ -411,9 +342,6 @@ products:
       - name: RHEL 8
         arch: ppc64le
         supported versions: [11, 12, 13, 14, 15, 16]
-      - name: RHEL 7
-        arch: ppc64le
-        supported versions: [11, 12, 13, 14, 15, 16]
       - name: Debian 12
         arch: x86_64
         supported versions: [16]
@@ -423,41 +351,32 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
       - name: SLES 15
-        arch: x86_64
+        arch: ppc64le
         supported versions: [11, 12, 13, 14, 15, 16]
       - name: SLES 12
-        arch: ppc64le
+        arch: x86_64
         supported versions: [11, 12, 13, 14, 15, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [11, 12, 13, 14, 15, 16]
   - name: EDB Postgres Extended Server
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [15, 16]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [15, 16]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [15, 16]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [15, 16]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [15, 16]
@@ -473,9 +392,6 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [15, 16]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [15, 16]
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [15, 16]
@@ -484,18 +400,12 @@ products:
         supported versions: [15, 16]
   - name: EDB*Plus
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [41]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [41]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [41]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [41]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [41]
@@ -508,9 +418,6 @@ products:
       - name: RHEL 8
         arch: ppc64le
         supported versions: [41]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [41]
       - name: Debian 11
         arch: x86_64
         supported versions: [41]
@@ -520,32 +427,26 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [41]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [41]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [41]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [41]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [41]
   - name: Failover Manager
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [4]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [4]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [4]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [4]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [4]
@@ -558,9 +459,6 @@ products:
       - name: RHEL 8
         arch: ppc64le
         supported versions: [4]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [4]
       - name: Debian 11
         arch: x86_64
         supported versions: [4]
@@ -576,32 +474,26 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [4]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [4]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [4]
   - name: Hadoop Foreign Data Wrapper
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [2]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [2]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [2]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [2]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [2]
@@ -614,9 +506,6 @@ products:
       - name: RHEL 8
         arch: ppc64le
         supported versions: [2]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [2]
       - name: Debian 11
         arch: x86_64
         supported versions: [2]
@@ -632,32 +521,26 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [2]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [2]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [2]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [2]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [2]
   - name: MongoDB Foreign Data Wrapper
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [5]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [5]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [5]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [5]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [5]
@@ -670,9 +553,6 @@ products:
       - name: RHEL 8
         arch: ppc64le
         supported versions: [5]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [5]
       - name: Debian 11
         arch: x86_64
         supported versions: [5]
@@ -688,32 +568,26 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [5]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [5]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [5]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [5]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [5]
   - name: MySQL Foreign Data Wrapper
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [2]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [2]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [2]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [2]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [2]
@@ -732,9 +606,6 @@ products:
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [2]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [2]
       - name: Debian 11
         arch: x86_64
         supported versions: [2]
@@ -744,32 +615,26 @@ products:
       - name: Debian 12
         arch: arm64
         supported versions: [2]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [2]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [2]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [2]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [2]
   - name: PostGIS
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [3.4.2]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [3.4.2]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [3.4.2]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [3.4.2]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [3.4.2]
@@ -797,35 +662,26 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [3.4.2]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [3.4.2]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [3.4.2]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [3.4.2]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [3.4.2]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [3.4.2]
   - name: Postgres Enterprise Manager server
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [8, 9]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [8, 9]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [8, 9]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [8, 9]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [8, 9]
@@ -847,41 +703,32 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [8, 9]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [8, 9]
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [8, 9]
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [8, 9]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [8, 9]
       - name: SLES 15
-        arch: x86_64
+        arch: ppc64le
         supported versions: [8, 9]
       - name: SLES 12
-        arch: ppc64le
+        arch: x86_64
         supported versions: [8, 9]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [8, 9]
   - name: Postgres Enterprise Manager agent
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [8, 9]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [8, 9]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [8, 9]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [8, 9]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [8, 9]
@@ -903,32 +750,26 @@ products:
       - name: Debian 11
         arch: x86_64
         supported versions: [8, 9]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [8, 9]
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [8, 9]
       - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [8, 9]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [8, 9]
       - name: SLES 15
-        arch: x86_64
+        arch: ppc64le
         supported versions: [8, 9]
       - name: SLES 12
-        arch: ppc64le
+        arch: x86_64
         supported versions: [8, 9]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [8, 9]
   - name: PostgreSQL
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [15, 16]
       - name: RHEL 8
         arch: ppc64le
         supported versions: [15, 16]
@@ -941,18 +782,12 @@ products:
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [15, 16]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [15, 16]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [15, 16]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [15, 16]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [15, 16]
       - name: Debian 12
         arch: x86_64
         supported versions: [15, 16]
@@ -968,54 +803,39 @@ products:
       - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [15, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: x86_64
         supported versions: [15, 16]
-      - name: SLES 12
+      - name: SLES 15
         arch: ppc64le
         supported versions: [15, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: x86_64
         supported versions: [15, 16]
-      - name: SLES 15
+      - name: SLES 12
         arch: ppc64le
         supported versions: [15, 16]
   - name: Replication Server
     platforms:
-      - name: CentOS 7
-        arch: x86_64
-        supported versions: [7]
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
         supported versions: [7]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
         supported versions: [7]
-      - name: RHEL 7 or OL 7
-        arch: x86_64
-        supported versions: [7]
       - name: RHEL 8 or OL 8
         arch: x86_64
         supported versions: [7]
       - name: RHEL 9 or OL 9
         arch: x86_64
         supported versions: [7]
-      - name: Ubuntu 22.04
-        arch: x86_64
-        supported versions: [7]
-      - name: Ubuntu 20.04
-        arch: x86_64
-        supported versions: [7]
-      - name: Debian 10
-        arch: x86_64
-        supported versions: [7]
       - name: Debian 11
         arch: x86_64
         supported versions: [7]
-      - name: SLES 12
+      - name: Ubuntu 22.04
         arch: x86_64
         supported versions: [7]
-      - name: SLES 15
+      - name: Ubuntu 20.04
         arch: x86_64
         supported versions: [7]
       - name: RHEL 8
@@ -1024,9 +844,15 @@ products:
       - name: RHEL 9
         arch: ppc64le
         supported versions: [7]
-      - name: SLES 12
-        arch: ppc64le
+      - name: SLES 15
+        arch: x86_64
         supported versions: [7]
       - name: SLES 15
+        arch: ppc64le
+        supported versions: [7]
+      - name: SLES 12
+        arch: x86_64
+        supported versions: [7]
+      - name: SLES 12
         arch: ppc64le
         supported versions: [7]
\ No newline at end of file
diff --git a/install_template/templates/products/edb*plus/centos-7.njk b/install_template/templates/products/edb*plus/centos-7.njk
deleted file mode 100644
index 78e02471bd0..00000000000
--- a/install_template/templates/products/edb*plus/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb*plus/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb*plus/debian-10.njk b/install_template/templates/products/edb*plus/debian-10.njk
deleted file mode 100644
index bb8123cbe22..00000000000
--- a/install_template/templates/products/edb*plus/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb*plus/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb*plus/rhel-7-or-ol-7.njk b/install_template/templates/products/edb*plus/rhel-7-or-ol-7.njk
deleted file mode 100644
index 992aaeb60dc..00000000000
--- a/install_template/templates/products/edb*plus/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb*plus/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb*plus/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb*plus/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index 82805e2699a..00000000000
--- a/install_template/templates/products/edb*plus/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/edb*plus/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/edb*plus/ubuntu-18.04.njk b/install_template/templates/products/edb*plus/ubuntu-18.04.njk
deleted file mode 100644
index 7475de5b8b5..00000000000
--- a/install_template/templates/products/edb*plus/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb*plus/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-jdbc-connector/centos-7.njk b/install_template/templates/products/edb-jdbc-connector/centos-7.njk
deleted file mode 100644
index 5a302d86826..00000000000
--- a/install_template/templates/products/edb-jdbc-connector/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-jdbc-connector/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-jdbc-connector/debian-10.njk b/install_template/templates/products/edb-jdbc-connector/debian-10.njk
deleted file mode 100644
index d5f7157ef7b..00000000000
--- a/install_template/templates/products/edb-jdbc-connector/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-jdbc-connector/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-jdbc-connector/debian-9.njk b/install_template/templates/products/edb-jdbc-connector/debian-9.njk
deleted file mode 100644
index 193de285dc3..00000000000
--- a/install_template/templates/products/edb-jdbc-connector/debian-9.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-jdbc-connector/base.njk" %}
-{% set platformBaseTemplate = "debian-9" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7.njk
deleted file mode 100644
index 545d66585d3..00000000000
--- a/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-jdbc-connector/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-jdbc-connector/sles-12.njk b/install_template/templates/products/edb-jdbc-connector/sles-12.njk
index 83933a02add..efaa4e1ddc3 100644
--- a/install_template/templates/products/edb-jdbc-connector/sles-12.njk
+++ b/install_template/templates/products/edb-jdbc-connector/sles-12.njk
@@ -1,2 +1,2 @@
 {% extends "products/edb-jdbc-connector/sles.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
+{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-ocl-connector/centos-7.njk b/install_template/templates/products/edb-ocl-connector/centos-7.njk
deleted file mode 100644
index 601fb7f317d..00000000000
--- a/install_template/templates/products/edb-ocl-connector/centos-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/edb-ocl-connector/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% set packageDevSuffix %}-devel{% endset %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-ocl-connector/debian-10.njk b/install_template/templates/products/edb-ocl-connector/debian-10.njk
deleted file mode 100644
index 3f601d99e96..00000000000
--- a/install_template/templates/products/edb-ocl-connector/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-ocl-connector/debian.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-ocl-connector/debian-9.njk b/install_template/templates/products/edb-ocl-connector/debian-9.njk
deleted file mode 100644
index ddf34b2b4c0..00000000000
--- a/install_template/templates/products/edb-ocl-connector/debian-9.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-ocl-connector/debian.njk" %}
-{% set platformBaseTemplate = "debian-9" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7.njk
deleted file mode 100644
index 3d9c3b64b09..00000000000
--- a/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/edb-ocl-connector/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% set packageDevSuffix %}-devel{% endset %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-ocl-connector/sles-12_ppc64le.njk b/install_template/templates/products/edb-ocl-connector/sles-12_ppc64le.njk
index 22d04e71525..2b8a57dfbd5 100644
--- a/install_template/templates/products/edb-ocl-connector/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-ocl-connector/sles-12_ppc64le.njk
@@ -1,3 +1,4 @@
 {% extends "products/edb-ocl-connector/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
+
 {% set packageDevSuffix %}-devel{% endset %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/centos-7.njk b/install_template/templates/products/edb-odbc-connector/centos-7.njk
deleted file mode 100644
index 5ce919f3dd8..00000000000
--- a/install_template/templates/products/edb-odbc-connector/centos-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/edb-odbc-connector/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% set packageDevSuffix %}-devel{% endset %}
diff --git a/install_template/templates/products/edb-odbc-connector/debian-10.njk b/install_template/templates/products/edb-odbc-connector/debian-10.njk
deleted file mode 100644
index a743c425dc6..00000000000
--- a/install_template/templates/products/edb-odbc-connector/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-odbc-connector/debian.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/debian-9.njk b/install_template/templates/products/edb-odbc-connector/debian-9.njk
deleted file mode 100644
index aa1b7359224..00000000000
--- a/install_template/templates/products/edb-odbc-connector/debian-9.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-odbc-connector/debian.njk" %}
-{% set platformBaseTemplate = "debian-9" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7.njk
deleted file mode 100644
index 81fe5978f71..00000000000
--- a/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/edb-odbc-connector/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% set packageDevSuffix %}-devel{% endset %}
diff --git a/install_template/templates/products/edb-odbc-connector/sles-12_ppc64le.njk b/install_template/templates/products/edb-odbc-connector/sles-12_ppc64le.njk
index 9bd75c3a33a..c486b577f54 100644
--- a/install_template/templates/products/edb-odbc-connector/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-odbc-connector/sles-12_ppc64le.njk
@@ -1,3 +1,4 @@
 {% extends "products/edb-odbc-connector/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
+
 {% set packageDevSuffix %}-devel{% endset %}
diff --git a/install_template/templates/products/edb-odbc-connector/ubuntu-18.04.njk b/install_template/templates/products/edb-odbc-connector/ubuntu-18.04.njk
deleted file mode 100644
index efc9a2eba6d..00000000000
--- a/install_template/templates/products/edb-odbc-connector/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-odbc-connector/ubuntu.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgbouncer/centos-7.njk b/install_template/templates/products/edb-pgbouncer/centos-7.njk
deleted file mode 100644
index 8442447ef64..00000000000
--- a/install_template/templates/products/edb-pgbouncer/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgbouncer/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgbouncer/debian-10.njk b/install_template/templates/products/edb-pgbouncer/debian-10.njk
deleted file mode 100644
index b08994b1cf5..00000000000
--- a/install_template/templates/products/edb-pgbouncer/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgbouncer/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7.njk
deleted file mode 100644
index 415e2a0a9d0..00000000000
--- a/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgbouncer/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgbouncer/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgbouncer/sles-12_ppc64le.njk
index e58c3610bd1..95cd231e1fb 100644
--- a/install_template/templates/products/edb-pgbouncer/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-pgbouncer/sles-12_ppc64le.njk
@@ -1,2 +1,2 @@
 {% extends "products/edb-pgbouncer/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
diff --git a/install_template/templates/products/edb-pgbouncer/ubuntu-18.04.njk b/install_template/templates/products/edb-pgbouncer/ubuntu-18.04.njk
deleted file mode 100644
index e69aecb2d90..00000000000
--- a/install_template/templates/products/edb-pgbouncer/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgbouncer/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk
deleted file mode 100644
index b8fc8288891..00000000000
--- a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii-extensions/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk b/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk
deleted file mode 100644
index 65626c6f7ff..00000000000
--- a/install_template/templates/products/edb-pgpool-ii-extensions/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii-extensions/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk
deleted file mode 100644
index 1b0bcbe374c..00000000000
--- a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii-extensions/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk
index 1f1d8e42297..f28b5c1fc2f 100644
--- a/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-pgpool-ii-extensions/sles-12_ppc64le.njk
@@ -1,2 +1,2 @@
 {% extends "products/edb-pgpool-ii-extensions/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk
deleted file mode 100644
index d8b89b6123e..00000000000
--- a/install_template/templates/products/edb-pgpool-ii-extensions/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii-extensions/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii/centos-7.njk b/install_template/templates/products/edb-pgpool-ii/centos-7.njk
deleted file mode 100644
index f177dd38d1c..00000000000
--- a/install_template/templates/products/edb-pgpool-ii/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii/debian-10.njk b/install_template/templates/products/edb-pgpool-ii/debian-10.njk
deleted file mode 100644
index 2328f3f5381..00000000000
--- a/install_template/templates/products/edb-pgpool-ii/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii/debian.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk
deleted file mode 100644
index 4ec372bc95c..00000000000
--- a/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk
index 4ac98e225cf..3c3a29224bb 100644
--- a/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-pgpool-ii/sles-12_ppc64le.njk
@@ -1,2 +1,2 @@
 {% extends "products/edb-pgpool-ii/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
diff --git a/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk b/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk
deleted file mode 100644
index e08d9dd850b..00000000000
--- a/install_template/templates/products/edb-pgpool-ii/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-pgpool-ii/ubuntu.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk b/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk
deleted file mode 100644
index b5554bfdafa..00000000000
--- a/install_template/templates/products/edb-postgres-advanced-server/centos-7.njk
+++ /dev/null
@@ -1,6 +0,0 @@
-{% extends "products/edb-postgres-advanced-server/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% block installCommand %}
-{{ super() }}
-{% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk b/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk
deleted file mode 100644
index 76194d7b97d..00000000000
--- a/install_template/templates/products/edb-postgres-advanced-server/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-postgres-advanced-server/debian.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk
deleted file mode 100644
index 49d9eebf2bd..00000000000
--- a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,6 +0,0 @@
-{% extends "products/edb-postgres-advanced-server/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block installCommand %}
-{{ super() }}
-{% include "products/edb-postgres-advanced-server/_centos-rhel-installcommand.njk" %}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7_local.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7_local.njk
deleted file mode 100644
index 2c29868f09c..00000000000
--- a/install_template/templates/products/edb-postgres-advanced-server/rhel-7-or-ol-7_local.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk" %}
-{% set includeLOCAL = true %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-7_ppc64le.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-7_ppc64le.njk
deleted file mode 100644
index ba9c1c86bc2..00000000000
--- a/install_template/templates/products/edb-postgres-advanced-server/rhel-7_ppc64le.njk
+++ /dev/null
@@ -1,5 +0,0 @@
-{% extends "products/edb-postgres-advanced-server/rhel-7-or-ol-7.njk" %}
-
-{% block installCommand %}
-{{ super() }}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk
index ada87aca5d9..9ae56a9eaf8 100644
--- a/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk
+++ b/install_template/templates/products/edb-postgres-advanced-server/sles-12.njk
@@ -10,4 +10,4 @@ To install an individual component:
 sudo {{packageManager}} -n install <package_name>
 ```
 Where `package_name` can be any of the available packages from the [available package list](/epas/{{ product.version }}/installing/linux_install_details/rpm_packages/).
-{% endblock slesoption %}
+{% endblock slesoption %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk b/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk
index d60eb9b7058..b50e82a3b9a 100644
--- a/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk
+++ b/install_template/templates/products/edb-postgres-advanced-server/sles-12_ppc64le.njk
@@ -1 +1,2 @@
 {% extends "products/edb-postgres-advanced-server/sles-12.njk" %}
+
diff --git a/install_template/templates/products/edb-postgres-extended-server/centos-7.njk b/install_template/templates/products/edb-postgres-extended-server/centos-7.njk
deleted file mode 100644
index 2b2e18eba8f..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/centos-7.njk
+++ /dev/null
@@ -1,5 +0,0 @@
-{% extends "products/edb-postgres-extended-server/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% block installCommand %}
-{{ super() }}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-extended-server/debian-10.njk b/install_template/templates/products/edb-postgres-extended-server/debian-10.njk
deleted file mode 100644
index c04bda372b7..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/debian-10.njk
+++ /dev/null
@@ -1,8 +0,0 @@
-{% extends "products/edb-postgres-extended-server/debian.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
-{% set packageName %}edb-postgresextended-<xx>{% endset %}
-{% block installCommand %}
-```shell
-sudo {{ packageManager }} {{ packageManagerNoninteractive }} install {{ packageName }}
-```
-{% endblock installCommand %}
diff --git a/install_template/templates/products/edb-postgres-extended-server/rhel-7-or-ol-7.njk b/install_template/templates/products/edb-postgres-extended-server/rhel-7-or-ol-7.njk
deleted file mode 100644
index 0c79b0b490a..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,5 +0,0 @@
-{% extends "products/edb-postgres-extended-server/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block installCommand %}
-{{ super() }}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-extended-server/rhel-7_ppc64le.njk b/install_template/templates/products/edb-postgres-extended-server/rhel-7_ppc64le.njk
deleted file mode 100644
index 4c5f472ab87..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/rhel-7_ppc64le.njk
+++ /dev/null
@@ -1,6 +0,0 @@
-{% extends "products/edb-postgres-extended-server/rhel-7-or-ol-7.njk" %}
-
-{% set packageName %}edb-postgresextended<xx>{% endset %}
-{% block installCommand %}
-{{ super() }}
-{% endblock installCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-postgres-extended-server/sles-12.njk b/install_template/templates/products/edb-postgres-extended-server/sles-12.njk
deleted file mode 100644
index 4c86e881d3c..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/sles-12.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/edb-postgres-extended-server/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
-{% set packageManager = "zypper" %}
diff --git a/install_template/templates/products/edb-postgres-extended-server/sles-12_ppc64le.njk b/install_template/templates/products/edb-postgres-extended-server/sles-12_ppc64le.njk
deleted file mode 100644
index 8391fdc3fab..00000000000
--- a/install_template/templates/products/edb-postgres-extended-server/sles-12_ppc64le.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/edb-postgres-extended-server/sles-12.njk" %}
-
diff --git a/install_template/templates/products/failover-manager/centos-7.njk b/install_template/templates/products/failover-manager/centos-7.njk
deleted file mode 100644
index b7569bfc129..00000000000
--- a/install_template/templates/products/failover-manager/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/failover-manager/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/failover-manager/debian-10.njk b/install_template/templates/products/failover-manager/debian-10.njk
deleted file mode 100644
index 67711a0d8da..00000000000
--- a/install_template/templates/products/failover-manager/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/failover-manager/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
diff --git a/install_template/templates/products/failover-manager/rhel-7-or-ol-7.njk b/install_template/templates/products/failover-manager/rhel-7-or-ol-7.njk
deleted file mode 100644
index 19d0ff7e1a7..00000000000
--- a/install_template/templates/products/failover-manager/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/failover-manager/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/failover-manager/ubuntu-18.04.njk b/install_template/templates/products/failover-manager/ubuntu-18.04.njk
deleted file mode 100644
index 8c5a8b6f58f..00000000000
--- a/install_template/templates/products/failover-manager/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/failover-manager/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7.njk
deleted file mode 100644
index 1d2ae335746..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7_ppc64le.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7_ppc64le.njk
deleted file mode 100644
index be8eecb2df8..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/centos-7_ppc64le.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/centos-7.njk" %}
-
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/debian-10.njk
deleted file mode 100644
index 5dba7ec69db..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/debian-9.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/debian-9.njk
deleted file mode 100644
index a08d36cc6db..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/debian-9.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "debian-9" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7.njk
deleted file mode 100644
index f82dec09351..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index e428ba91ed9..00000000000
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/hadoop-foreign-data-wrapper/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-20.04.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-20.04.njk
index 3d80e70b108..40019e6ca09 100644
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-20.04.njk
+++ b/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-20.04.njk
@@ -1,2 +1,2 @@
-{% extends "products/hadoop-foreign-data-wrapper/debian-10.njk" %}
+{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
 {% set platformBaseTemplate = "ubuntu-20.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-22.04.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-22.04.njk
index e0c7480bf24..8609c20215a 100644
--- a/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-22.04.njk
+++ b/install_template/templates/products/hadoop-foreign-data-wrapper/ubuntu-22.04.njk
@@ -1,2 +1,2 @@
-{% extends "products/hadoop-foreign-data-wrapper/debian-10.njk" %}
+{% extends "products/hadoop-foreign-data-wrapper/base.njk" %}
 {% set platformBaseTemplate = "ubuntu-22.04" %}
diff --git a/install_template/templates/products/migration-toolkit/centos-7.njk b/install_template/templates/products/migration-toolkit/centos-7.njk
deleted file mode 100644
index dcdf228e846..00000000000
--- a/install_template/templates/products/migration-toolkit/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/migration-toolkit/debian-10.njk b/install_template/templates/products/migration-toolkit/debian-10.njk
deleted file mode 100644
index 33103dcacf5..00000000000
--- a/install_template/templates/products/migration-toolkit/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk b/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk
deleted file mode 100644
index 8797e6d5da5..00000000000
--- a/install_template/templates/products/migration-toolkit/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,9 +0,0 @@
-{% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block prerequisites %}
-- Address other prerequisites:
-  ```shell
-  # Install the EPEL repository:
-  sudo {{ packageManager }} -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-{% endblock prerequisites %}
\ No newline at end of file
diff --git a/install_template/templates/products/migration-toolkit/sles-12.njk b/install_template/templates/products/migration-toolkit/sles-12.njk
index 459e87d293c..10ba722d276 100644
--- a/install_template/templates/products/migration-toolkit/sles-12.njk
+++ b/install_template/templates/products/migration-toolkit/sles-12.njk
@@ -1,2 +1,2 @@
 {% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
+{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
diff --git a/install_template/templates/products/migration-toolkit/sles-12_ppc64le.njk b/install_template/templates/products/migration-toolkit/sles-12_ppc64le.njk
index 36ff2a4651e..459e87d293c 100644
--- a/install_template/templates/products/migration-toolkit/sles-12_ppc64le.njk
+++ b/install_template/templates/products/migration-toolkit/sles-12_ppc64le.njk
@@ -1,3 +1,2 @@
 {% extends "products/migration-toolkit/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
-
diff --git a/install_template/templates/products/migration-toolkit/ubuntu-18.04.njk b/install_template/templates/products/migration-toolkit/ubuntu-18.04.njk
deleted file mode 100644
index 85e63316663..00000000000
--- a/install_template/templates/products/migration-toolkit/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
\ No newline at end of file
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7.njk
deleted file mode 100644
index 89e975e964b..00000000000
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/mongodb-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7_ppc64le.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7_ppc64le.njk
deleted file mode 100644
index c4dcb7f750e..00000000000
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/centos-7_ppc64le.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/mongodb-foreign-data-wrapper/centos-7.njk" %}
-
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/debian-10.njk
deleted file mode 100644
index def4e54863f..00000000000
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/mongodb-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7.njk
deleted file mode 100644
index 68affb9166b..00000000000
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/mongodb-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index 98788a20153..00000000000
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/mongodb-foreign-data-wrapper/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/sles-12_ppc64le.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/sles-12_ppc64le.njk
index 2de68a3f06d..8e1dfe39cb7 100644
--- a/install_template/templates/products/mongodb-foreign-data-wrapper/sles-12_ppc64le.njk
+++ b/install_template/templates/products/mongodb-foreign-data-wrapper/sles-12_ppc64le.njk
@@ -1,2 +1,2 @@
 {% extends "products/mongodb-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk
deleted file mode 100644
index a910a4bd21a..00000000000
--- a/install_template/templates/products/mysql-foreign-data-wrapper/centos-7.njk
+++ /dev/null
@@ -1,17 +0,0 @@
-{% extends "products/mysql-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% block prerequisites %}
-{{ super() }}
-- Download and install the MySQL repo:
-  ```shell
-  sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm
-  ```
-- Enable the MySQL repo:
-  ```shell
-  # For MySQL 8:
-  sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as<xx>-mysql8_fdw
-
-  # For MySQL 5:
-  sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as<xx>-mysql5_fdw
-  ```
-{% endblock prerequisites %}
\ No newline at end of file
diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk b/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk
deleted file mode 100644
index 4462138a26d..00000000000
--- a/install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk
+++ /dev/null
@@ -1,21 +0,0 @@
-{% extends "products/mysql-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
-{% block prerequisites %}
-{{ super() }}
-
-- Download the GPG key to your APT keyring directly using the apt-key utility
-  ```shell
-  sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29
-  ```
-- Install and configure the MySQL repo:
-  ```shell
-  # For MySQL 8:
-  sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee  /etc/apt/sources.list.d/mysql.list
-  
-  # For MySQL 5:
-  sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee  /etc/apt/sources.list.d/mysql.list
-  
-  # Get the most up-to-date package information from the MySQL APT repository:
-  sudo apt-get update
-  ```
-{% endblock prerequisites %}
diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk
deleted file mode 100644
index 99cd1b5c547..00000000000
--- a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,18 +0,0 @@
-{% extends "products/mysql-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block prerequisites %}
-{{ super() }}
-- Download and install the MYSQL repo:
-  ```shell
-  sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm
-  ```
-- Enable the MYSQL repo:
-  ```shell
-  # For MySQL 8:
-  sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as<xx>-mysql8_fdw
-  
-  # For MySQL 5:
-  sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as<xx>-mysql5_fdw
-  ```
-{% endblock prerequisites %}
-  
\ No newline at end of file
diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index 773b89e56ac..00000000000
--- a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/mysql-foreign-data-wrapper/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/postgis/centos-7.njk b/install_template/templates/products/postgis/centos-7.njk
deleted file mode 100644
index 44bf56c2fc8..00000000000
--- a/install_template/templates/products/postgis/centos-7.njk
+++ /dev/null
@@ -1,16 +0,0 @@
-{% extends "products/postgis/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% block installCommand %}
-```shell
-# To install PostGIS 3.4:
-sudo yum -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo yum -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 10-12:
-sudo yum -y install edb-as<xx>-postgis
-```
-{% include "./_epasVersionInPostGISPackageName.njk" %}
-{% endblock installCommand %}
-
diff --git a/install_template/templates/products/postgis/debian-10.njk b/install_template/templates/products/postgis/debian-10.njk
deleted file mode 100644
index 45557b8b464..00000000000
--- a/install_template/templates/products/postgis/debian-10.njk
+++ /dev/null
@@ -1,19 +0,0 @@
-{% extends "products/postgis/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
-{% block installCommand %}
-```shell
-
-# To install PostGIS 3.4 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 12:
-sudo apt-get -y install edb-as12-postgis-3.1
-```
-{% include "./_epasVersionInPostGISPackageName.njk" %}
-{% endblock installCommand %}
-
-
-
diff --git a/install_template/templates/products/postgis/rhel-7-or-ol-7.njk b/install_template/templates/products/postgis/rhel-7-or-ol-7.njk
deleted file mode 100644
index a8abd5c3b50..00000000000
--- a/install_template/templates/products/postgis/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,15 +0,0 @@
-{% extends "products/postgis/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block installCommand %}
-```shell
-# To install PostGIS 3.4:
-sudo yum -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo yum -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 10-11:
-sudo yum -y install edb-as<xx>-postgis
-```
-{% include "./_epasVersionInPostGISPackageName.njk" %}
-{% endblock installCommand %}
diff --git a/install_template/templates/products/postgis/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/postgis/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index eff5b926d4f..00000000000
--- a/install_template/templates/products/postgis/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/postgis/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/postgis/sles-12_ppc64le.njk b/install_template/templates/products/postgis/sles-12_ppc64le.njk
index 08cee10dc4c..55bbd8abe03 100644
--- a/install_template/templates/products/postgis/sles-12_ppc64le.njk
+++ b/install_template/templates/products/postgis/sles-12_ppc64le.njk
@@ -12,4 +12,5 @@ zypper -n install edb-as<xx>-postgis3
 zypper -n install edb-as12-postgis
 ```
 {% include "./_epasVersionInPostGISPackageName.njk" %}
-{% endblock installCommand %}
\ No newline at end of file
+{% endblock installCommand %}
+
diff --git a/install_template/templates/products/postgis/ubuntu-18.04.njk b/install_template/templates/products/postgis/ubuntu-18.04.njk
deleted file mode 100644
index 06682272dab..00000000000
--- a/install_template/templates/products/postgis/ubuntu-18.04.njk
+++ /dev/null
@@ -1,21 +0,0 @@
-{% extends "products/postgis/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
-{% block installCommand %}
-```shell
-# To install PostGIS 3.2 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis32 
-
-# To install PostGIS 3.2 using EDB Postgres Advanced Server 11-12:
-sudo apt-get -y install edb-as<xx>-postgis-3.2
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12:
-sudo apt-get -y install edb-as<xx>-postgis-3.1
-```
-{% include "./_epasVersionInPostGISPackageName.njk" %}
-{% endblock installCommand %}
-
-
-
diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-agent/centos-7.njk
deleted file mode 100644
index d57c53afd4b..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-agent/centos-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/postgres-enterprise-manager-agent/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% block prerequisites %}{% endblock prerequisites %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-agent/debian-10.njk
deleted file mode 100644
index 92928052883..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-agent/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/postgres-enterprise-manager-agent/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7-or-ol-7.njk
deleted file mode 100644
index b7bbabb4179..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/postgres-enterprise-manager-agent/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% block prerequisites %}{% endblock prerequisites %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-agent/sles-12.njk
index c6a595eb237..0e8fe90311a 100644
--- a/install_template/templates/products/postgres-enterprise-manager-agent/sles-12.njk
+++ b/install_template/templates/products/postgres-enterprise-manager-agent/sles-12.njk
@@ -5,4 +5,4 @@
 
     Postgres Enterprise Manager 8.3 and later is supported on SLES.
 
-{% endblock introductory_notes %}
\ No newline at end of file
+{% endblock introductory_notes %}
diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/ubuntu-18.04.njk b/install_template/templates/products/postgres-enterprise-manager-agent/ubuntu-18.04.njk
deleted file mode 100644
index 2df4e55aa52..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-agent/ubuntu-18.04.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/postgres-enterprise-manager-agent/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk
deleted file mode 100644
index da8e815b82d..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk
+++ /dev/null
@@ -1,17 +0,0 @@
-{% extends "products/postgres-enterprise-manager-server/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
-{% set ssutilsName %}sslutils_<x> postgresql<x>-contrib{% endset %}
-{% set ssutilsExtendedName %}edb-postgresextended<x>-contrib{% endset %}
-{% set ssutilsExtendedFirstName %}edb-postgresextended<x>-sslutils{% endset %}
-{% block postinstall %}
-{{ super() }}
-    - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system.
-
-    - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system.
-{% endblock postinstall %}
-{% block prerequisites %}{% endblock prerequisites %}
-{% block firewallCommand %}```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-         
-   firewall-cmd --reload
-   ```{% endblock firewallCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk b/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk
deleted file mode 100644
index d42fc18a4d2..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-server/debian-10.njk
+++ /dev/null
@@ -1,17 +0,0 @@
-{% extends "products/postgres-enterprise-manager-server/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
-{% set upgradeCommand = "update" %}
-{% block repocheck %}
-To determine if your repository exists, enter this command: 
-  
-`apt-cache search enterprisedb`
-{% endblock repocheck %}
-{% block debianUbuntuNote %}!!! Note               
-      Debian 10 changed the requirements for accepting certificates.
-
-      - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it.
-      - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak"{% endblock debianUbuntuNote %}
-{% block firewallDebianCommand %}```shell
-   iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT
-   ```{% endblock firewallDebianCommand %}
-
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk
deleted file mode 100644
index 61f8562e2c9..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,17 +0,0 @@
-{% extends "products/postgres-enterprise-manager-server/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
-{% set ssutilsName %}sslutils_<x> postgresql<x>-contrib{% endset %}
-{% set ssutilsExtendedName %}edb-postgresextended<x>-contrib{% endset %}
-{% set ssutilsExtendedFirstName %}edb-postgresextended<x>-sslutils{% endset %}
-{% block postinstall %}
-{{ super() }}
-    - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system.
-
-    - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system.
-{% endblock postinstall %}
-{% block prerequisites %}{% endblock prerequisites %}
-{% block firewallCommand %}```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-         
-   firewall-cmd --reload
-   ```{% endblock firewallCommand %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk
index 883445754c5..71fc2aa55af 100644
--- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk
+++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12.njk
@@ -8,17 +8,15 @@
 !!! Note
 
     Postgres Enterprise Manager 8.3 and later is supported on SLES.
-    
 {% endblock introductory_notes %}
 {% block repocheck %}
 To determine if your repository exists, enter this command: 
-  
+
 `zypper lr -E | grep enterprisedb`
 {% endblock repocheck %}
 {% block firewallCommand %}```shell
    firewall-cmd --permanent --zone=public --add-port=8443/tcp
-         
+
    firewall-cmd --reload
    ```{% endblock firewallCommand %}
-{% block prerequisites %}{% endblock prerequisites %}
-
+{% block prerequisites %}{% endblock prerequisites %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk
index cf53ae658dc..5a9117b402a 100644
--- a/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk
+++ b/install_template/templates/products/postgres-enterprise-manager-server/sles-12_ppc64le.njk
@@ -4,4 +4,3 @@
 {% set ssutilsName %}sslutils_<x> postgresql<x>-contrib{% endset %}
 {% set ssutilsExtendedName %}edb-postgresextended<x>-contrib{% endset %}
 {% set ssutilsExtendedFirstName %}edb-postgresextended<x>-sslutils{% endset %}
-
diff --git a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-18.04.njk b/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-18.04.njk
deleted file mode 100644
index abb8bb1106c..00000000000
--- a/install_template/templates/products/postgres-enterprise-manager-server/ubuntu-18.04.njk
+++ /dev/null
@@ -1,7 +0,0 @@
-{% extends "products/postgres-enterprise-manager-server/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
-{% block repocheck %}
-To determine if your repository exists, enter this command: 
-  
-`apt-cache search enterprisedb`
-{% endblock repocheck %}
diff --git a/install_template/templates/products/postgresql/centos-7.njk b/install_template/templates/products/postgresql/centos-7.njk
deleted file mode 100644
index 66554f5ef74..00000000000
--- a/install_template/templates/products/postgresql/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/postgresql/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/postgresql/debian-10.njk b/install_template/templates/products/postgresql/debian-10.njk
deleted file mode 100644
index cca403fbe70..00000000000
--- a/install_template/templates/products/postgresql/debian-10.njk
+++ /dev/null
@@ -1,3 +0,0 @@
-{% extends "products/postgresql/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
-{% set packageName %}postgresql-<xx>{% endset %}
diff --git a/install_template/templates/products/postgresql/rhel-7-or-ol-7.njk b/install_template/templates/products/postgresql/rhel-7-or-ol-7.njk
deleted file mode 100644
index 0d90be5cc3a..00000000000
--- a/install_template/templates/products/postgresql/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/postgresql/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
diff --git a/install_template/templates/products/postgresql/sles-12.njk b/install_template/templates/products/postgresql/sles-12.njk
index e4c1b87cc47..926e06bad28 100644
--- a/install_template/templates/products/postgresql/sles-12.njk
+++ b/install_template/templates/products/postgresql/sles-12.njk
@@ -1,3 +1,4 @@
 {% extends "products/postgresql/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
 {% set packageName %}postgresql<xx>-server{% endset %}
+
diff --git a/install_template/templates/products/postgresql/sles-12_ppc64le.njk b/install_template/templates/products/postgresql/sles-12_ppc64le.njk
index 926e06bad28..e4c1b87cc47 100644
--- a/install_template/templates/products/postgresql/sles-12_ppc64le.njk
+++ b/install_template/templates/products/postgresql/sles-12_ppc64le.njk
@@ -1,4 +1,3 @@
 {% extends "products/postgresql/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
 {% set packageName %}postgresql<xx>-server{% endset %}
-
diff --git a/install_template/templates/products/replication-server/centos-7.njk b/install_template/templates/products/replication-server/centos-7.njk
deleted file mode 100644
index 643abd8ea9f..00000000000
--- a/install_template/templates/products/replication-server/centos-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/replication-server/base.njk" %}
-{% set platformBaseTemplate = "centos-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/replication-server/centos-7_ppc64le.njk b/install_template/templates/products/replication-server/centos-7_ppc64le.njk
deleted file mode 100644
index 40e2fb89ed7..00000000000
--- a/install_template/templates/products/replication-server/centos-7_ppc64le.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/replication-server/centos-7.njk" %}
-
diff --git a/install_template/templates/products/replication-server/debian-10.njk b/install_template/templates/products/replication-server/debian-10.njk
deleted file mode 100644
index 90abb59daa4..00000000000
--- a/install_template/templates/products/replication-server/debian-10.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/replication-server/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
\ No newline at end of file
diff --git a/install_template/templates/products/replication-server/debian-9.njk b/install_template/templates/products/replication-server/debian-9.njk
deleted file mode 100644
index 380ae26a7bf..00000000000
--- a/install_template/templates/products/replication-server/debian-9.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/replication-server/base.njk" %}
-{% set platformBaseTemplate = "debian-9" %}
\ No newline at end of file
diff --git a/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk b/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk
deleted file mode 100644
index e24ab1bfe1c..00000000000
--- a/install_template/templates/products/replication-server/rhel-7-or-ol-7.njk
+++ /dev/null
@@ -1,2 +0,0 @@
-{% extends "products/replication-server/base.njk" %}
-{% set platformBaseTemplate = "rhel-7-or-ol-7" %}
\ No newline at end of file
diff --git a/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk
deleted file mode 100644
index 55e1a7b606c..00000000000
--- a/install_template/templates/products/replication-server/rhel-7-or-ol-7_ppc64le.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/replication-server/rhel-7-or-ol-7.njk" %}
diff --git a/install_template/templates/products/replication-server/sles-12_ppc64le.njk b/install_template/templates/products/replication-server/sles-12_ppc64le.njk
index 18823a2b02e..0670561dee0 100644
--- a/install_template/templates/products/replication-server/sles-12_ppc64le.njk
+++ b/install_template/templates/products/replication-server/sles-12_ppc64le.njk
@@ -1,2 +1,2 @@
 {% extends "products/replication-server/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
diff --git a/install_template/templates/products/replication-server/ubuntu-18.04.njk b/install_template/templates/products/replication-server/ubuntu-18.04.njk
deleted file mode 100644
index e77281fa687..00000000000
--- a/install_template/templates/products/replication-server/ubuntu-18.04.njk
+++ /dev/null
@@ -1 +0,0 @@
-{% extends "products/replication-server/debian-10.njk" %}
diff --git a/install_template/templates/products/replication-server/ubuntu-20.04.njk b/install_template/templates/products/replication-server/ubuntu-20.04.njk
index e77281fa687..286fce48535 100644
--- a/install_template/templates/products/replication-server/ubuntu-20.04.njk
+++ b/install_template/templates/products/replication-server/ubuntu-20.04.njk
@@ -1 +1,2 @@
-{% extends "products/replication-server/debian-10.njk" %}
+{% extends "products/replication-server/base.njk" %}
+{% set platformBaseTemplate = "ubuntu-20.04" %}
\ No newline at end of file
diff --git a/product_docs/docs/edb_plus/41/installing/configuring_linux_installation.mdx b/product_docs/docs/edb_plus/41/installing/configuring_linux_installation.mdx
index 7a722b13e15..4f9e49b1d8c 100644
--- a/product_docs/docs/edb_plus/41/installing/configuring_linux_installation.mdx
+++ b/product_docs/docs/edb_plus/41/installing/configuring_linux_installation.mdx
@@ -9,19 +9,13 @@ By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authen
 - Modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server.
 - Ensure that an `IDENT` server is accessible. 
 
-To ensure an `IDENT` server is accessible, you must confirm that an `identd` server is installed and running. You can use the `yum` package manager to install an `identd` server.
+To ensure an `IDENT` server is accessible, you must confirm that an `identd` server is installed and running. You can use the package manager to install an `identd` server.
 
--   On RHEL or CentOS 7:
+On RHEL/Rocky Linux/AlmaLinux 8:
 
-    ```text
-    yum -y install xinetd authd
-    ```
-
--   On RHEL/Rocky Linux/AlmaLinux 8:
-
-    ```text
-    dnf -y install xinetd authd
-    ```
+```text
+dnf -y install xinetd authd
+```
 
 The command creates a file named `/etc/xinetd.d/auth` that contains:
 
diff --git a/product_docs/docs/edb_plus/41/installing/index.mdx b/product_docs/docs/edb_plus/41/installing/index.mdx
index 9d96d478cb6..deb8850616d 100644
--- a/product_docs/docs/edb_plus/41/installing/index.mdx
+++ b/product_docs/docs/edb_plus/41/installing/index.mdx
@@ -23,25 +23,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/edbplus_rhel_9), [RHEL 8](linux_x86_64/edbplus_rhel_8), [RHEL 7](linux_x86_64/edbplus_rhel_7)
+- [RHEL 9](linux_x86_64/edbplus_rhel_9), [RHEL 8](linux_x86_64/edbplus_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/edbplus_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/edbplus_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/edbplus_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/edbplus_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/edbplus_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/edbplus_other_linux_9), [Rocky Linux 8](linux_x86_64/edbplus_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/edbplus_other_linux_9), [AlmaLinux 8](linux_x86_64/edbplus_other_linux_8)
 
-- [CentOS 7](linux_x86_64/edbplus_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/edbplus_sles_15), [SLES 12](linux_x86_64/edbplus_sles_12)
+- [SLES 15](linux_x86_64/edbplus_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/edbplus_ubuntu_22), [Ubuntu 20.04](linux_x86_64/edbplus_ubuntu_20)
 
-- [Debian 11](linux_x86_64/edbplus_debian_11), [Debian 10](linux_x86_64/edbplus_debian_10)
+- [Debian 11](linux_x86_64/edbplus_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -51,7 +49,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/edbplus_sles_15), [SLES 12](linux_ppc64le/edbplus_sles_12)
+- [SLES 15](linux_ppc64le/edbplus_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx
deleted file mode 100644
index 4a338d3d211..00000000000
--- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/edbplus_sles_12.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB*Plus on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /edb_plus/41/03_installing_edb_plus/install_on_linux/ibm_power_ppc64le/edbplus_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-edbplus
-```
-
-## Initial configuration
-
-After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation:
-
-```shell
-export JAVA_HOME=<path_to_java>
-export PATH=<path_to_java>/bin:$PATH
-```
diff --git a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx
index ba38eb86c08..545fa7b28dd 100644
--- a/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/edb_plus/41/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - edbplus_rhel_9
   - edbplus_rhel_8
   - edbplus_sles_15
-  - edbplus_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](edbplus_sles_15)
-
-- [SLES 12](edbplus_sles_12)
diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx
deleted file mode 100644
index 4bf252bf5c9..00000000000
--- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_centos_7.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB*Plus on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /edb_plus/41/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-edbplus
-```
-
-## Initial configuration
-
-After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation:
-
-```shell
-export JAVA_HOME=<path_to_java>
-export PATH=<path_to_java>/bin:$PATH
-```
diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx
deleted file mode 100644
index 135192ba01a..00000000000
--- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_debian_10.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB*Plus on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /edb_plus/41/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-edbplus
-```
-
-## Initial configuration
-
-After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation:
-
-```shell
-export JAVA_HOME=<path_to_java>
-export PATH=<path_to_java>/bin:$PATH
-```
diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx
deleted file mode 100644
index 3064b11ce87..00000000000
--- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_rhel_7.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB*Plus on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /edb_plus/41/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-edbplus
-```
-
-## Initial configuration
-
-After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation:
-
-```shell
-export JAVA_HOME=<path_to_java>
-export PATH=<path_to_java>/bin:$PATH
-```
diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx
deleted file mode 100644
index c3ebe2bc609..00000000000
--- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/edbplus_sles_12.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB*Plus on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /edb_plus/41/03_installing_edb_plus/install_on_linux/x86_amd64/edbplus_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-edbplus
-```
-
-## Initial configuration
-
-After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation:
-
-```shell
-export JAVA_HOME=<path_to_java>
-export PATH=<path_to_java>/bin:$PATH
-```
diff --git a/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx b/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx
index 78de80f9d3d..03e4117697d 100644
--- a/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/edb_plus/41/installing/linux_x86_64/index.mdx
@@ -12,16 +12,12 @@ redirects:
 navigation:
   - edbplus_rhel_9
   - edbplus_rhel_8
-  - edbplus_rhel_7
   - edbplus_other_linux_9
   - edbplus_other_linux_8
-  - edbplus_centos_7
   - edbplus_sles_15
-  - edbplus_sles_12
   - edbplus_ubuntu_22
   - edbplus_ubuntu_20
   - edbplus_debian_11
-  - edbplus_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -32,14 +28,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](edbplus_rhel_8)
 
-- [RHEL 7](edbplus_rhel_7)
-
 - [Oracle Linux (OL) 9](edbplus_rhel_9)
 
 - [Oracle Linux (OL) 8](edbplus_rhel_8)
 
-- [Oracle Linux (OL) 7](edbplus_rhel_7)
-
 - [Rocky Linux 9](edbplus_other_linux_9)
 
 - [Rocky Linux 8](edbplus_other_linux_8)
@@ -48,14 +40,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](edbplus_other_linux_8)
 
-- [CentOS 7](edbplus_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](edbplus_sles_15)
 
-- [SLES 12](edbplus_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](edbplus_ubuntu_22)
@@ -63,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](edbplus_ubuntu_20)
 
 - [Debian 11](edbplus_debian_11)
-
-- [Debian 10](edbplus_debian_10)
diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx
index a2e7ba1d577..798cea4f71d 100644
--- a/product_docs/docs/efm/4/05_using_efm.mdx
+++ b/product_docs/docs/efm/4/05_using_efm.mdx
@@ -35,7 +35,7 @@ By default, [some of the efm commands](07_using_efm_utility/#using_efm_utility)
 
 You can start the nodes of a Failover Manager cluster in any order.
 
-To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges, and invoke the command:
+To start the Failover Manager cluster on RHEL/Rocky Linux/AlmaLinux 8.x or later, assume superuser privileges, and invoke the command:
 
 `systemctl start edb-efm-4.<x>`
 
@@ -69,7 +69,7 @@ You can add a node to a Failover Manager cluster at any time. When you add a nod
 
 2.  Configure the cluster members file on the new node, adding an entry for the membership coordinator. For more information about modifying the cluster members file, see [The cluster members file](04_configuring_efm/03_cluster_members/#cluster_members).
 
-3.  Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, invoke the command:
+3.  Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/Rocky Linux/AlmaLinux 8.x or later, invoke the command:
 
     `systemctl start edb-efm-4.<x>`
 
@@ -165,7 +165,7 @@ For more information about the efm utility, see [Using the efm utility](07_using
 
 When you stop an agent, Failover Manager removes the node's address from the cluster members list on all of the running nodes of the cluster but doesn't remove the address from the Failover Manager Allowed node host list.
 
-To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges and invoke the command:
+To stop the Failover Manager agent on RHEL/Rocky Linux/AlmaLinux 8.x or later, assume superuser privileges and invoke the command:
 
 `systemctl stop edb-efm-4.<x>`
 
@@ -204,7 +204,7 @@ You can monitor multiple database clusters that reside on the same host by runni
 
 1.  Create a cluster properties file for each member of each cluster that defines a unique set of properties and the role of the node within the cluster.
 2.  Create a cluster members file for each member of each cluster that lists the members of the cluster.
-3.  Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files.
+3.  Customize the unit file (on a RHEL/Rocky Linux/AlmaLinux 8.x or later system) for each cluster to specify the names of the cluster properties and the cluster members files.
 4.  Start the services for each cluster.
 
 These examples use two database clusters (acctg and sales) running on the same node:
@@ -262,14 +262,14 @@ Use the following parameters when assigning the virtual IP address to a node. If
 
 This parameter value is determined by the virtual IP addresses being used and can be the same for both `acctg.properties` and `sales.properties`.
 
-After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x](#rhelcentos-7x-or-rhelrocky-linuxalmalinux-8x).
+After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/Rocky Linux/AlmaLinux 8.x or later, see [RHEL/Rocky Linux/AlmaLinux 8.x or later](#rhelrocky-linuxalmalinux-8x-or-later).
 
 !!! Note
     If you're using a unit file, manually update the file to reflect the new service name when you upgrade Failover Manager.
 
-### RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### RHEL/Rocky Linux/AlmaLinux 8.x or later
 
-If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the service file `/usr/lib/systemd/system/edb-efm-4.<x>.service` to `/etc/systemd/system` with a new name that's unique for each cluster.
+If you're using RHEL/Rocky Linux/AlmaLinux 8.x or later, copy the service file `/usr/lib/systemd/system/edb-efm-4.<x>.service` to `/etc/systemd/system` with a new name that's unique for each cluster.
 
 For example, if you have two clusters named `acctg` and `sales` managed by Failover Manager 4.9, the unit file names might be `efm-acctg.service` and `efm-sales.service`. You can create them with:
 
diff --git a/product_docs/docs/efm/4/08_controlling_efm_service.mdx b/product_docs/docs/efm/4/08_controlling_efm_service.mdx
index 479f26fb5f1..892a46b60a6 100644
--- a/product_docs/docs/efm/4/08_controlling_efm_service.mdx
+++ b/product_docs/docs/efm/4/08_controlling_efm_service.mdx
@@ -21,11 +21,11 @@ The commands that control the Failover Manager service are platform specific.
 
 <div id="service_utility" class="registered_link"></div>
 
-## Using the systemctl utility on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x
+## Using the systemctl utility on RHEL/Rocky Linux/AlmaLinux 8.x or later
 
-On RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-4.<x>.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster.
+On RHEL/Rocky Linux/AlmaLinux 8.x or later, Failover Manager runs as a Linux service named (by default) `edb-efm-4.<x>.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster.
 
-Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x host:
+Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/Rocky Linux/AlmaLinux 8.x or later host:
 
 `systemctl start edb-efm-4.<x>`
 
diff --git a/product_docs/docs/efm/4/installing/index.mdx b/product_docs/docs/efm/4/installing/index.mdx
index 1dc1d847201..8cac86cdc53 100644
--- a/product_docs/docs/efm/4/installing/index.mdx
+++ b/product_docs/docs/efm/4/installing/index.mdx
@@ -42,25 +42,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/efm_rhel_9), [RHEL 8](linux_x86_64/efm_rhel_8), [RHEL 7](linux_x86_64/efm_rhel_7)
+- [RHEL 9](linux_x86_64/efm_rhel_9), [RHEL 8](linux_x86_64/efm_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/efm_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/efm_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/efm_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/efm_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/efm_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/efm_other_linux_9), [Rocky Linux 8](linux_x86_64/efm_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/efm_other_linux_9), [AlmaLinux 8](linux_x86_64/efm_other_linux_8)
 
-- [CentOS 7](linux_x86_64/efm_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/efm_sles_15), [SLES 12](linux_x86_64/efm_sles_12)
+- [SLES 15](linux_x86_64/efm_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/efm_ubuntu_22), [Ubuntu 20.04](linux_x86_64/efm_ubuntu_20)
 
-- [Debian 12](linux_x86_64/efm_debian_12), [Debian 11](linux_x86_64/efm_debian_11), [Debian 10](linux_x86_64/efm_debian_10)
+- [Debian 12](linux_x86_64/efm_debian_12), [Debian 11](linux_x86_64/efm_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -70,7 +68,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/efm_sles_15), [SLES 12](linux_ppc64le/efm_sles_12)
+- [SLES 15](linux_ppc64le/efm_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx
deleted file mode 100644
index 1ea1fe83fcf..00000000000
--- a/product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Failover Manager on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /efm/4/03_installing_efm/ibm_power_ppc64le/efm_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host (not needed for witness nodes).
-
-  - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - See [PostgreSQL Downloads](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-efm<4x>
-```
-
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.9, the package name is `edb-efm49`.
-
-The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.
-
-## Initial configuration
-
-If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions).
-
-After installing on each node of the cluster:
-
-1.  Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node.
-2.  Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node.
-3.  If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file.
-4.  Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/).
diff --git a/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx b/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx
index 1a3c7093259..8ca1dee17db 100644
--- a/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/efm/4/installing/linux_ppc64le/index.mdx
@@ -14,7 +14,6 @@ navigation:
   - efm_rhel_9
   - efm_rhel_8
   - efm_sles_15
-  - efm_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,5 +27,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](efm_sles_15)
-
-- [SLES 12](efm_sles_12)
diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx
deleted file mode 100644
index 691b286ce38..00000000000
--- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_centos_7.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Failover Manager on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /efm/4/03_installing_efm/x86_amd64/efm_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host (not needed for witness nodes).
-
-  - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - See [PostgreSQL Downloads](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-efm<4x>
-```
-
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.9, the package name is `edb-efm49`.
-
-The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.
-
-## Initial configuration
-
-If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions).
-
-After installing on each node of the cluster:
-
-1.  Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node.
-2.  Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node.
-3.  If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file.
-4.  Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/).
diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx
deleted file mode 100644
index 5d7e60ccf39..00000000000
--- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_debian_10.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Failover Manager on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /efm/4/03_installing_efm/x86_amd64/efm_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host (not needed for witness nodes).
-
-  - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - See [PostgreSQL Downloads](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-efm<4x>
-```
-
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.9, the package name is `edb-efm49`.
-
-The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.
-
-## Initial configuration
-
-If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions).
-
-After installing on each node of the cluster:
-
-1.  Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node.
-2.  Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node.
-3.  If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file.
-4.  Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/).
diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx
deleted file mode 100644
index 6a20e227811..00000000000
--- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_rhel_7.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Failover Manager on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /efm/4/03_installing_efm/x86_amd64/efm_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host (not needed for witness nodes).
-
-  - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - See [PostgreSQL Downloads](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-efm<4x>
-```
-
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.9, the package name is `edb-efm49`.
-
-The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.
-
-## Initial configuration
-
-If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions).
-
-After installing on each node of the cluster:
-
-1.  Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node.
-2.  Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node.
-3.  If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file.
-4.  Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/).
diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx
deleted file mode 100644
index f1b2c92dd5c..00000000000
--- a/product_docs/docs/efm/4/installing/linux_x86_64/efm_sles_12.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Failover Manager on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /efm/4/03_installing_efm/x86_amd64/efm_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host (not needed for witness nodes).
-
-  - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - See [PostgreSQL Downloads](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-efm<4x>
-```
-
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.9, the package name is `edb-efm49`.
-
-The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.
-
-## Initial configuration
-
-If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions).
-
-After installing on each node of the cluster:
-
-1.  Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node.
-2.  Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node.
-3.  If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file.
-4.  Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/).
diff --git a/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx b/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx
index 0d7d9a4382c..7b6fd49d27a 100644
--- a/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/efm/4/installing/linux_x86_64/index.mdx
@@ -13,17 +13,13 @@ redirects:
 navigation:
   - efm_rhel_9
   - efm_rhel_8
-  - efm_rhel_7
   - efm_other_linux_9
   - efm_other_linux_8
-  - efm_centos_7
   - efm_sles_15
-  - efm_sles_12
   - efm_ubuntu_22
   - efm_ubuntu_20
   - efm_debian_12
   - efm_debian_11
-  - efm_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](efm_rhel_8)
 
-- [RHEL 7](efm_rhel_7)
-
 - [Oracle Linux (OL) 9](efm_rhel_9)
 
 - [Oracle Linux (OL) 8](efm_rhel_8)
 
-- [Oracle Linux (OL) 7](efm_rhel_7)
-
 - [Rocky Linux 9](efm_other_linux_9)
 
 - [Rocky Linux 8](efm_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](efm_other_linux_8)
 
-- [CentOS 7](efm_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](efm_sles_15)
 
-- [SLES 12](efm_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](efm_ubuntu_22)
@@ -67,5 +55,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](efm_debian_12)
 
 - [Debian 11](efm_debian_11)
-
-- [Debian 10](efm_debian_10)
diff --git a/product_docs/docs/efm/4/upgrading.mdx b/product_docs/docs/efm/4/upgrading.mdx
index f890e574564..e714e565b2f 100644
--- a/product_docs/docs/efm/4/upgrading.mdx
+++ b/product_docs/docs/efm/4/upgrading.mdx
@@ -75,13 +75,7 @@ Summary:
 
 After upgrading to Failover Manager 4.9, you can use your native package manager to remove previous installations of Failover Manager. For example, use the following command to remove Failover Manager 4.8 and any unneeded dependencies:
 
--   On RHEL or CentOS 7.x:
-
-```shell
-yum remove edb-efm48
-```
-
--   On RHEL or Rocky Linux or AlmaLinux 8.x:
+-   On RHEL/Rocky Linux/AlmaLinux 8.x or later:
 
 ```shell
 dnf remove edb-efm48
diff --git a/product_docs/docs/epas/11/epas_limitations/index.mdx b/product_docs/docs/epas/11/epas_limitations/index.mdx
index 419ad102f93..5c6becf758a 100644
--- a/product_docs/docs/epas/11/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/11/epas_limitations/index.mdx
@@ -5,4 +5,4 @@ title: Limitations
 The following limitations apply:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported on RHEL or CentOS x86 only. 
+-   The LLVM JIT package is supported on RHEL x86 only. 
diff --git a/product_docs/docs/epas/11/installing/index.mdx b/product_docs/docs/epas/11/installing/index.mdx
index 8600a99f210..7a87927f339 100644
--- a/product_docs/docs/epas/11/installing/index.mdx
+++ b/product_docs/docs/epas/11/installing/index.mdx
@@ -26,35 +26,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx
index 7a657f60ef5..67babb99d96 100644
--- a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx
@@ -7,10 +7,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu Locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table below:
 
diff --git a/product_docs/docs/epas/11/installing/linux_install_details/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/11/installing/linux_install_details/managing_an_advanced_server_installation.mdx
index e51af196c85..bc2c8af388d 100644
--- a/product_docs/docs/epas/11/installing/linux_install_details/managing_an_advanced_server_installation.mdx
+++ b/product_docs/docs/epas/11/installing/linux_install_details/managing_an_advanced_server_installation.mdx
@@ -33,9 +33,9 @@ The following table lists the names of the services that control Advanced Server
 
 You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific.
 
-### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Controlling a Service on RHEL/Rocky Linux/AlmaLinux 8.x
 
-If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
+If your installation of Advanced Server resides on RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter:
 
@@ -112,9 +112,8 @@ You can use the `pg_ctl` utility to control an Advanced Server service from the
 -   `reload` sends the server a `SIGHUP` signal, reloading configuration parameters
 -   `status` to discover the current status of the service.
 
-For more information about using the `pg_ctl` utility, or the command line options available, see the official PostgreSQL Core Documentation available at:
+For more information about using the `pg_ctl` utility or the command-line options available, see the official [PostgreSQL Core Documentation available](https://www.postgresql.org/docs/11/static/app-pg-ctl.html).
 
-<https://www.postgresql.org/docs/11/static/app-pg-ctl.html>
 
 **Choosing Between pg_ctl and the service Command**
 
@@ -148,30 +147,28 @@ Where:
 
 `-U` specifies the identity of the database user that will be used for the session.
 
-For more information about using the command line client, see the PostgreSQL Core Documentation at:
+For more information about using the command line client, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/11/static/app-psql.html).
 
-<https://www.postgresql.org/docs/11/static/app-psql.html>
 
 ## Configuring a Package Installation
 
-The packages that install the database server component create a unit file (on version 7.x or 8.x hosts) and service startup scripts.
+The packages that install the database server component create a unit file (on 8.x hosts) and service startup scripts.
 
 ### Creating a Database Cluster and Starting the Service
 
 The PostgreSQL `initdb` command creates a database cluster. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the `systemd` service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
-To review the `initdb` documentation, visit:
+For more information, see the [initdb documentation](https://www.postgresql.org/docs/11/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/11/static/app-initdb.html>
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -310,9 +307,9 @@ You can also view online help for `initdb` by assuming superuser privileges and
 Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file.
 
 
-### Modifying the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Modifying the Data Directory Location on RHEL/Rocky Linux/AlmaLinux 8.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
 
 By default, data files reside under `/var/lib/edb/as11/data` directory. To use a data directory that resides in a non-default location, perform the following steps:
 
@@ -340,9 +337,9 @@ By default, data files reside under `/var/lib/edb/as11/data` directory. To use a
 
 You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-The `edb-as11-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
+The `edb-as11-server-core` RPM for version 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
 
 The example that follows creates an Advanced Server installation with two instances; the secondary instance is named `secondary`:
 
@@ -382,15 +379,7 @@ You can create a local repository to act as a host for the Advanced Server RPM p
 
 To create and use a local repository, you must:
 
--   Use `yum` or `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
-
-    On RHEL or CentOS 7.x:
-
-    ```bash
-    yum install epel-release
-    yum install yum-utils
-    yum install createrepo
-    ```
+-   Use `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
 
     On RHEL or Rocky Linux/AlmaLinux 8.x:
 
@@ -427,20 +416,9 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use `yum` or `dnf` commands to install Advanced Server and its supporting components on the isolated servers. For example:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum -y install edb-as11-server
-    ```
-
--   On RHEL or Rocky Linux/AlmaLinux 8:
+After specifying the location and connection information for your local repository, you can use `dnf` to install Advanced Server and its supporting components on the isolated servers. For example:
 
-    ```text
-    dnf -y install edb-as11-server
-    ```
-
-For more information about creating a local `yum` repository, visit:
+```text
+dnf -y install edb-as11-server
+```
 
-<https://wiki.centos.org/HowTos/CreateLocalRepos>
\ No newline at end of file
diff --git a/product_docs/docs/epas/11/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/11/installing/linux_install_details/rpm_packages.mdx
index c3e3d5125e2..23dfa6300a6 100644
--- a/product_docs/docs/epas/11/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/11/installing/linux_install_details/rpm_packages.mdx
@@ -7,21 +7,15 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu Packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages
+## RHEL/Rocky Linux/AlmaLinux/SLES Packages
 
 ### EDB Postgres Advanced Server RPM packages
 
 The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
 
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
-
 On RHEL or Rocky Linux or AlmaLinux 8:
 
 ```text
@@ -167,41 +161,25 @@ apt list edb*
 | edb-efm40                        | This package installs EDB Failover Manager that adds fault tolerance to database clusters to minimize downtime when a primary database fails by keeping data online in high availability configurations.                                                                                                                                                                                                                                                                                                                                                                                                                                |
 
 
-### Updating an RPM installation
-
-If you have an existing EDB Postgres Advanced Server RPM installation, you can use `yum` or `dnf` to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb-repo
-    ```
+### Updating RPM installations
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
+If you have an existing EDB Postgres Advanced Server RPM installation, you can use `dnf` to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
 
     ```text
     dnf upgrade edb-repo
     ```
 
-`yum` or `dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `yum` or `dnf` to upgrade all packages whose names include the expression `edb`:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
+`dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `yum` or `dnf` to upgrade all packages whose names include the expression `edb`:
 
     ```text
     dnf upgrade edb*
     ```
 
 !!! Note
-    The `yum upgrade` or `dnf upgrade` command perform an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
+    The `dnf upgrade` command performs an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
 
 For more information about using yum commands and options, enter `yum --help` on your command line.
 
 For more information about using `dnf` commands and options, visit:
 
-<https://docs.fedoraproject.org/en-US/quick-docs/dnf/>
\ No newline at end of file
+<https://docs.fedoraproject.org/en-US/quick-docs/dnf/>
diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index 075922a0300..00000000000
--- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb
-
-sudo systemctl start edb-as-11
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index 09b008e8882..00000000000
--- a/product_docs/docs/epas/11/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb
-
-sudo systemctl start edb-as-11
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx
index 1ae890d5109..908bb54c932 100644
--- a/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/11/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index a061300849f..00000000000
--- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb
-
-sudo systemctl start edb-as-11
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index 266524c6b26..00000000000
--- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index 14e4671b6b0..00000000000
--- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 11, the package name is `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as11`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb
-
-sudo systemctl start edb-as-11
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index fe09c100fd5..00000000000
--- a/product_docs/docs/epas/11/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/11/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 11, the package name would be `edb-as11-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/11/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-11-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as11/bin/edb-as-11-setup initdb
-
-sudo systemctl start edb-as-11
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (11.0.0, server 11.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx
index f8990722b3e..078e9a0060a 100644
--- a/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/11/installing/linux_x86_64/index.mdx
@@ -14,16 +14,12 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -65,5 +53,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](epas_ubuntu_20)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/11/troubleshooting/linux_troubleshooting.mdx b/product_docs/docs/epas/11/troubleshooting/linux_troubleshooting.mdx
index ed6677420a8..cff55c6df2c 100644
--- a/product_docs/docs/epas/11/troubleshooting/linux_troubleshooting.mdx
+++ b/product_docs/docs/epas/11/troubleshooting/linux_troubleshooting.mdx
@@ -12,9 +12,8 @@ legacyRedirectsGenerated:
 
 **Difficulty Displaying Java-based Applications**
 
-If you encounter difficulty displaying Java-based server features (controls or text not being displayed correctly, or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit the following link for other possible work-arounds:
+If you encounter difficulty displaying Java-based server features (controls or text not displayed correctly or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit this [link](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373) for other possible workarounds.
 
-<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373>
 
 **The Installation Fails to Complete Due to Existing data Directory Contents**
 
@@ -26,11 +25,9 @@ If you encounter a similar message, you should confirm that the data directory i
 
 **Difficulty Installing the EPEL Release Package**
 
-If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x:
+If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x:
 
 ```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 ```
 
@@ -44,7 +41,5 @@ Error: Nothing to do
 If you receive this error, you can download the `EPEL` rpm package, and install it manually. To manually install `EPEL`, download the rpm package, assume superuser privileges, navigate into the directory that contains the package, and install `EPEL` with the command:
 
 ```text
-yum -y install epel-release
-
 dnf -y install epel-release
 ```
diff --git a/product_docs/docs/epas/11/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/11/uninstalling/linux_uninstall.mdx
index bbce93ea8a7..af3abd8735f 100644
--- a/product_docs/docs/epas/11/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/11/uninstalling/linux_uninstall.mdx
@@ -15,9 +15,9 @@ legacyRedirectsGenerated:
 
 Note that after uninstalling Advanced Server, the cluster data files remain intact and the service user persists. You may manually remove the cluster `data` and service user from the system.
 
-## Uninstalling on RHEL/OL/AlmaLinux/Rocky Linux
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
 
-You can use variations of the `rpm, yum` or `dnf` command to remove installed packages. Note that removing a package does not damage the Advanced Server `data` directory.
+You can use variations of the `rpm` or `dnf` command to remove installed packages. Note that removing a package does not damage the Advanced Server `data` directory.
 
 Include the `-e` option when invoking the `rpm` command to remove an installed package; the command syntax is:
 
@@ -27,40 +27,24 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you would like to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
+You can use the `dnf remove` command to remove a package installed by `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove <package_name>
-    ```
+```text
+dnf remove <package_name>
+```
 
 Where `package_name` is the name of the package that you would like to remove.
 
-`yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning.
+`rpm` doesn't remove a package that another package requires. If you attempt to remove a package that satisfies a package dependency, `rpm` provides a warning.
 
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
 To uninstall Advanced Server and its dependent packages; use the following command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove edb-as11-server*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove edb-as11-server*
-    ```
+```text
+dnf remove edb-as11-server*
+```
 
 ## Uninstalling on Debian or Ubuntu
 
diff --git a/product_docs/docs/epas/12/epas_limitations/index.mdx b/product_docs/docs/epas/12/epas_limitations/index.mdx
index 419ad102f93..5c6becf758a 100644
--- a/product_docs/docs/epas/12/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/12/epas_limitations/index.mdx
@@ -5,4 +5,4 @@ title: Limitations
 The following limitations apply:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported on RHEL or CentOS x86 only. 
+-   The LLVM JIT package is supported on RHEL x86 only. 
diff --git a/product_docs/docs/epas/12/installing/index.mdx b/product_docs/docs/epas/12/installing/index.mdx
index b5ba523ec42..ebd230fc881 100644
--- a/product_docs/docs/epas/12/installing/index.mdx
+++ b/product_docs/docs/epas/12/installing/index.mdx
@@ -26,35 +26,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx
index a3a535bbaa4..c041e365d97 100644
--- a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx
@@ -7,10 +7,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu Locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table below:
 
diff --git a/product_docs/docs/epas/12/installing/linux_install_details/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/12/installing/linux_install_details/managing_an_advanced_server_installation.mdx
index 9c33c57c381..5886dbd9b6d 100644
--- a/product_docs/docs/epas/12/installing/linux_install_details/managing_an_advanced_server_installation.mdx
+++ b/product_docs/docs/epas/12/installing/linux_install_details/managing_an_advanced_server_installation.mdx
@@ -36,9 +36,9 @@ The following table lists the names of the services that control Advanced Server
 
 You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific.
 
-### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Controlling a Service on RHEL/Rocky Linux/AlmaLinux 8.x
 
-If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
+If your installation of Advanced Server resides on RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter:
 
@@ -115,9 +115,8 @@ You can use the `pg_ctl` utility to control an Advanced Server service from the
 -   `reload` sends the server a `SIGHUP` signal, reloading configuration parameters
 -   `status` to discover the current status of the service.
 
-For more information about using the `pg_ctl` utility, or the command line options available, see the official PostgreSQL Core Documentation available at:
+For more information about using the `pg_ctl` utility, or the command line options available, see the official [PostgreSQL Core Documentation](https://www.postgresql.org/docs/12/static/app-pg-ctl.html).
 
-<https://www.postgresql.org/docs/12/static/app-pg-ctl.html>
 
 **Choosing Between pg_ctl and the service Command**
 
@@ -151,9 +150,8 @@ Where:
 
 `-U` specifies the identity of the database user that will be used for the session.
 
-For more information about using the command line client, see the PostgreSQL Core Documentation at:
+For more information about using the command line client, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/12/static/app-psql.html).
 
-<https://www.postgresql.org/docs/12/static/app-psql.html>
 
 
 ## Creating a Database Cluster and Starting the Service
@@ -161,17 +159,16 @@ For more information about using the command line client, see the PostgreSQL Cor
 The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the `systemd` service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
-To review the `initdb` documentation, visit:
+For more information, see the [initdb documentation](https://www.postgresql.org/docs/12/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/12/static/app-initdb.html>
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -191,7 +188,7 @@ After creating the cluster, use `systemctl` to start, stop, or restart the servi
 systemctl { start | stop | restart } edb-as-12
 ```
 
-### On Debian 10 | 11 or Ubuntu 18.04
+### On Debian 11
 
 You can initialize multiple clusters using the bundled scripts. To create a new cluster, assume `root` privileges, and invoke the bundled script:
 
@@ -306,9 +303,8 @@ Include the `--icu-short-form` keywords to create a cluster that uses a default
 
 [https://www.enterprisedb.com/docs](/epas/latest/)
 
-For more information about using `initdb`, and the available cluster configuration options, see the PostgreSQL Core Documentation available at:
+For more information about using `initdb`, and the available cluster configuration options, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/12/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/12/static/app-initdb.html>
 
 You can also view online help for `initdb` by assuming superuser privileges and entering:
 
@@ -318,9 +314,9 @@ You can also view online help for `initdb` by assuming superuser privileges and
 
 Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file.
 
-### Modifying the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Modifying the Data Directory Location on RHEL/Rocky Linux/AlmaLinux 8.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
 
 By default, data files reside under `/var/lib/edb/as12/data` directory. To use a data directory that resides in a non-default location, perform the following steps:
 
@@ -348,9 +344,9 @@ By default, data files reside under `/var/lib/edb/as12/data` directory. To use a
 
 You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-The `edb-as12-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
+The `edb-as12-server-core` RPM for version 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
 
 The example that follows creates an Advanced Server installation with two instances; the secondary instance is named `secondary`:
 
@@ -390,15 +386,7 @@ You can create a local repository to act as a host for the Advanced Server RPM p
 
 To create and use a local repository, you must:
 
--   Use `yum` or `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
-
-    On RHEL or CentOS 7.x:
-
-    ```bash
-    yum install epel-release
-    yum install yum-utils
-    yum install createrepo
-    ```
+-   Use `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
 
     On RHEL or Rocky Linux or AlmaLinux 8.x:
 
@@ -435,21 +423,9 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use `yum` or `dnf` commands to install Advanced Server and its supporting components on the isolated servers. For example:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum -y install edb-as12-server
-    ```
+After specifying the location and connection information for your local repository, you can use `dnf` to install Advanced Server and its supporting components on the isolated servers. For example:
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf -y install edb-as12-server
-    ```
-
-For more information about creating a local `yum` repository, visit:
-
-<https://wiki.centos.org/HowTos/CreateLocalRepos>
+```text
+dnf -y install edb-as12-server
+```
 
diff --git a/product_docs/docs/epas/12/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/12/installing/linux_install_details/rpm_packages.mdx
index dae225a999b..dd6fa9a15bf 100644
--- a/product_docs/docs/epas/12/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/12/installing/linux_install_details/rpm_packages.mdx
@@ -7,20 +7,14 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu Packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages
+## RHEL/Rocky Linux/AlmaLinux/SLES Packages
 
 ### EDB Postgres Advanced Server RPM packages
 
-The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
-
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
+The tables that follow list the RPM packages that are available from EDB. You can also use the `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
 
 On RHEL or Rocky Linux or AlmaLinux 8:
 
@@ -171,36 +165,20 @@ apt list edb*
 
 If you have an existing EDB Postgres Advanced Server RPM installation, you can use `yum` or `dnf` to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb-repo
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
     ```text
     dnf upgrade edb-repo
     ```
 
-`yum` or `dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `yum` or `dnf` to upgrade all packages whose names include the expression `edb`:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
+dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `yum` or `dnf` to upgrade all packages whose names include the expression `edb`:
 
     ```text
     dnf upgrade edb*
     ```
 
 !!! Note
-    The `yum upgrade` or `dnf upgrade` command perform an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
+    The `dnf upgrade` command perform an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
 
-For more information about using yum commands and options, enter `yum --help` on your command line.
+For more information about using yum commands and options, enter `dnf --help` on your command line.
 
 For more information about using `dnf` commands and options, visit:
 
diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index 107e46928ae..00000000000
--- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb
-
-sudo systemctl start edb-as-12
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index 9476c1dd5a2..00000000000
--- a/product_docs/docs/epas/12/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb
-
-sudo systemctl start edb-as-12
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx
index 9d590c4d142..3920fe11cd9 100644
--- a/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/12/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index 3ce3a2afaee..00000000000
--- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb
-
-sudo systemctl start edb-as-12
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index 59a6bdc76f2..00000000000
--- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index a143b6ca6c9..00000000000
--- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 12, the package name is `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as12`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb
-
-sudo systemctl start edb-as-12
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index 1297c547a24..00000000000
--- a/product_docs/docs/epas/12/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/12/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 12, the package name would be `edb-as12-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/12/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-12-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as12/bin/edb-as-12-setup initdb
-
-sudo systemctl start edb-as-12
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (12.0.0, server 12.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx
index 9e2c8bb4641..8316bb9f765 100644
--- a/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/12/installing/linux_x86_64/index.mdx
@@ -14,16 +14,12 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -65,5 +53,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](epas_ubuntu_20)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/12/troubleshooting/linux_troubleshooting.mdx b/product_docs/docs/epas/12/troubleshooting/linux_troubleshooting.mdx
index b61a83b1355..b86a9a20fbc 100644
--- a/product_docs/docs/epas/12/troubleshooting/linux_troubleshooting.mdx
+++ b/product_docs/docs/epas/12/troubleshooting/linux_troubleshooting.mdx
@@ -12,9 +12,8 @@ legacyRedirectsGenerated:
 
 **Difficulty Displaying Java-based Applications**
 
-If you encounter difficulty displaying Java-based server features (controls or text not being displayed correctly, or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit the following link for other possible work-arounds:
+If you encounter difficulty displaying Java-based server features (controls or text not displayed correctly or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit this [link](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373) for other possible workarounds.
 
-<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373>
 
 **The Installation Fails to Complete Due to Existing data Directory Contents**
 
@@ -26,11 +25,9 @@ If you encounter a similar message, you should confirm that the data directory i
 
 **Difficulty Installing the EPEL Release Package**
 
-If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x:
+If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x:
 
 ```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 ```
 
diff --git a/product_docs/docs/epas/12/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/12/uninstalling/linux_uninstall.mdx
index ac3926cac0c..333d8ff96b2 100644
--- a/product_docs/docs/epas/12/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/12/uninstalling/linux_uninstall.mdx
@@ -28,40 +28,24 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you would like to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
+You can use the `dnf remove` command to remove a package installed by `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove <package_name>
-    ```
+```text
+dnf remove <package_name>
+```
 
 Where `package_name` is the name of the package that you would like to remove.
 
-`yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning.
+`rpm` doesn't remove a package that another package requires. If you attempt to remove a package that satisfies a package dependency, `rpm` provides a warning.
 
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
 To uninstall Advanced Server and its dependent packages; use the following command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove edb-as12-server*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove edb-as12-server*
-    ```
+```text
+dnf remove edb-as12-server*
+```
 
 ## Uninstalling on Debian or Ubuntu
 
diff --git a/product_docs/docs/epas/13/ecpgplus_guide/epas_platform_support/index.mdx b/product_docs/docs/epas/13/ecpgplus_guide/epas_platform_support/index.mdx
index 23919539ab5..25aaee199f8 100644
--- a/product_docs/docs/epas/13/ecpgplus_guide/epas_platform_support/index.mdx
+++ b/product_docs/docs/epas/13/ecpgplus_guide/epas_platform_support/index.mdx
@@ -12,4 +12,4 @@ For information about the platforms and versions supported by EDB Postgres Advan
 The following limitations apply to EDB Postgres Advanced Server:
 
 -   The `data` directory of a production database should not be stored on an NFS file system.
--   The LLVM JIT package is supported on RHEL or CentOS 7.x and 8.x only. LLVM JIT is not supported on PPC-LE 64 running RHEL or CentOS 7.x.
+-   The LLVM JIT package is supported on RHEL 8.x only. LLVM JIT is not supported on PPC-LE 64 running RHEL or CentOS 7.x.
diff --git a/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx b/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx
index a6a66486136..f2ebc6b7171 100644
--- a/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx
+++ b/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx
@@ -10,7 +10,7 @@ redirects:
 
 pgAdmin 4 is the leading Open Source management tool for Postgres databases. EDB pgAdmin 4 is distributed by EDB along with EDB Postgres Advanced Server databases. It is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance and use of database objects.
 
-You can install EDB pgAdmin 4 for your Advanced Server databases using yum package manager for RHEL/CentOS 7.x or 8.x platforms.
+You can install EDB pgAdmin 4 for your Advanced Server databases using yum package manager for 8.x platforms.
 
 **Installing EDB pgAdmin 4 on a Linux Host**
 
diff --git a/product_docs/docs/epas/13/epas_limitations/index.mdx b/product_docs/docs/epas/13/epas_limitations/index.mdx
index 419ad102f93..5c6becf758a 100644
--- a/product_docs/docs/epas/13/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/13/epas_limitations/index.mdx
@@ -5,4 +5,4 @@ title: Limitations
 The following limitations apply:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported on RHEL or CentOS x86 only. 
+-   The LLVM JIT package is supported on RHEL x86 only. 
diff --git a/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.png b/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.png
deleted file mode 100644
index f4a93cf57f5..00000000000
--- a/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:07423b012a855204780fe5a2a5a1e33607304a5c3020ae4acbf3d575691dedd6
-size 12136
diff --git a/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.svg b/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.svg
deleted file mode 100644
index f24d1dfefee..00000000000
--- a/product_docs/docs/epas/13/epas_qs_linux_7/images/edb_logo.svg
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="280px" height="100px" viewBox="0 0 280 100" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <title>edb-logo-disc-dark</title>
-    <g id="edb-logo-disc-dark" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="logo" transform="translate(12.000000, 2.000000)">
-            <g id="type" transform="translate(113.000000, 23.000000)" fill="#000000">
-                <path d="M123.569826,40.243321 C129.448552,40.243321 131.768408,38.2631725 131.768408,34.3028757 C131.768408,30.6730056 129.139398,28.198423 123.337361,28.198423 L110.264205,28.198423 L110.264205,40.243321 L123.569826,40.243321 Z M110.264205,9.55222635 L110.264205,19.6169759 L123.723205,19.6169759 C128.365313,19.6169759 129.990171,17.3064007 129.990171,14.6678108 C129.990171,11.8628015 127.90278,9.55222635 122.951517,9.55222635 L110.264205,9.55222635 Z M100.67323,49.6496289 C100.2083,49.6496289 99.7457667,49.1527829 99.7457667,48.6583488 L99.7457667,1.13719852 C99.7457667,0.640352505 100.2083,0.145918367 100.67323,0.145918367 L124.420599,0.145918367 C134.941434,0.145918367 140.511006,6.08636364 140.511006,13.7585343 C140.511006,17.7188312 139.039527,20.8542672 136.487206,23.0828386 L136.487206,23.246846 C140.122766,25.7238404 142.289243,29.6817254 142.289243,34.7973098 C142.289243,44.2856215 135.792208,49.6496289 124.653064,49.6496289 L100.67323,49.6496289 Z" id="Fill-17"></path>
-                <path d="M57.8167319,9.55174397 L57.8167319,40.2428386 L67.9493264,40.2428386 C77.7727665,40.2428386 82.9564944,34.3023933 82.9564944,24.8984972 C82.9564944,15.4921892 76.6128384,9.55174397 67.7959475,9.55174397 L57.8167319,9.55174397 Z M48.2257567,49.6491466 C47.7608269,49.6491466 47.2958971,49.1547124 47.2958971,48.6602783 L47.2958971,1.13671614 C47.2958971,0.642282004 47.7608269,0.145435993 48.2257567,0.145435993 L67.7959475,0.145435993 C82.4915646,0.145435993 93.4773293,9.80016698 93.4773293,24.8984972 C93.4773293,39.8304082 84.1931119,49.6491466 67.9493264,49.6491466 L48.2257567,49.6491466 Z" id="Fill-15"></path>
-                <path d="M10.8636121,29.0228015 L10.8636121,40.2428386 L38.0931623,40.2428386 C38.5556956,40.2428386 39.1740043,40.903692 39.1740043,41.3981262 L39.1740043,48.493859 C39.1740043,48.9882931 38.5556956,49.6491466 38.0931623,49.6491466 L1.27263692,49.6491466 C0.807707089,49.6491466 0.342777258,49.1547124 0.342777258,48.6578664 L0.342777258,1.13671614 C0.342777258,0.642282004 0.807707089,0.145435993 1.27263692,0.145435993 L37.6282325,0.145435993 C38.0931623,0.145435993 38.711471,0.806289425 38.711471,1.30072356 L38.711471,8.3964564 C38.711471,8.89089054 38.0931623,9.55174397 37.6282325,9.55174397 L10.8636121,9.55174397 L10.8636121,19.6164935 L35.3059798,19.6164935 C35.7709097,19.6164935 36.3892184,20.2773469 36.3892184,20.7717811 L36.3892184,27.8675139 C36.3892184,28.3619481 35.7709097,29.0228015 35.3059798,29.0228015 L10.8636121,29.0228015 Z" id="Fill-13"></path>
-            </g>
-            <g id="symbol">
-                <circle id="Oval" fill="#FF3E00" cx="48" cy="48" r="48"></circle>
-                <path d="M78,38.5615351 L78,38.5615351 C78,33.9375556 74.1296742,30.5708514 69.3566614,31.0444251 L62.0972485,31.7638661 C61.3316415,31.8393026 60.7118644,32.5014676 60.7118644,33.2432601 L60.7118644,45.7252111 L60.7118644,47.3065841 L60.7118644,59.7885351 C60.7118644,60.5289306 61.3316415,61.069559 62.0972485,60.9927255 L69.3566614,60.2732846 C74.1296742,59.8011078 78,55.6688626 78,51.0434861 L78,51.0434861 C78,48.5638596 76.8858595,46.446049 75.1169427,45.0881915 C76.8858595,43.3796939 78,41.0411617 78,38.5615351" id="Fill-20" fill="#FFFFFF"></path>
-                <path d="M33.9027515,31.7632098 L26.6447969,31.044371 C21.8703258,30.5711936 18,33.9364759 18,38.5607731 C18,41.041116 19.1141405,43.379087 20.8830573,45.0875505 C19.1141405,46.4456674 18,48.5631014 18,51.0434443 L18,51.0434443 C18,55.6677414 21.8703258,59.8007158 26.6447969,60.2738932 L33.9027515,60.992732 C34.6683585,61.0695012 35.2881356,60.5293252 35.2881356,59.7881535 L35.2881356,47.3054824 L35.2881356,45.7254327 L35.2881356,33.2427616 C35.2881356,32.5015899 34.6683585,31.8385832 33.9027515,31.7632098" id="Fill-23" fill="#FFFFFF"></path>
-                <path d="M47.9978126,39 L40.7413163,39 C39.9757093,39 39.3559322,39.5944567 39.3559322,40.3284573 L39.3559322,58.4007795 L39.3559322,60.235781 C39.3559322,61.0116447 39.9130025,61.7902993 40.7179835,61.7902993 L47.9992709,61.7902993 C47.9234393,63.2387643 45.849738,64.332788 40.9877689,64.8504956 L40.4365318,64.8979405 C40.1084145,64.931431 39.3559322,64.8979405 39.3559322,66.2598884 L39.3559322,66.6213069 C39.3559322,67.3553075 39.9567514,68 40.7223584,68 L47.9788547,68 C52.7533259,68 56.6440678,64.2378982 56.6440678,59.6580695 L56.6440678,47.2930902 C56.6440678,42.7132615 52.773742,39 47.9978126,39" id="Fill-26" fill="#FFFFFF"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx b/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx
deleted file mode 100644
index 45e2825098f..00000000000
--- a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx
+++ /dev/null
@@ -1,146 +0,0 @@
----
-navTitle: CentOS/RHEL 7
-title: "Quick Start Guide for CentOS/RHEL 7"
-
-legacyRedirectsGenerated:
-  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
-  - "/edb-docs/d/edb-postgres-advanced-server/installation-getting-started/quick-start-guide-for-linux-on-centos-or-rhel-7/13/index.html"
-  - "/edb-docs/d/edb-postgres-advanced-server/installation-getting-started/quick-start-guide-for-linux-on-centos-or-rhel-7/13/genindex.html"
----
-
-Advanced Server adds extended functionality to the open-source PostgreSQL database that supports database administration, enhanced SQL capabilities, database and application security, performance monitoring and analysis, and application development utilities. Advanced Server also supports database compatibility features for Oracle users; for detailed information about compatibility features, [see the Advanced Server documentation](/epas/latest/).
-
-This guide will walk you through using `yum` to install EDB Postgres Advanced Server on a RHEL or CentOS 7 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are additional security and resource considerations when configuring a production installation that are not covered by this document.
-
-This guide assumes that you are familiar with simple operating system and system administration procedures, and have administrative privileges on the host on which Advanced Server will be installed.
-
-Please note that if you are using the pdf version of this document, using cut/paste to copy a command may result in extra spaces or carriage returns in the pasted command. If a command fails, check the command carefully for extra characters.
-
-**Components of an EDB Postgres Advanced Server Deployment**
-
-Among the components that make up an Advanced Server deployment are:
-
-**The Database Server** - The database server (the `postmaster`) is the service that provides the key functionality that allows you to store and manage data. Advanced Server is built on the PostgreSQL open-source database project; it includes all of the documented features of community PostgreSQL and more.
-
-**The Database Cluster** - A cluster is a set of on-disk structures that comprise a collection of databases. A cluster is serviced by a single-instance of the database server. A database cluster is stored in the `data` directory; please note that the `data` directory of a production database should not be stored on an NFS file system.
-
-**Configuration Files** - You can use the parameters listed in Postgres configuration files to manage deployment preferences, security preferences, connection behaviors, and logging preferences.
-
-**Supporting Tools, Utilities, and Clients** - EDB makes available a full suite of tools and utilities that can help you monitor and manage your Advanced Server deployment. For more information, visit the [EDB website](https://www.enterprisedb.com/).
-
-**Supporting Functions, Procedures, Data Types, Index Types, Operators, Utilities, and Aggregates** - Advanced Server includes a number of features that help you manage your data.
-
-**Prerequisites**
-
-Before installing Advanced Server, use `yum` to install prerequisite packages:
-
-```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-```
-
-If you are installing Migration Toolkit or EDB\*Plus, you must first install Java:
-
-```text
-yum -y install java
-```
-
-**Installing and Configuring Advanced Server**
-
-**Step 1:** You must register with EDB to receive credentials for the EDB repository. For information about requesting credentials, visit the https://www.enterprisedb.com/user/login.
-
-**Step 2:** Assume superuser privileges to install the EDB repository configuration package:
-
-```text
-yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm
-```
-
-**Step 3:** The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. Ensure the `username` and `password` placeholders in the baseurl specification matches with the name and password of a registered EDB user. 
-
-**Step 4:** Update the cache and install Advanced Server:
-
-```text
-yum makecache
-
-yum -y install edb-as13-server
-```
-
-**Step 5:** Use sudo to assume the identity of the `enterprisedb` database superuser and create an Advanced Server cluster named `acctg` on listener port `5444`:
-
-```text
-sudo su - enterprisedb
-
-/usr/edb/as13/bin/initdb -D /var/lib/edb/as13/acctg
-```
-
-**Starting the Cluster**
-
-As the `enterprisedb` user, start the cluster:
-
-```text
-/usr/edb/as13/bin/pg_ctl start -D /var/lib/edb/as13/acctg
-```
-
-You can check the status of the cluster with the command:
-
-```text
-/usr/edb/as13/bin/pg_ctl status -D /var/lib/edb/as13/acctg
-```
-
-**Using the psql Command Line Client**
-
-After installing the server and initializing a cluster, you can connect to the database with your choice of client. For convenience, the server is deployed with the [pgAdmin 4 graphical client](https://www.pgadmin.org/docs/) and the [psql command line client](https://www.postgresql.org/docs/current/app-psql.html).
-
-As the `enterprisedb` user, open a psql session:
-
-```text
-/usr/edb/as13/bin/psql -d edb -p 5444
-```
-
-Then, assign a password to the `enterprisedb` user:
-
-```text
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-Create a database (named `hr`):
-
-```text
-CREATE DATABASE hr;
-```
-
-Connect to the new database and create a table (named `dept`):
-
-```text
-\c hr
-
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-```
-
-Add data to the table:
-
-```text
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-```
-
-You can use simple SQL commands to query the database and retrieve information about the data you have added to the table:
-
-```text
-SELECT * FROM dept;
- deptno |   dname    |   loc
---------+------------+----------
-     10 | ACCOUNTING | NEW YORK
-     20 | RESEARCH   | DALLAS
-(2 rows)
-```
-
-Or, create database users:
-
-```text
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-For detailed product usage information, see the [Advanced Server documentation, available at the EDB website](/epas/latest/).
diff --git a/product_docs/docs/epas/13/installing/index.mdx b/product_docs/docs/epas/13/installing/index.mdx
index 1921a37aef1..674914f33be 100644
--- a/product_docs/docs/epas/13/installing/index.mdx
+++ b/product_docs/docs/epas/13/installing/index.mdx
@@ -26,35 +26,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx
index 43f8e1cf9cc..b75abd7a79f 100644
--- a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx
@@ -6,10 +6,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu Locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES locations
+## RHEL/Rocky Linux/AlmaLinux/SLES locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table below:
 
diff --git a/product_docs/docs/epas/13/installing/linux_install_details/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/13/installing/linux_install_details/managing_an_advanced_server_installation.mdx
index 3251ce52f2f..602cda8db61 100644
--- a/product_docs/docs/epas/13/installing/linux_install_details/managing_an_advanced_server_installation.mdx
+++ b/product_docs/docs/epas/13/installing/linux_install_details/managing_an_advanced_server_installation.mdx
@@ -28,9 +28,9 @@ The following table lists the names of the services that control Advanced Server
 
 You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific.
 
-### Controlling a service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Controlling a service on RHEL/Rocky Linux/AlmaLinux 8.x
 
-If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
+If your installation of Advanced Server resides on RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter:
 
@@ -49,9 +49,9 @@ Where:
 -   `restart` to stop and then start the service.
 -   `status` to discover the current status of the service.
 
-### Controlling a service on Debian 10.x or Ubuntu 18.04 | 20.04
+### Controlling a service on Ubuntu 20.04
 
-If your installation of Advanced Server resides on version 10.x of Debian or 18.04 or 20.04 of Ubuntu, assume superuser privileges and invoke the following commands (using bundled scripts) to manage the service. Use the following commands to:
+If your installation of Advanced Server resides on version 20.04 of Ubuntu, assume superuser privileges and invoke the following commands (using bundled scripts) to manage the service. Use the following commands to:
 
 -   Discover the current status of a service:
 
@@ -101,9 +101,8 @@ You can use the `pg_ctl` utility to control an Advanced Server service from the
 -   `reload` sends the server a `SIGHUP` signal, reloading configuration parameters
 -   `status` to discover the current status of the service.
 
-For more information about using the `pg_ctl` utility, or the command line options available, see the official PostgreSQL Core Documentation available at:
+For more information about using the `pg_ctl` utility or the command line options available, see the official [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-pg-ctl.html).
 
-<https://www.postgresql.org/docs/current/static/app-pg-ctl.html>
 
 **Choosing Between pg_ctl and the service Command**
 
@@ -137,9 +136,8 @@ Where:
 
 `-U` specifies the identity of the database user that will be used for the session.
 
-`edb-psql` is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community `psql`, with added support for Advanced Server features. . For more information about using the command line client, see the PostgreSQL Core Documentation at:
+`edb-psql` is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community `psql`, with added support for Advanced Server features.  For more information about using the command line client, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-psql.html).
 
-<https://www.postgresql.org/docs/current/static/app-psql.html>
 
 ## Configuring a package installation
 
@@ -150,17 +148,16 @@ The packages that install the database server component create service startup s
 The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the `systemd` service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
-To review the `initdb` documentation, visit:
+For more information, see the [initdb documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/current/static/app-initdb.html>
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific.
 
-#### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+#### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x on RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -295,9 +292,8 @@ Include the `--icu-short-form` keywords to create a cluster that uses a default
 
 [https://www.enterprisedb.com/docs](/epas/latest/)
 
-For more information about using `initdb`, and the available cluster configuration options, see the PostgreSQL Core Documentation available at:
+For more information about using `initdb`, and the available cluster configuration options, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/current/static/app-initdb.html>
 
 You can also view online help for `initdb` by assuming superuser privileges and entering:
 
@@ -309,9 +305,9 @@ Where `path_to_initdb_installation_directory` specifies the location of the `ini
 
 ## Modifying the Data Directory Location 
 
-### on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x
+### on RHEL or Rocky Linux 8.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
 
 By default, data files reside under `/var/lib/edb/as13/data` directory. To use a data directory that resides in a non-default location, perform the following steps:
 
@@ -354,7 +350,7 @@ By default, data files reside under `/var/lib/edb/as13/data` directory. To use a
     systemctl start edb-as-13
     ```
 
-### Configuring SELinux Policy to Change the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Configuring SELinux Policy to Change the Data Directory Location on RHEL/Rocky Linux/AlmaLinux 8.x
 
 By default, the data files resides under `/var/lib/edb/as13/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps:
 
@@ -438,9 +434,9 @@ By default, the data files resides under `/var/lib/edb/as13/data` directory. To
 
 You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination.
 
-### Enabling Core Dumps on a RHEL/CentOS 7 or RHEL/Rocky Linux/AlmaLinux 8 Host
+### Enabling Core Dumps on a RHEL/Rocky Linux/AlmaLinux 8 Host
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands:
+On a RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
@@ -665,9 +661,9 @@ On Debian 10 or Ubuntu 18, 20, core file creation is disabled by default. To ena
 
 You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-The `edb-as13-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
+The `edb-as13-server-core` RPM for version 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
 
 The example that follows creates an Advanced Server installation with two instances; the secondary instance is named `secondary`:
 
@@ -707,15 +703,7 @@ You can create a local repository to act as a host for the Advanced Server RPM p
 
 To create and use a local repository, you must:
 
--   Use `yum` or `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
-
-    On RHEL or CentOS 7.x:
-
-    ```bash
-    yum install epel-release
-    yum install yum-utils
-    yum install createrepo
-    ```
+-   Use `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
 
     On RHEL or Rocky Linux or AlmaLinux 8.x:
 
@@ -752,13 +740,7 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use `yum` or `dnf` commands to install Advanced Server and its supporting components on the isolated servers. For example:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum -y install edb-as13-server
-    ```
+After specifying the location and connection information for your local repository, you can use `dnf` to install Advanced Server and its supporting components on the isolated servers. For example:
 
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
@@ -766,6 +748,3 @@ After specifying the location and connection information for your local reposito
     dnf -y install edb-as13-server
     ```
 
-For more information about creating a local `yum` repository, visit:
-
-<https://wiki.centos.org/HowTos/CreateLocalRepos>
diff --git a/product_docs/docs/epas/13/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/13/installing/linux_install_details/rpm_packages.mdx
index e43393a2011..e5358a45984 100644
--- a/product_docs/docs/epas/13/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/13/installing/linux_install_details/rpm_packages.mdx
@@ -6,21 +6,15 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu Packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages
+## RHEL/Rocky Linux/AlmaLinux/SLES Packages
 
 ### EDB Postgres Advanced Server RPM Packages
 
 The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
 
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
-
 On RHEL or Rocky Linux or AlmaLinux 8:
 
 ```text
diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index 24185ec8231..00000000000
--- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb
-
-sudo systemctl start edb-as-13
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index b99182814c6..00000000000
--- a/product_docs/docs/epas/13/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb
-
-sudo systemctl start edb-as-13
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx
index a3a7b44b039..00399bd5080 100644
--- a/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/13/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index 3e880ffb8f1..00000000000
--- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb
-
-sudo systemctl start edb-as-13
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index a7353cac88c..00000000000
--- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index ebcf9046343..00000000000
--- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb
-
-sudo systemctl start edb-as-13
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index 99ce0bf1248..00000000000
--- a/product_docs/docs/epas/13/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 13, the package name would be `edb-as13-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb
-
-sudo systemctl start edb-as-13
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (13.0.0, server 13.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx
index f1bfa456b51..7f285870d0c 100644
--- a/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/13/installing/linux_x86_64/index.mdx
@@ -14,16 +14,12 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -65,5 +53,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](epas_ubuntu_20)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/13/troubleshooting/linux_troubleshooting.mdx b/product_docs/docs/epas/13/troubleshooting/linux_troubleshooting.mdx
index 1f539508740..ef7e10b2ba4 100644
--- a/product_docs/docs/epas/13/troubleshooting/linux_troubleshooting.mdx
+++ b/product_docs/docs/epas/13/troubleshooting/linux_troubleshooting.mdx
@@ -12,9 +12,8 @@ legacyRedirectsGenerated:
 
 **Difficulty Displaying Java-based Applications**
 
-If you encounter difficulty displaying Java-based server features (controls or text not being displayed correctly, or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit the following link for other possible work-arounds:
+If you encounter difficulty displaying Java-based server features (controls or text not displayed correctly or blank windows), upgrading to the latest `libxcb-xlib` libraries should correct the problem on most distributions. Please visit this [link](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373) for other possible workarounds.
 
-<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373>
 
 **The Installation Fails to Complete Due to Existing data Directory Contents**
 
@@ -26,11 +25,9 @@ If you encounter a similar message, you should confirm that the data directory i
 
 **Difficulty Installing the EPEL Release Package**
 
-If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x:
+If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x:
 
 ```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 ```
 
@@ -44,7 +41,5 @@ Error: Nothing to do
 If you receive this error, you can download the `EPEL` rpm package, and install it manually. To manually install `EPEL`, download the rpm package, assume superuser privileges, navigate into the directory that contains the package, and install `EPEL` with the command:
 
 ```text
-yum -y install epel-release
-
 dnf -y install epel-release
 ```
diff --git a/product_docs/docs/epas/13/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/13/uninstalling/linux_uninstall.mdx
index 8e4771aa51b..56c76acddc1 100644
--- a/product_docs/docs/epas/13/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/13/uninstalling/linux_uninstall.mdx
@@ -12,9 +12,9 @@ legacyRedirectsGenerated:
 
 Note that after uninstalling Advanced Server, the cluster data files remain intact and the service user persists. You may manually remove the cluster `data` and service user from the system.
 
-## Uninstalling on RHEL/OL/AlmaLinux/Rocky Linux
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
 
-You can use variations of the `rpm, yum` or `dnf` command to remove installed packages. Note that removing a package does not damage the Advanced Server `data` directory.
+You can use variations of the `rpm` or `dnf` command to remove installed packages. Note that removing a package does not damage the Advanced Server `data` directory.
 
 Include the `-e` option when invoking the `rpm` command to remove an installed package; the command syntax is:
 
@@ -24,40 +24,24 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you would like to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
+You can use the `dnf remove` command to remove a package installed by `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove <package_name>
-    ```
+```text
+dnf remove <package_name>
+```
 
 Where `package_name` is the name of the package that you would like to remove.
 
-`yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning.
+`rpm` does not remove a package that another package requires. If you attempt to remove a package that satisfies a package dependency, `rpm` provides a warning.
 
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
 To uninstall Advanced Server and its dependent packages; use the following command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove edb-as13-server*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove edb-as13-server*
-    ```
+```text
+dnf remove edb-as13-server*
+```
 
 ## Uninstalling on Debian or Ubuntu
 
diff --git a/product_docs/docs/epas/14/epas_limitations/index.mdx b/product_docs/docs/epas/14/epas_limitations/index.mdx
index e9bed63f207..e5b1c55d8ab 100644
--- a/product_docs/docs/epas/14/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/14/epas_limitations/index.mdx
@@ -5,4 +5,4 @@ title: "Limitations"
 The following limitations apply:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported on RHEL or CentOS x86 only. 
+-   The LLVM JIT package is supported on RHEL x86 only. 
diff --git a/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.png b/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.png
deleted file mode 100644
index f4a93cf57f5..00000000000
--- a/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:07423b012a855204780fe5a2a5a1e33607304a5c3020ae4acbf3d575691dedd6
-size 12136
diff --git a/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.svg b/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.svg
deleted file mode 100644
index f24d1dfefee..00000000000
--- a/product_docs/docs/epas/14/epas_qs_linux_7/images/edb_logo.svg
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="280px" height="100px" viewBox="0 0 280 100" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <title>edb-logo-disc-dark</title>
-    <g id="edb-logo-disc-dark" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="logo" transform="translate(12.000000, 2.000000)">
-            <g id="type" transform="translate(113.000000, 23.000000)" fill="#000000">
-                <path d="M123.569826,40.243321 C129.448552,40.243321 131.768408,38.2631725 131.768408,34.3028757 C131.768408,30.6730056 129.139398,28.198423 123.337361,28.198423 L110.264205,28.198423 L110.264205,40.243321 L123.569826,40.243321 Z M110.264205,9.55222635 L110.264205,19.6169759 L123.723205,19.6169759 C128.365313,19.6169759 129.990171,17.3064007 129.990171,14.6678108 C129.990171,11.8628015 127.90278,9.55222635 122.951517,9.55222635 L110.264205,9.55222635 Z M100.67323,49.6496289 C100.2083,49.6496289 99.7457667,49.1527829 99.7457667,48.6583488 L99.7457667,1.13719852 C99.7457667,0.640352505 100.2083,0.145918367 100.67323,0.145918367 L124.420599,0.145918367 C134.941434,0.145918367 140.511006,6.08636364 140.511006,13.7585343 C140.511006,17.7188312 139.039527,20.8542672 136.487206,23.0828386 L136.487206,23.246846 C140.122766,25.7238404 142.289243,29.6817254 142.289243,34.7973098 C142.289243,44.2856215 135.792208,49.6496289 124.653064,49.6496289 L100.67323,49.6496289 Z" id="Fill-17"></path>
-                <path d="M57.8167319,9.55174397 L57.8167319,40.2428386 L67.9493264,40.2428386 C77.7727665,40.2428386 82.9564944,34.3023933 82.9564944,24.8984972 C82.9564944,15.4921892 76.6128384,9.55174397 67.7959475,9.55174397 L57.8167319,9.55174397 Z M48.2257567,49.6491466 C47.7608269,49.6491466 47.2958971,49.1547124 47.2958971,48.6602783 L47.2958971,1.13671614 C47.2958971,0.642282004 47.7608269,0.145435993 48.2257567,0.145435993 L67.7959475,0.145435993 C82.4915646,0.145435993 93.4773293,9.80016698 93.4773293,24.8984972 C93.4773293,39.8304082 84.1931119,49.6491466 67.9493264,49.6491466 L48.2257567,49.6491466 Z" id="Fill-15"></path>
-                <path d="M10.8636121,29.0228015 L10.8636121,40.2428386 L38.0931623,40.2428386 C38.5556956,40.2428386 39.1740043,40.903692 39.1740043,41.3981262 L39.1740043,48.493859 C39.1740043,48.9882931 38.5556956,49.6491466 38.0931623,49.6491466 L1.27263692,49.6491466 C0.807707089,49.6491466 0.342777258,49.1547124 0.342777258,48.6578664 L0.342777258,1.13671614 C0.342777258,0.642282004 0.807707089,0.145435993 1.27263692,0.145435993 L37.6282325,0.145435993 C38.0931623,0.145435993 38.711471,0.806289425 38.711471,1.30072356 L38.711471,8.3964564 C38.711471,8.89089054 38.0931623,9.55174397 37.6282325,9.55174397 L10.8636121,9.55174397 L10.8636121,19.6164935 L35.3059798,19.6164935 C35.7709097,19.6164935 36.3892184,20.2773469 36.3892184,20.7717811 L36.3892184,27.8675139 C36.3892184,28.3619481 35.7709097,29.0228015 35.3059798,29.0228015 L10.8636121,29.0228015 Z" id="Fill-13"></path>
-            </g>
-            <g id="symbol">
-                <circle id="Oval" fill="#FF3E00" cx="48" cy="48" r="48"></circle>
-                <path d="M78,38.5615351 L78,38.5615351 C78,33.9375556 74.1296742,30.5708514 69.3566614,31.0444251 L62.0972485,31.7638661 C61.3316415,31.8393026 60.7118644,32.5014676 60.7118644,33.2432601 L60.7118644,45.7252111 L60.7118644,47.3065841 L60.7118644,59.7885351 C60.7118644,60.5289306 61.3316415,61.069559 62.0972485,60.9927255 L69.3566614,60.2732846 C74.1296742,59.8011078 78,55.6688626 78,51.0434861 L78,51.0434861 C78,48.5638596 76.8858595,46.446049 75.1169427,45.0881915 C76.8858595,43.3796939 78,41.0411617 78,38.5615351" id="Fill-20" fill="#FFFFFF"></path>
-                <path d="M33.9027515,31.7632098 L26.6447969,31.044371 C21.8703258,30.5711936 18,33.9364759 18,38.5607731 C18,41.041116 19.1141405,43.379087 20.8830573,45.0875505 C19.1141405,46.4456674 18,48.5631014 18,51.0434443 L18,51.0434443 C18,55.6677414 21.8703258,59.8007158 26.6447969,60.2738932 L33.9027515,60.992732 C34.6683585,61.0695012 35.2881356,60.5293252 35.2881356,59.7881535 L35.2881356,47.3054824 L35.2881356,45.7254327 L35.2881356,33.2427616 C35.2881356,32.5015899 34.6683585,31.8385832 33.9027515,31.7632098" id="Fill-23" fill="#FFFFFF"></path>
-                <path d="M47.9978126,39 L40.7413163,39 C39.9757093,39 39.3559322,39.5944567 39.3559322,40.3284573 L39.3559322,58.4007795 L39.3559322,60.235781 C39.3559322,61.0116447 39.9130025,61.7902993 40.7179835,61.7902993 L47.9992709,61.7902993 C47.9234393,63.2387643 45.849738,64.332788 40.9877689,64.8504956 L40.4365318,64.8979405 C40.1084145,64.931431 39.3559322,64.8979405 39.3559322,66.2598884 L39.3559322,66.6213069 C39.3559322,67.3553075 39.9567514,68 40.7223584,68 L47.9788547,68 C52.7533259,68 56.6440678,64.2378982 56.6440678,59.6580695 L56.6440678,47.2930902 C56.6440678,42.7132615 52.773742,39 47.9978126,39" id="Fill-26" fill="#FFFFFF"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx b/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx
deleted file mode 100644
index 12443db0883..00000000000
--- a/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx
+++ /dev/null
@@ -1,139 +0,0 @@
----
-navTitle: CentOS/RHEL 7
-title: "Quick start for CentOS or RHEL 7"
----
-
-EDB Postgres Advanced Server adds extended functionality to the open-source PostgreSQL database that supports database administration, enhanced SQL capabilities, database and application security, performance monitoring and analysis, and application development utilities. EDB Postgres Advanced Server also supports database compatibility features for Oracle users; for detailed information about compatibility features, [see the EDB Postgres Advanced Server documentation](/epas/latest/).
-
-This guide walks you through using `yum` to install EDB Postgres Advanced Server on a RHEL or CentOS 7 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are additional security and resource considerations when configuring a production installation that are not covered by this document.
-
-This guide assumes that you are familiar with simple operating system and system administration procedures, and have administrative privileges on the host on which EDB Postgres Advanced Server is installed.
-
-## Components of an EDB Postgres Advanced Server deployment
-
-Among the components that make up an EDB Postgres Advanced Server deployment are:
-
-The Database server - The database server (the `postmaster`) is the service that provides the key functionality that allows you to store and manage data. EDB Postgres Advanced Server is built on the PostgreSQL open-source database project; it includes all of the documented features of community PostgreSQL and more.
-
-The database cluster - A cluster is a set of on-disk structures that comprise a collection of databases. A cluster is serviced by a single-instance of the database server. A database cluster is stored in the `data` directory. Don't store the `data` directory of a production database on an NFS file system.
-
-Configuration files - You can use the parameters listed in Postgres configuration files to manage deployment preferences, security preferences, connection behaviors, and logging preferences.
-
-Supporting tools, utilities, and clients - EDB makes available a full suite of tools and utilities that can help you monitor and manage your EDB Postgres Advanced Server deployment. For more information, visit the [EDB website](https://www.enterprisedb.com/).
-
-Supporting functions, rocedures, data types, index types, operators, utilities, and aggregates - EDB Postgres Advanced Server includes a number of features that help you manage your data.
-
-## Prerequisites
-
-Before installing EDB Postgres Advanced Server, use `yum` to install prerequisite packages:
-
-```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-```
-
-If you are installing Migration Toolkit or EDB\*Plus, you must first install Java:
-
-```text
-yum -y install java
-```
-
-## Installing and configuring EDB Postgres Advanced Server
-
-**Step 1:** You must register with EDB to receive credentials for the EDB repository. For information about requesting credentials, visit the https://www.enterprisedb.com/user/login.
-
-**Step 2:** Assume superuser privileges to install the EDB repository configuration package:
-
-```text
-yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm
-```
-
-**Step 3:** The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. Ensure the `username` and `password` placeholders in the baseurl specification matches with the name and password of a registered EDB user. 
-
-**Step 4:** Update the cache and install EDB Postgres Advanced Server:
-
-```text
-yum makecache
-
-yum -y install edb-as14-server
-```
-
-**Step 5:** Use sudo to assume the identity of the `enterprisedb` database superuser and create an EDB Postgres Advanced Server cluster named `acctg` on listener port `5444`:
-
-```text
-sudo su - enterprisedb
-
-/usr/edb/as14/bin/initdb -D /var/lib/edb/as14/acctg
-```
-
-## Starting the cluster
-
-As the `enterprisedb` user, start the cluster:
-
-```text
-/usr/edb/as14/bin/pg_ctl start -D /var/lib/edb/as14/acctg
-```
-
-You can check the status of the cluster with the command:
-
-```text
-/usr/edb/as14/bin/pg_ctl status -D /var/lib/edb/as14/acctg
-```
-
-## Using the psql command line client
-
-After installing the server and initializing a cluster, you can connect to the database with your choice of client. For convenience, the server is deployed with the [pgAdmin 4 graphical client](https://www.pgadmin.org/docs/) and the [psql command line client](https://www.postgresql.org/docs/current/app-psql.html).
-
-As the `enterprisedb` user, open a psql session:
-
-```text
-/usr/edb/as14/bin/psql -d edb -p 5444
-```
-
-Then, assign a password to the `enterprisedb` user:
-
-```text
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-Create a database (named `hr`):
-
-```text
-CREATE DATABASE hr;
-```
-
-Connect to the new database and create a table (named `dept`):
-
-```text
-\c hr
-
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-```
-
-Add data to the table:
-
-```text
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-```
-
-You can use simple SQL commands to query the database and retrieve information about the data you have added to the table:
-
-```text
-SELECT * FROM dept;
- deptno |   dname    |   loc
---------+------------+----------
-     10 | ACCOUNTING | NEW YORK
-     20 | RESEARCH   | DALLAS
-(2 rows)
-```
-
-Or, create database users:
-
-```text
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-For detailed product usage information, see the [EDB Postgres Advanced Server documentation](/epas/latest/) available at the EDB website.
diff --git a/product_docs/docs/epas/14/installing/index.mdx b/product_docs/docs/epas/14/installing/index.mdx
index a76cc227936..e11325dffa1 100644
--- a/product_docs/docs/epas/14/installing/index.mdx
+++ b/product_docs/docs/epas/14/installing/index.mdx
@@ -26,35 +26,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx
index 30e7801b18a..91380f0c052 100644
--- a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx
@@ -6,10 +6,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu Locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table below:
 
diff --git a/product_docs/docs/epas/14/installing/linux_install_details/installing_epas_using_local_repository.mdx b/product_docs/docs/epas/14/installing/linux_install_details/installing_epas_using_local_repository.mdx
index 7dc2135df59..6081d42c0af 100644
--- a/product_docs/docs/epas/14/installing/linux_install_details/installing_epas_using_local_repository.mdx
+++ b/product_docs/docs/epas/14/installing/linux_install_details/installing_epas_using_local_repository.mdx
@@ -55,20 +55,8 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use `yum` or `dnf` commands to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example:
+After specifying the location and connection information for your local repository, you can use `dnf` commands to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum -y install edb-as14-server
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf -y install edb-as14-server
-    ```
-
-For more information about creating a local `yum` repository, visit:
-
-<https://wiki.centos.org/HowTos/CreateLocalRepos>
+```text
+dnf -y install edb-as14-server
+```
diff --git a/product_docs/docs/epas/14/installing/linux_install_details/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/14/installing/linux_install_details/managing_an_advanced_server_installation.mdx
index e2a2e4cebe5..0a5e672bd6e 100644
--- a/product_docs/docs/epas/14/installing/linux_install_details/managing_an_advanced_server_installation.mdx
+++ b/product_docs/docs/epas/14/installing/linux_install_details/managing_an_advanced_server_installation.mdx
@@ -27,9 +27,9 @@ The following table lists the names of the services that control EDB Postgres Ad
 
 You can use the Linux command line to control EDB Postgres Advanced Server's database server and the services of EDB Postgres Advanced Server's supporting components. The commands that control the EDB Postgres Advanced Server service on a Linux platform are host specific.
 
-### Controlling a service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Controlling a service on RHEL/Rocky Linux/AlmaLinux 8.x
 
-If your installation of EDB Postgres Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
+If your installation of EDB Postgres Advanced Server resides on version 8.x of RHEL, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter:
 
@@ -48,9 +48,9 @@ Where:
 -   `restart` to stop and then start the service.
 -   `status` to discover the current status of the service.
 
-### Controlling a service on Debian 10.x or Ubuntu 18.04 | 20.04
+### Controlling a service on Ubuntu 20.04
 
-If your installation of EDB Postgres Advanced Server resides on version 18.04 | 20.04 of Ubuntu, assume superuser privileges and invoke the following commands (using bundled scripts) to manage the service. Use the following commands to:
+If your installation of EDB Postgres Advanced Server resides on version 20.04 of Ubuntu, assume superuser privileges and invoke the following commands (using bundled scripts) to manage the service. Use the following commands to:
 
 -   Discover the current status of a service:
 
@@ -100,9 +100,8 @@ You can use the `pg_ctl` utility to control an EDB Postgres Advanced Server serv
 -   `reload` sends the server a `SIGHUP` signal, reloading configuration parameters
 -   `status` to discover the current status of the service.
 
-For more information about using the `pg_ctl` utility, or the command line options available, see the official PostgreSQL Core Documentation available at:
+For more information about using the `pg_ctl` utility or the command-line options available, see the official [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-pg-ctl.html). 
 
-<https://www.postgresql.org/docs/current/static/app-pg-ctl.html>
 
 **Choosing Between pg_ctl and the service Command**
 
@@ -136,17 +135,15 @@ Where:
 
 `-U` specifies the identity of the database user to use for the session.
 
-`edb-psql` is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community `psql`, with added support for Advanced Server features. For more information about using the command line client, see the PostgreSQL Core Documentation at:
+`edb-psql` is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community `psql`, with added support for Advanced Server features. For more information about using the command line client, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-psql.html).
 
-<https://www.postgresql.org/docs/current/static/app-psql.html>
 
 ### Managing authentication on a Debian or Ubuntu host
 
 By default, the server is running with the peer or md5 permission on a Debian or Ubuntu host. You can change the authentication method by modifying the `pg_hba.conf` file, located under `/etc/edb-as/14/main/`.
 
-For more information about modifying the `pg_hba.conf` file, see the PostgreSQL core documentation available at:
+For more information about modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). 
 
-<https://www.postgresql.org/docs/current/auth-pg-hba-conf.html>
 
 ## Configuring a package installation
 
@@ -157,17 +154,16 @@ The packages that install the database server component create a unit file (on v
 The PostgreSQL `initdb` command creates a database cluster; when installing EDB Postgres Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing EDB Postgres Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the `systemd` service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
-To review the `initdb` documentation, visit:
+For more information, see the [initdb documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/current/static/app-initdb.html>
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific.
 
-#### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+#### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -298,9 +294,8 @@ Include the `--icu-short-form` keywords to create a cluster that uses a default
 
 [https://www.enterprisedb.com/docs](/epas/latest/)
 
-For more information about using `initdb`, and the available cluster configuration options, see the PostgreSQL Core Documentation available at:
+For more information about using `initdb`, and the available cluster configuration options, see the [PostgreSQL Core Documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
-<https://www.postgresql.org/docs/current/static/app-initdb.html>
 
 You can also view online help for `initdb` by assuming superuser privileges and entering:
 
@@ -312,9 +307,9 @@ Where `path_to_initdb_installation_directory` specifies the location of the `ini
 
 ## Modifying the data directory location 
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades.
 
 By default, data files reside under `/var/lib/edb/as14/data` directory. To use a data directory that resides in a non-default location, perform the following steps:
 
@@ -357,7 +352,7 @@ By default, data files reside under `/var/lib/edb/as14/data` directory. To use a
     systemctl start edb-as-14
     ```
 
-### Configuring SELinux policy to change the data directory location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### Configuring SELinux policy to change the data directory location on RHEL/Rocky Linux/AlmaLinux 8.x
 
 By default, the data files resides under `/var/lib/edb/as14/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps:
 
@@ -441,7 +436,7 @@ By default, the data files resides under `/var/lib/edb/as14/data` directory. To
 
 You can configure EDB Postgres Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
 The `edb-as14-server-core` RPM for version 7.x | 8.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script.
 
diff --git a/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx
index b08723e8b77..bc227da1bd8 100644
--- a/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/14/installing/linux_install_details/rpm_packages.mdx
@@ -6,22 +6,14 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES Packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu Packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Packages
+## RHEL/Rocky Linux/AlmaLinux/SLES Packages
 
 ### EDB Postgres Advanced Server RPM packages
 
-The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
-
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
-
-On RHEL or Rocky Linux or AlmaLinux 8:
+The tables that follow list the RPM packages that are available from EDB. You can also use the `dnf search` command to access a list of the packages that are currently available from your configured repository. Open a command line, assume superuser privileges, and enter:
 
 ```text
 dnf search <package>
@@ -168,38 +160,20 @@ apt list edb*
 
 ### Updating an RPM installation
 
-If you have an existing EDB Postgres Advanced Server RPM installation, you can use `yum` or `dnf` to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb-repo
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
+If you have an existing EDB Postgres Advanced Server RPM installation, you can use `dnf` to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
 
-    ```text
-    dnf upgrade edb-repo
-    ```
-
-`yum` or `dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `yum` or `dnf` to upgrade all packages whose names include the expression `edb`:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb*
-    ```
+```text
+dnf upgrade edb-repo
+```
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
+`dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `dnf` to upgrade all packages whose names include the expression `edb`:
 
-    ```text
-    dnf upgrade edb*
-    ```
+```text
+dnf upgrade edb*
+```
 
 !!! Note
-    The `yum upgrade` or `dnf upgrade` command perform an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
-
-For more information about using yum commands and options, enter `yum --help` on your command line.
+    The `dnf upgrade` command perform an update only between minor releases; to update between major releases, you must use `pg_upgrade`.
 
 For more information about using `dnf` commands and options, visit:
 
diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index 489cc668de5..00000000000
--- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb
-
-sudo systemctl start edb-as-14
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index ed9d182000d..00000000000
--- a/product_docs/docs/epas/14/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb
-
-sudo systemctl start edb-as-14
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx
index 8916fe99c5a..e1f7f6e9d18 100644
--- a/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/14/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index c322a018b1f..00000000000
--- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb
-
-sudo systemctl start edb-as-14
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index 6c8af33e087..00000000000
--- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index 7e91b155c2b..00000000000
--- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb
-
-sudo systemctl start edb-as-14
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index 612bd5dabb1..00000000000
--- a/product_docs/docs/epas/14/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 14, the package name would be `edb-as14-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb
-
-sudo systemctl start edb-as-14
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (14.0.0, server 14.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx
index 3de970a17ce..6a154a7bb90 100644
--- a/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/14/installing/linux_x86_64/index.mdx
@@ -14,16 +14,12 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -65,5 +53,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](epas_ubuntu_20)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/14/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx b/product_docs/docs/epas/14/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
index c857013cb70..3981ffd36b2 100644
--- a/product_docs/docs/epas/14/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
+++ b/product_docs/docs/epas/14/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
@@ -7,9 +7,9 @@ redirects:
 
 You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination.
 
-## Enabling core dumps on a RHEL or CentOS or Rocky Linux or AlmaLinux host
+## Enabling core dumps on a RHEL or Rocky Linux or AlmaLinux host
 
-On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands:
+On RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
@@ -116,9 +116,9 @@ On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disa
     (gdb) bt full
     ```
 
-## Enabling core dumps on a Debian or Ubuntu host
+## Enabling core dumps on an Ubuntu host
 
-On Debian 10 or Ubuntu 18, 20, core file creation is disabled by default. To enable the core file generation, follow the following commands:
+On Ubuntu 20, core file creation is disabled by default. To enable the core file generation, follow the following commands:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
diff --git a/product_docs/docs/epas/14/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/14/uninstalling/linux_uninstall.mdx
index 38b4b16f449..20278f8641c 100644
--- a/product_docs/docs/epas/14/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/14/uninstalling/linux_uninstall.mdx
@@ -10,9 +10,9 @@ legacyRedirects:
 
 Note that after uninstalling EDB Postgres Advanced Server, the cluster data files remain intact and the service user persists. You may manually remove the cluster `data` and service user from the system.
 
-## Uninstalling on RHEL/OL/AlmaLinux/Rocky Linux
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
 
-You can use variations of the `rpm, yum` or `dnf` command to remove installed packages. Note that removing a package does not damage the EDB Postgres Advanced Server `data` directory.
+You can use variations of the `rpm` or `dnf` command to remove installed packages. Note that removing a package does not damage the EDB Postgres Advanced Server `data` directory.
 
 Include the `-e` option when invoking the `rpm` command to remove an installed package; the command syntax is:
 
@@ -22,40 +22,26 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you would like to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
+You can use the `dnf remove` command to remove a package installed by `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
 
--   On RHEL or CentOS 7:
+On RHEL or Rocky Linux or AlmaLinux 8:
 
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove <package_name>
-    ```
+```text
+dnf remove <package_name>
+```
 
 Where `package_name` is the name of the package that you want to remove.
 
-`yum` and RPM don't remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM provides a warning.
+`rpm` doesn't remove a package that another package requires. If you attempt to remove a package that satisfies a package dependency, `rpm` provides a warning.
 
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
 To uninstall EDB Postgres Advanced Server and its dependent packages; use the following command:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove edb-as14-server*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove edb-as14-server*
-    ```
+```text
+dnf remove edb-as14-server*
+```
 
 ## Uninstalling on Debian or Ubuntu
 
diff --git a/product_docs/docs/epas/15/epas_security_guide/04_sslutils.mdx b/product_docs/docs/epas/15/epas_security_guide/04_sslutils.mdx
index 1d07c9d442c..8014acbbe6e 100644
--- a/product_docs/docs/epas/15/epas_security_guide/04_sslutils.mdx
+++ b/product_docs/docs/epas/15/epas_security_guide/04_sslutils.mdx
@@ -22,7 +22,6 @@ Install `sslutils` using the following command:
       | Package manager | Operating system                 |
       | --------------- | -------------------------------- |
       | dnf             | RHEL 8/9 and derivatives         |
-      | yum             | RHEL 7 and derivatives, CentOS 7 |
       | zypper          | SLES                             |
       | apt-get         | Debian 10/11 and derivatives     |
 
diff --git a/product_docs/docs/epas/15/installing/index.mdx b/product_docs/docs/epas/15/installing/index.mdx
index ecf3eb113aa..d1ea85b3cf0 100644
--- a/product_docs/docs/epas/15/installing/index.mdx
+++ b/product_docs/docs/epas/15/installing/index.mdx
@@ -30,35 +30,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx
index 093c4acd6e7..78a6e7ca166 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx
@@ -7,10 +7,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/OL/Rocky Linux/AlmaLinux/SLES locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table.
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/installing_epas_using_local_repository.mdx b/product_docs/docs/epas/15/installing/linux_install_details/installing_epas_using_local_repository.mdx
index acd5787a295..e23cb939c1c 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/installing_epas_using_local_repository.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/installing_epas_using_local_repository.mdx
@@ -11,17 +11,7 @@ If the server on which you want to install EDB Postgres Advanced Server or the s
 
 To create and use a local repository, you must:
 
--   Use yum or dnf to install the `epel-release`, `yum-utils`, and `createrepo` packages.
-
-    On RHEL or CentOS 7.x:
-
-    ```bash
-    yum install epel-release
-    yum install yum-utils
-    yum install createrepo
-    ```
-
-    On RHEL or Rocky Linux or AlmaLinux 8.x:
+-   Use dnf to install the `epel-release`, `yum-utils`, and `createrepo` packages.
 
     ```bash
     dnf install epel-release
@@ -56,18 +46,10 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use yum or dnf commands to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum -y install edb-as15-server
-    ```
+After specifying the location and connection information for your local repository, you can use the dnf command to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example:
 
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
     ```text
     dnf -y install edb-as15-server
     ```
-
-For more information about creating a local yum repository, see the [Centos wiki](https://wiki.centos.org/HowTos/CreateLocalRepos).
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
index 06d347e40f6..dd03acee28c 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
@@ -9,15 +9,15 @@ The packages that install the database server component create a unit file on ve
 The PostgreSQL `initdb` command creates a database cluster. When installing EDB Postgres Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing EDB Postgres Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the systemd service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the systemd service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
 For more information, see the [`initdb` documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service. The steps are platform specific.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux 8.x system with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -37,7 +37,7 @@ After creating the cluster, use `systemctl` to start, stop, or restart the servi
 systemctl { start | stop | restart } edb-as-15
 ```
 
-### On Debian 10.x or Ubuntu 18.04 | 20.04
+### On Ubuntu 20.04
 
 You can initialize multiple clusters using the bundled scripts. To create a new cluster, assume root privileges, and invoke the bundled script:
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
index 1406e794994..7dc2e756838 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
@@ -2,9 +2,9 @@
 title: "Modifying the data directory location"
 ---
 
-## On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+## On RHEL/Rocky Linux/AlmaLinux 8.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-<xx>.service`, where `<xx>` is the EDB Postgres Advanced Server version. It resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. Avoid making any modifications directly to the unit file because they might be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-<xx>.service`, where `<xx>` is the EDB Postgres Advanced Server version. It resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. Avoid making any modifications directly to the unit file because they might be overwritten during package upgrades.
 
 By default, data files reside under the `/var/lib/edb/as15/data` directory. To use a data directory that resides in a nondefault location:
 
@@ -33,7 +33,7 @@ By default, data files reside under the `/var/lib/edb/as15/data` directory. To u
     systemctl start edb-as-15
     ```
 
-## Configuring SELinux policy to change the data directory location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+## Configuring SELinux policy to change the data directory location on RHEL/Rocky Linux/AlmaLinux 8.x
 
 By default, the data files reside under the `/var/lib/edb/as15/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy:
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
index 542760cdd1e..23047a75746 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
@@ -19,9 +19,9 @@ The following table lists the names of the services that control EDB Postgres Ad
 
 You can use the Linux command line to control the EDB Postgres Advanced Server database server and the services of EDB Postgres Advanced Server's supporting components. The commands that control the EDB Postgres Advanced Server service on a Linux platform are host specific.
 
-## Controlling a service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+## Controlling a service on RHEL/Rocky Linux/AlmaLinux 8.x
 
-If your installation of EDB Postgres Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
+If your installation of EDB Postgres Advanced Server resides on version 8.x of RHEL, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path, and you must invoke it with superuser privileges. To use the command, at the command line, enter:
 
@@ -40,9 +40,9 @@ Where:
 -   `restart` to stop and then start the service.
 -   `status` to discover the current status of the service.
 
-## Controlling a service on Debian 10.x or Ubuntu 18.04 | 20.04
+## Controlling a service on Ubuntu 20.04
 
-If your installation of EDB Postgres Advanced Server resides on version 18.04 | 20.04 of Ubuntu, assume superuser privileges and invoke the following commands using bundled scripts to manage the service. Use the following commands to:
+If your installation of EDB Postgres Advanced Server resides on version 20.04 of Ubuntu, assume superuser privileges and invoke the following commands using bundled scripts to manage the service. Use the following commands to:
 
 -   Discover the current status of a service:
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
index 85255ec38f5..fd4e1d8a4b0 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
@@ -4,9 +4,9 @@ title: "Starting multiple postmasters with different clusters"
 
 You can configure EDB Postgres Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are specific to the version of the Linux host.
 
-## On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+## On RHEL/Rocky Linux/AlmaLinux 8.x
 
-The `edb-as15-server-core` RPM for version 7.x | 8.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services with unique `data` directories and monitor different ports. You need root access to invoke or modify the script.
+The `edb-as15-server-core` RPM for version 8.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services with unique `data` directories and monitor different ports. You need root access to invoke or modify the script.
 
 This example creates an EDB Postgres Advanced Server installation with two instances. The secondary instance is named `secondary`.
 
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/15/installing/linux_install_details/rpm_packages.mdx
index 25943fab27e..b5ff863a9ef 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/rpm_packages.mdx
@@ -7,22 +7,14 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations. See:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES packages
+## RHEL/Rocky Linux/AlmaLinux/SLES packages
 
 ### EDB Postgres Advanced Server RPM packages
 
-The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
-
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
-
-On RHEL or Rocky Linux or AlmaLinux 8:
+The tables that follow list the RPM packages that are available from EDB. You can also use the `dnf search` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
 
 ```text
 dnf search <package>
diff --git a/product_docs/docs/epas/15/installing/linux_install_details/updating_an_rpm_installation.mdx b/product_docs/docs/epas/15/installing/linux_install_details/updating_an_rpm_installation.mdx
index 3f62f904a37..bc151798fca 100644
--- a/product_docs/docs/epas/15/installing/linux_install_details/updating_an_rpm_installation.mdx
+++ b/product_docs/docs/epas/15/installing/linux_install_details/updating_an_rpm_installation.mdx
@@ -3,39 +3,21 @@ title: "Updating an RPM installation"
 description: "Describes how to upgrade your repository configuration file and update to a more recent product version"
 ---
 
-If you have an existing EDB Postgres Advanced Server RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. 
+If you have an existing EDB Postgres Advanced Server RPM installation, you can use dnf to upgrade your repository configuration file and update to a more recent product version. 
 
 To update the `edb.repo` file, assume superuser privileges and enter:
 
--   On RHEL or CentOS 7:
+```text
+dnf upgrade edb-repo
+```
 
-    ```text
-    yum upgrade edb-repo
-    ```
+dnf updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use dnf to upgrade all packages whose names include the expression `edb`:
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf upgrade edb-repo
-    ```
-
-yum or dnf updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade all packages whose names include the expression `edb`:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf upgrade edb*
-    ```
+```text
+dnf upgrade edb*
+```
 
 !!! Note
-    The `yum upgrade` or `dnf upgrade` commands perform an update only between minor releases. To update between major releases, use `pg_upgrade`.
-
-For more information about using yum commands and options, enter `yum --help` at the command line.
+    The `dnf upgrade` command performs an update only between minor releases. To update between major releases, use `pg_upgrade`.
 
 For more information about using dnf commands and options, see the [dnf documentation](https://docs.fedoraproject.org/en-US/quick-docs/dnf/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index 1e8115b03cb..00000000000
--- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb
-
-sudo systemctl start edb-as-15
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index 6ae29f774d5..00000000000
--- a/product_docs/docs/epas/15/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb
-
-sudo systemctl start edb-as-15
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx
index 39f9f238856..fe98633741a 100644
--- a/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/15/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index e7731bf035e..00000000000
--- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb
-
-sudo systemctl start edb-as-15
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index c1368714c53..00000000000
--- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index 03fe2095e80..00000000000
--- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb
-
-sudo systemctl start edb-as-15
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index 314e526663e..00000000000
--- a/product_docs/docs/epas/15/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 15, the package name would be `edb-as15-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb
-
-sudo systemctl start edb-as-15
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (15.0.0, server 15.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx
index 1089e690691..a1e91999eea 100644
--- a/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/15/installing/linux_x86_64/index.mdx
@@ -14,16 +14,12 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -65,5 +53,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](epas_ubuntu_20)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx b/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
index c3541a7761a..6f81f9121e3 100644
--- a/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
+++ b/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
@@ -8,9 +8,9 @@ redirects:
 
 You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps can be produced on demand, such as by a debugger, or upon termination.
 
-## Enabling core dumps on a RHEL or CentOS or Rocky Linux or AlmaLinux host
+## Enabling core dumps on a RHEL or Rocky Linux or AlmaLinux host
 
-On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation:
+On RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
@@ -117,9 +117,9 @@ On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disa
     (gdb) bt full
     ```
 
-## Enabling core dumps on a Debian or Ubuntu host
+## Enabling core dumps on a Ubuntu host
 
-On Debian 10 or Ubuntu 18 and 20, core file creation is disabled by default. To enable the core file generation:
+On Ubuntu 20, core file creation is disabled by default. To enable the core file generation:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
diff --git a/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx b/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
index 792a90fd3b4..a3e98bcd1f4 100644
--- a/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
+++ b/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
@@ -20,11 +20,9 @@ If you encounter a similar message, confirm that the data directory is empty. Th
 
 ### Difficulty installing the EPEL release package
 
-If you have difficulty installing the EPEL release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x:
+If you have difficulty installing the EPEL release package, you can use the following command to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x:
 
 ```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 ```
 
diff --git a/product_docs/docs/epas/15/installing/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/15/installing/uninstalling/linux_uninstall.mdx
index 906b7d37e53..9bffc6b1436 100644
--- a/product_docs/docs/epas/15/installing/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/15/installing/uninstalling/linux_uninstall.mdx
@@ -13,9 +13,9 @@ legacyRedirects:
 !!! Note
     After uninstalling EDB Postgres Advanced Server, the cluster data files remain intact, and the service user persists. You can manually remove the cluster `data` and service user from the system.
 
-## Uninstalling on RHEL/OL/AlmaLinux/Rocky Linux
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
 
-You can use variations of the `rpm`, `yum`, or `dnf` command to remove installed packages. Removing a package doesn't damage the EDB Postgres Advanced Server `data` directory.
+You can use variations of the `rpm` or `dnf` command to remove installed packages. Removing a package doesn't damage the EDB Postgres Advanced Server `data` directory.
 
 Include the `-e` option when invoking the `rpm` command to remove an installed package:
 
@@ -25,19 +25,11 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you want to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by yum or dnf. To remove a package, at the command line, assume superuser privileges, and enter the appropriate command.
+You can use the `dnf remove` command to remove a package installed or dnf. To remove a package, at the command line, assume superuser privileges, and enter:
 
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove <package_name>
-    ```
+```text
+dnf remove <package_name>
+```
 
 Where `package_name` is the name of the package that you want to remove.
 
@@ -46,21 +38,14 @@ yum and rpm don't remove a package that's required by another package. If you at
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that aren't required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
-To uninstall EDB Postgres Advanced Server and its dependent packages, use the appropriate command.
+To uninstall EDB Postgres Advanced Server and its dependent packages, enter:
 
--   On RHEL or CentOS 7:
+```text
+dnf remove edb-as<xx>-server*
+```
 
-    ```text
-    yum remove edb-as<xx>-server*
-    ```
 Where `<xx>` is the EDB Postgres Advanced Server version number.
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf remove edb-as<xx>-server*
-    ```
-
 ## Uninstalling on Debian or Ubuntu
 
 -   To uninstall EDB Postgres Advanced Server, invoke the following command. The configuration files and data directory remains intact.
diff --git a/product_docs/docs/epas/15/managing_performance/02_index_advisor/installing_index_advisor.mdx b/product_docs/docs/epas/15/managing_performance/02_index_advisor/installing_index_advisor.mdx
index 756d3ed6110..03e58858727 100644
--- a/product_docs/docs/epas/15/managing_performance/02_index_advisor/installing_index_advisor.mdx
+++ b/product_docs/docs/epas/15/managing_performance/02_index_advisor/installing_index_advisor.mdx
@@ -15,7 +15,6 @@ Install Index Advisor using the following command:
       | Package manager | Operating system                 |
       | --------------- | -------------------------------- |
       | dnf             | RHEL 8/9 and derivatives         |
-      | yum             | RHEL 7 and derivatives, CentOS 7 |
       | apt-get         | Debian 10/11 and derivatives     |
 
     
diff --git a/product_docs/docs/epas/15/planning/planning_prerequisites/epas_limitations/index.mdx b/product_docs/docs/epas/15/planning/planning_prerequisites/epas_limitations/index.mdx
index 632bd49318f..6af15f2f842 100644
--- a/product_docs/docs/epas/15/planning/planning_prerequisites/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/15/planning/planning_prerequisites/epas_limitations/index.mdx
@@ -8,4 +8,4 @@ redirects:
 The following limitations apply when implementing EDB Postgres Advanced Server:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported only on RHEL or CentOS x86. 
+-   The LLVM JIT package is supported only on RHEL x86. 
diff --git a/product_docs/docs/epas/16/installing/index.mdx b/product_docs/docs/epas/16/installing/index.mdx
index 6d1ac3ff4a7..254c2681d1d 100644
--- a/product_docs/docs/epas/16/installing/index.mdx
+++ b/product_docs/docs/epas/16/installing/index.mdx
@@ -27,35 +27,33 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8), [RHEL 7](linux_x86_64/epas_rhel_7)
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/epas_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
 
-- [CentOS 7](linux_x86_64/epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/epas_sles_15), [SLES 12](linux_x86_64/epas_sles_12)
+- [SLES 15](linux_x86_64/epas_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
 
-- [Debian 12](linux_x86_64/epas_debian_12), [Debian 11](linux_x86_64/epas_debian_11), [Debian 10](linux_x86_64/epas_debian_10)
+- [Debian 12](linux_x86_64/epas_debian_12), [Debian 11](linux_x86_64/epas_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8), [RHEL 7](linux_ppc64le/epas_rhel_7)
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/epas_sles_15), [SLES 12](linux_ppc64le/epas_sles_12)
+- [SLES 15](linux_ppc64le/epas_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
index b56ea8decf6..c251989554f 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
@@ -7,10 +7,10 @@ redirects:
 
 The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES locations](#rhelolrocky-linuxalmalinuxcentossles-locations)
+- [RHEL/Rocky Linux/AlmaLinux/SLES locations](#rhelrocky-linuxalmalinuxsles-locations)
 - [Debian/Ubuntu locations](#debianubuntu-locations)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
 
 The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table.
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx b/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
index aaa351e8655..53d38026d3b 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
@@ -11,15 +11,7 @@ If the server on which you want to install EDB Postgres Advanced Server or the s
 
 To create and use a local repository, you must:
 
--   Use yum or dnf to install the `epel-release`, `yum-utils`, and `createrepo` packages.
-
-    On RHEL or CentOS 7.x:
-
-    ```bash
-    yum install epel-release
-    yum install yum-utils
-    yum install createrepo
-    ```
+-   Use `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
 
     On RHEL or Rocky Linux or AlmaLinux 8.x:
 
@@ -56,18 +48,10 @@ To create and use a local repository, you must:
     gpgcheck=0
     ```
 
-After specifying the location and connection information for your local repository, you can use yum or dnf commands to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example:
-
--   On RHEL or CentOS 7:
+After specifying the location and connection information for your local repository, you can use the dnf command to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example, on RHEL or Rocky Linux or AlmaLinux 8:
 
-    ```text
-    yum -y install edb-as16-server
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf -y install edb-as16-server
-    ```
+```text
+dnf -y install edb-as16-server
+```
 
 For more information about creating a local yum repository, see the [Centos wiki](https://wiki.centos.org/HowTos/CreateLocalRepos).
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
index 55ebe6bb9f9..4de069cff88 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
@@ -9,15 +9,15 @@ The packages that install the database server component create a unit file on ve
 The PostgreSQL `initdb` command creates a database cluster. When installing EDB Postgres Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing EDB Postgres Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
 
 -   Specify environment options on the command line.
--   Include the systemd service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+-   Include the systemd service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
 
 For more information, see the [`initdb` documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
 
 After specifying any options in the service configuration file, you can create the database cluster and start the service. The steps are platform specific.
 
-### On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x
+### On RHEL/Rocky Linux/AlmaLinux 8.x
 
-To invoke `initdb` on a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux 8.x system with the options specified in the service configuration file, assume the identity of the operating system superuser:
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system with the options specified in the service configuration file, assume the identity of the operating system superuser:
 
 ```text
 su - root
@@ -37,7 +37,7 @@ After creating the cluster, use `systemctl` to start, stop, or restart the servi
 systemctl { start | stop | restart } edb-as-16
 ```
 
-### On Debian 10.x | 11.x or Ubuntu 20.04 | 22.04
+### On Debian 11.x or Ubuntu 20.04 | 22.04
 
 You can initialize multiple clusters using the bundled scripts. To create a new cluster, assume root privileges, and invoke the bundled script:
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
index 9701b25d933..be18b1e31f8 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
@@ -2,9 +2,9 @@
 title: "Modifying the data directory location"
 ---
 
-## On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+## On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
 
-On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x or 9.x host, the unit file is named `edb-as-<xx>.service`, where `<xx>` is the EDB Postgres Advanced Server version. It resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. Avoid making any modifications directly to the unit file because they might be overwritten during package upgrades.
+On a RHEL/Rocky Linux/AlmaLinux 8.x or 9.x host, the unit file is named `edb-as-<xx>.service`, where `<xx>` is the EDB Postgres Advanced Server version. It resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. Avoid making any modifications directly to the unit file because they might be overwritten during package upgrades.
 
 By default, data files reside under the `/var/lib/edb/as16/data` directory. To use a data directory that resides in a nondefault location:
 
@@ -33,7 +33,7 @@ By default, data files reside under the `/var/lib/edb/as16/data` directory. To u
     systemctl start edb-as-16
     ```
 
-## Configuring SELinux policy to change the data directory location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+## Configuring SELinux policy to change the data directory location on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
 
 By default, the data files reside under the `/var/lib/edb/as16/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy:
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
index 833b1d1ef1f..8986d9b6f4d 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
@@ -19,9 +19,9 @@ The following table lists the names of the services that control EDB Postgres Ad
 
 You can use the Linux command line to control the EDB Postgres Advanced Server database server and the services of EDB Postgres Advanced Server's supporting components. The commands that control the EDB Postgres Advanced Server service on a Linux platform are host specific.
 
-## Controlling a service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+## Controlling a service on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
 
-If your installation of EDB Postgres Advanced Server resides on version 7.x | 8.x | 9.x of RHEL and CentOS, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
+If your installation of EDB Postgres Advanced Server resides on version 8.x | 9.x of RHEL, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
 
 The `systemctl` command must be in your search path, and you must invoke it with superuser privileges. To use the command, at the command line, enter:
 
@@ -40,9 +40,9 @@ Where:
 -   `restart` to stop and then start the service.
 -   `status` to discover the current status of the service.
 
-## Controlling a service on Debian 10.x | 11.x or Ubuntu 20.04 | 22.04
+## Controlling a service on Debian 11.x or Ubuntu 20.04 | 22.04
 
-If your installation of EDB Postgres Advanced Server resides on version 10.x | 11.x of Debian or 20.04 | 22.04 of Ubuntu, assume superuser privileges and invoke the following commands using bundled scripts to manage the service. Use the following commands to:
+If your installation of EDB Postgres Advanced Server resides on version 11.x of Debian or 20.04 | 22.04 of Ubuntu, assume superuser privileges and invoke the following commands using bundled scripts to manage the service. Use the following commands to:
 
 -   Discover the current status of a service:
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
index 09291176d08..eb00c38e798 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
@@ -4,9 +4,9 @@ title: "Starting multiple postmasters with different clusters"
 
 You can configure EDB Postgres Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are specific to the version of the Linux host.
 
-## On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+## On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
 
-The `edb-as16-server-core` RPM for version 7.x | 8.x | 9.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services with unique `data` directories and monitor different ports. You need root access to invoke or modify the script.
+The `edb-as16-server-core` RPM for version 8.x | 9.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services with unique `data` directories and monitor different ports. You need root access to invoke or modify the script.
 
 This example creates an EDB Postgres Advanced Server installation with two instances. The secondary instance is named `secondary`.
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
index ed2aee09545..213dc7d35e4 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
@@ -7,20 +7,14 @@ redirects:
 
 EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations. See:
 
-- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES packages](#rhelolrocky-linuxalmalinuxcentossles-packages)
+- [RHEL/Rocky Linux/AlmaLinux/SLES packages](#rhelrocky-linuxalmalinuxsles-packages)
 - [Debian/Ubuntu packages](#debianubuntu-packages)
 
-## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES packages
+## RHEL/Rocky Linux/AlmaLinux/SLES packages
 
 ### EDB Postgres Advanced Server RPM packages
 
-The tables that follow list the RPM packages that are available from EDB. You can also use the `yum search` or `dnf search` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
-
-On RHEL or CentOS 7:
-
-```text
-yum search <package>
-```
+The tables that follow list the RPM packages that are available from EDB. You can also use the `dnf search` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
 
 On RHEL or Rocky Linux or AlmaLinux 8:
 
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx b/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
index 3f62f904a37..7bf129adabe 100644
--- a/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
+++ b/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
@@ -7,35 +7,17 @@ If you have an existing EDB Postgres Advanced Server RPM installation, you can u
 
 To update the `edb.repo` file, assume superuser privileges and enter:
 
--   On RHEL or CentOS 7:
+```text
+dnf upgrade edb-repo
+```
 
-    ```text
-    yum upgrade edb-repo
-    ```
+`dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `dnf` to upgrade all packages whose names include the expression `edb`:
 
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf upgrade edb-repo
-    ```
-
-yum or dnf updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade all packages whose names include the expression `edb`:
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum upgrade edb*
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-    ```text
-    dnf upgrade edb*
-    ```
+```text
+dnf upgrade edb*
+```
 
 !!! Note
-    The `yum upgrade` or `dnf upgrade` commands perform an update only between minor releases. To update between major releases, use `pg_upgrade`.
-
-For more information about using yum commands and options, enter `yum --help` at the command line.
+    The `dnf upgrade` command performs an update only between minor releases. To update between major releases, use `pg_upgrade`.
 
 For more information about using dnf commands and options, see the [dnf documentation](https://docs.fedoraproject.org/en-US/quick-docs/dnf/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_7.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_7.mdx
deleted file mode 100644
index fa9410e6873..00000000000
--- a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_7.mdx
+++ /dev/null
@@ -1,151 +0,0 @@
----
-navTitle: RHEL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel7_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel7_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-- Refresh the cache:
-  ```shell
-  sudo dnf makecache
-  ```
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 16, the package name is `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as16`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
-
-sudo systemctl start edb-as-16
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_12.mdx
deleted file mode 100644
index dc74ddfd3f4..00000000000
--- a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
-
-sudo systemctl start edb-as-16
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
index b8622dde56f..3cf00fbf03f 100644
--- a/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
@@ -14,9 +14,7 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_sles_15
-  - epas_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,10 +25,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
-
-- [SLES 12](epas_sles_12)
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_centos_7.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_centos_7.mdx
deleted file mode 100644
index c13ae1c14a9..00000000000
--- a/product_docs/docs/epas/16/installing/linux_x86_64/epas_centos_7.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Advanced Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_centos7_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 16, the package name is `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as16`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
-
-sudo systemctl start edb-as-16
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_10.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_10.mdx
deleted file mode 100644
index 4b4c7ec15da..00000000000
--- a/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_10.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Advanced Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb10_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 16, the package name is `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo apt-get -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_7.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_7.mdx
deleted file mode 100644
index 6b8b8347f9a..00000000000
--- a/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_7.mdx
+++ /dev/null
@@ -1,149 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Advanced Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel7_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 16, the package name is `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo yum -y install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as16`.
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
-
-sudo systemctl start edb-as-16
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_12.mdx
deleted file mode 100644
index d1ea27afc13..00000000000
--- a/product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_12.mdx
+++ /dev/null
@@ -1,147 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-server
-```
-
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
-
-To install an individual component:
-
-```shell
-sudo zypper -n install <package_name>
-```
-
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode).
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
-
-sudo systemctl start edb-as-16
-```
-
-To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo su - enterprisedb
-
-psql edb
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE enterprisedb IDENTIFIED BY password;
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-psql (16.0.0, server 16.0.0)
-You are now connected to database "hr" as user "enterprisedb".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
index 571a9fba22c..5d06a808c66 100644
--- a/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
@@ -14,17 +14,13 @@ redirects:
 navigation:
   - epas_rhel_9
   - epas_rhel_8
-  - epas_rhel_7
   - epas_other_linux_9
   - epas_other_linux_8
-  - epas_centos_7
   - epas_sles_15
-  - epas_sles_12
   - epas_ubuntu_22
   - epas_ubuntu_20
   - epas_debian_12
   - epas_debian_11
-  - epas_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -35,14 +31,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](epas_rhel_8)
 
-- [RHEL 7](epas_rhel_7)
-
 - [Oracle Linux (OL) 9](epas_rhel_9)
 
 - [Oracle Linux (OL) 8](epas_rhel_8)
 
-- [Oracle Linux (OL) 7](epas_rhel_7)
-
 - [Rocky Linux 9](epas_other_linux_9)
 
 - [Rocky Linux 8](epas_other_linux_8)
@@ -51,14 +43,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](epas_other_linux_8)
 
-- [CentOS 7](epas_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](epas_sles_15)
 
-- [SLES 12](epas_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](epas_ubuntu_22)
@@ -68,5 +56,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](epas_debian_12)
 
 - [Debian 11](epas_debian_11)
-
-- [Debian 10](epas_debian_10)
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
index 013330e3e0d..dd0b9a6606e 100644
--- a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
+++ b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
@@ -8,9 +8,9 @@ redirects:
 
 You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps can be produced on demand, such as by a debugger, or upon termination.
 
-## Enabling core dumps on a RHEL or CentOS or Rocky Linux or AlmaLinux host
+## Enabling core dumps on a RHEL or Rocky Linux or AlmaLinux host
 
-On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x, core file creation is disabled by default. To enable the core file generation:
+On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x, core file creation is disabled by default. To enable the core file generation:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
@@ -119,7 +119,7 @@ On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x | 9.x, core file creation i
 
 ## Enabling core dumps on a Debian or Ubuntu host
 
-On Debian 10 or 11 or Ubuntu 20 and 22, core file creation is disabled by default. To enable the core file generation:
+On Debian 11 or Ubuntu 20 and 22, core file creation is disabled by default. To enable the core file generation:
 
 -   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
 
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
index 58082af8118..c927aa8a210 100644
--- a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
+++ b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
@@ -20,11 +20,9 @@ If you encounter a similar message, confirm that the data directory is empty. Th
 
 ### Difficulty installing the EPEL release package
 
-If you have difficulty installing the EPEL release package, you can use one of the following commands to install the `epel-release` package on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x | 9.x:
+If you have difficulty installing the EPEL release package, you can use one of the following commands to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x:
 
 ```text
-yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 
 dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
diff --git a/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
index c228cfc5f42..b070008d1bc 100644
--- a/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
+++ b/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
@@ -13,9 +13,9 @@ legacyRedirects:
 !!! Note
     After uninstalling EDB Postgres Advanced Server, the cluster data files remain intact, and the service user persists. You can manually remove the cluster `data` and service user from the system.
 
-## Uninstalling on RHEL/OL/AlmaLinux/Rocky Linux
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
 
-You can use variations of the `rpm`, `yum`, or `dnf` command to remove installed packages. Removing a package doesn't damage the EDB Postgres Advanced Server `data` directory.
+You can use  `dnf` command to remove installed packages. Removing a package doesn't damage the EDB Postgres Advanced Server `data` directory.
 
 Include the `-e` option when invoking the `rpm` command to remove an installed package:
 
@@ -25,15 +25,7 @@ rpm -e <package_name>
 
 Where `package_name` is the name of the package that you want to remove.
 
-You can use the `yum remove` or `dnf remove` command to remove a package installed by yum or dnf. To remove a package, at the command line, assume superuser privileges, and enter the appropriate command.
-
--   On RHEL or CentOS 7:
-
-    ```text
-    yum remove <package_name>
-    ```
-
--   On RHEL or Rocky Linux or AlmaLinux 8 or 9:
+You can use the `dnf remove` command to remove a package installed by dnf. To remove a package, at the command line, assume superuser privileges, and enter:
 
     ```text
     dnf remove <package_name>
@@ -46,20 +38,14 @@ yum and rpm don't remove a package that's required by another package. If you at
 !!! Note
     In RHEL or Rocky Linux or AlmaLinux 8 or 9, removing a package also removes all its dependencies that aren't required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8 or 9, disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
 
-To uninstall EDB Postgres Advanced Server and its dependent packages, use the appropriate command.
+To uninstall EDB Postgres Advanced Server and its dependent packages, enter:
 
--   On RHEL or CentOS 7:
+```text
+dnf remove edb-as<xx>-server*
+```
 
-    ```text
-    yum remove edb-as<xx>-server*
-    ```
 Where `<xx>` is the EDB Postgres Advanced Server version number.
 
--   On RHEL or Rocky Linux or AlmaLinux 8 or 9:
-
-    ```text
-    dnf remove edb-as<xx>-server*
-    ```
 
 ## Uninstalling on Debian or Ubuntu
 
diff --git a/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
index 632bd49318f..6af15f2f842 100644
--- a/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
+++ b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
@@ -8,4 +8,4 @@ redirects:
 The following limitations apply when implementing EDB Postgres Advanced Server:
 
 -   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
--   The LLVM JIT package is supported only on RHEL or CentOS x86. 
+-   The LLVM JIT package is supported only on RHEL x86. 
diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx
index 4c6575efa70..536b70fd9cb 100644
--- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx
+++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx
@@ -106,7 +106,7 @@ Shutting down loopback interface:                          [  OK  ]
 Bringing up loopback interface:                            [  OK  ]
 ```
 
-Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
+Use the following command for RHEL/Rocky Linux/AlmaLinux or and later:
 
 `systemctl restart network`
 
diff --git a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx
index 27b501d839a..47b0441a770 100644
--- a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx
+++ b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx
@@ -13,9 +13,9 @@ It's important that you record the login information for the publication server.
    !!! Note
        If you're using Oracle publication or subscription databases, and the publication server wasn't restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, restart the publication server.
 
-   **For Linux only:** You can verify the publication server is running by using the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux, AlmaLinux, or RHEL 8, and the service command for previous Linux versions.
+   **For Linux only:** You can verify the publication server is running by using the `systemctl` command for RHEL/Rocky Linux/AlmaLinux 8.x or later, and the service command for previous Linux versions.
 
-   Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
+   Use the following command for Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
 
    ```shell
    systemctl status edb-xdbpubserver
@@ -29,7 +29,7 @@ It's important that you record the login information for the publication server.
 
    If the publication server is running and you want to restart it, use the `restart` option.
 
-   For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
+   For RHEL/Rocky Linux/AlmaLinux 8.x or later:
 
    ```shell
    systemctl restart edb-xdbpubserver
@@ -43,7 +43,7 @@ It's important that you record the login information for the publication server.
 
    If the publication server isn't running, use the `start` option.
 
-   For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
+   For RHEL/Rocky Linux/AlmaLinux 8.x or later:
 
    ```shell
    systemctl start edb-xdbpubserver
diff --git a/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx
index 14a1ebcee51..a1bbd918f0f 100644
--- a/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx
+++ b/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx
@@ -13,7 +13,7 @@ It's important that you record the login information for the subscription server
    !!! Note
        If you're using Oracle publication or subscription databases and the subscription server wasn't restarted after copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, restart the subscription server.
 
-   **For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used.
+   **For Linux only:** Use the `systemctl` command for RHEL/Rocky Linux/AlmaLinux 8.x or later, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used.
 
    **For Windows only:** Open **Control Panel > System and Security > Administrative Tools > Services**. Use the **Start** or **Restart** link for the service named Subscription Service for Replication Server.
 
diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx
index 296a1c34ce0..252fb6dcd1b 100644
--- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx
+++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx
@@ -63,7 +63,7 @@ To set the configuration options:
 
 1.  Restart the publication or subscription server.
 
-    Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:
+    Use the following command for RHEL/Rocky Linux/AlmaLinux 8.x or later:
 
     `systemctl restart edb-xdbpubserver`
 
diff --git a/product_docs/docs/eprs/7/installing/index.mdx b/product_docs/docs/eprs/7/installing/index.mdx
index cba5c517784..5b11dbf6dd8 100644
--- a/product_docs/docs/eprs/7/installing/index.mdx
+++ b/product_docs/docs/eprs/7/installing/index.mdx
@@ -28,25 +28,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/eprs_rhel_9), [RHEL 8](linux_x86_64/eprs_rhel_8), [RHEL 7](linux_x86_64/eprs_rhel_7)
+- [RHEL 9](linux_x86_64/eprs_rhel_9), [RHEL 8](linux_x86_64/eprs_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/eprs_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/eprs_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/eprs_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/eprs_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/eprs_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/eprs_other_linux_9), [Rocky Linux 8](linux_x86_64/eprs_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/eprs_other_linux_9), [AlmaLinux 8](linux_x86_64/eprs_other_linux_8)
 
-- [CentOS 7](linux_x86_64/eprs_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/eprs_sles_15), [SLES 12](linux_x86_64/eprs_sles_12)
+- [SLES 15](linux_x86_64/eprs_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/eprs_ubuntu_22), [Ubuntu 20.04](linux_x86_64/eprs_ubuntu_20)
 
-- [Debian 11](linux_x86_64/eprs_debian_11), [Debian 10](linux_x86_64/eprs_debian_10)
+- [Debian 11](linux_x86_64/eprs_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -56,7 +54,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/eprs_sles_15), [SLES 12](linux_ppc64le/eprs_sles_12)
+- [SLES 15](linux_ppc64le/eprs_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/eprs/7/installing/installation_details.mdx b/product_docs/docs/eprs/7/installing/installation_details.mdx
index 4884ed3d3d7..3df81aea3ea 100644
--- a/product_docs/docs/eprs/7/installing/installation_details.mdx
+++ b/product_docs/docs/eprs/7/installing/installation_details.mdx
@@ -30,9 +30,9 @@ During the configuration process, you might need the following files that are cr
 | `edb-repl.conf` (Linux)            | `/etc`                                | EPRS Replication Configuration file                                                   |
 | `edb-repl.conf` (Windows)          | `XDB_HOME\etc`                        | EPRS Replication Configuration file                                                   |
 | `edb-xdbpubserver` (Linux)         | `/etc/init.d`                         | Start, stop, or restart the publication server                                       |
-| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system`             | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8)  |
+| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system`             | Start, stop, or restart the publication server (RHEL/Rocky Linux/AlmaLinux 8.x or later)  |
 | `edb-xdbsubserver` (Linux)         | `/etc/init.d`                         | Start, stop, or restart the subscription server                                      |
-| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system`             | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) |
+| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system`             | Start, stop, or restart the subscription server (RHEL/Rocky Linux/AlmaLinux 8.x or later) |
 | `xdb_pubserver.conf`               | `XDB_HOME/etc`                        | Publication server configuration file                                                |
 | `xdb_subserver.conf`               | `XDB_HOME/etc`                        | Subscription server configuration file                                               |
 | `xdbReplicationServer-xx.config`   | `XDB_HOME/etc/sysconfig`              | Replication Server Startup Configuration file                                                       |
diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx
deleted file mode 100644
index 069cd58bd0b..00000000000
--- a/product_docs/docs/eprs/7/installing/linux_ppc64le/eprs_sles_12.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Replication Server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages.
-
-To install all Replication Server components:
-
-```shell
-sudo zypper  -y install edb-xdb
-```
-
-To install an individual component:
-
-```shell
-sudo zypper  -y install <package_name>
-```
-
-Where `<package_name>` is:
-
-| Package name         | Component                                                             |
-| -------------------- | --------------------------------------------------------------------- |
-| `edb-xdb-console`    | Replication console and the Replication Server command line interface |
-| `edb-xdb-publisher`  | Publication server                                                    |
-| `edb-xdb-subscriber` | Subscription server                                                   |
-
-## Initial configuration
-
-Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/installing/installing_jdbc_driver) for details.
diff --git a/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx b/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx
index db9f2bed46f..722dc8fb9ee 100644
--- a/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/eprs/7/installing/linux_ppc64le/index.mdx
@@ -14,7 +14,6 @@ navigation:
   - eprs_rhel_9
   - eprs_rhel_8
   - eprs_sles_15
-  - eprs_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,5 +27,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](eprs_sles_15)
-
-- [SLES 12](eprs_sles_12)
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx
deleted file mode 100644
index d3e2a191eff..00000000000
--- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_centos_7.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Replication Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages.
-
-To install all Replication Server components:
-
-```shell
-sudo yum  -y install edb-xdb
-```
-
-To install an individual component:
-
-```shell
-sudo yum  -y install <package_name>
-```
-
-Where `<package_name>` is:
-
-| Package name         | Component                                                             |
-| -------------------- | --------------------------------------------------------------------- |
-| `edb-xdb-console`    | Replication console and the Replication Server command line interface |
-| `edb-xdb-publisher`  | Publication server                                                    |
-| `edb-xdb-subscriber` | Subscription server                                                   |
-
-## Initial configuration
-
-Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/installing/installing_jdbc_driver) for details.
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx
deleted file mode 100644
index da7d4d2f83a..00000000000
--- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_debian_10.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Replication Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages.
-
-To install all Replication Server components:
-
-```shell
-sudo apt-get  -y install edb-xdb
-```
-
-To install an individual component:
-
-```shell
-sudo apt-get  -y install <package_name>
-```
-
-Where `<package_name>` is:
-
-| Package name         | Component                                                             |
-| -------------------- | --------------------------------------------------------------------- |
-| `edb-xdb-console`    | Replication console and the Replication Server command line interface |
-| `edb-xdb-publisher`  | Publication server                                                    |
-| `edb-xdb-subscriber` | Subscription server                                                   |
-
-## Initial configuration
-
-Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/installing/installing_jdbc_driver) for details.
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx
deleted file mode 100644
index 1289fed40e2..00000000000
--- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_rhel_7.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Replication Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages.
-
-To install all Replication Server components:
-
-```shell
-sudo yum  -y install edb-xdb
-```
-
-To install an individual component:
-
-```shell
-sudo yum  -y install <package_name>
-```
-
-Where `<package_name>` is:
-
-| Package name         | Component                                                             |
-| -------------------- | --------------------------------------------------------------------- |
-| `edb-xdb-console`    | Replication console and the Replication Server command line interface |
-| `edb-xdb-publisher`  | Publication server                                                    |
-| `edb-xdb-subscriber` | Subscription server                                                   |
-
-## Initial configuration
-
-Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/installing/installing_jdbc_driver) for details.
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx
deleted file mode 100644
index e6239326df1..00000000000
--- a/product_docs/docs/eprs/7/installing/linux_x86_64/eprs_sles_12.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Replication Server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages.
-
-To install all Replication Server components:
-
-```shell
-sudo zypper  -n install edb-xdb
-```
-
-To install an individual component:
-
-```shell
-sudo zypper  -n install <package_name>
-```
-
-Where `<package_name>` is:
-
-| Package name         | Component                                                             |
-| -------------------- | --------------------------------------------------------------------- |
-| `edb-xdb-console`    | Replication console and the Replication Server command line interface |
-| `edb-xdb-publisher`  | Publication server                                                    |
-| `edb-xdb-subscriber` | Subscription server                                                   |
-
-## Initial configuration
-
-Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/installing/installing_jdbc_driver) for details.
diff --git a/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx b/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx
index b928e427262..0eba1ff3758 100644
--- a/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/eprs/7/installing/linux_x86_64/index.mdx
@@ -13,16 +13,12 @@ redirects:
 navigation:
   - eprs_rhel_9
   - eprs_rhel_8
-  - eprs_rhel_7
   - eprs_other_linux_9
   - eprs_other_linux_8
-  - eprs_centos_7
   - eprs_sles_15
-  - eprs_sles_12
   - eprs_ubuntu_22
   - eprs_ubuntu_20
   - eprs_debian_11
-  - eprs_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](eprs_rhel_8)
 
-- [RHEL 7](eprs_rhel_7)
-
 - [Oracle Linux (OL) 9](eprs_rhel_9)
 
 - [Oracle Linux (OL) 8](eprs_rhel_8)
 
-- [Oracle Linux (OL) 7](eprs_rhel_7)
-
 - [Rocky Linux 9](eprs_other_linux_9)
 
 - [Rocky Linux 8](eprs_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](eprs_other_linux_8)
 
-- [CentOS 7](eprs_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](eprs_sles_15)
 
-- [SLES 12](eprs_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](eprs_ubuntu_22)
@@ -64,5 +52,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](eprs_ubuntu_20)
 
 - [Debian 11](eprs_debian_11)
-
-- [Debian 10](eprs_debian_10)
diff --git a/product_docs/docs/eprs/7/installing/windows.mdx b/product_docs/docs/eprs/7/installing/windows.mdx
index de71d49674c..203c540aec7 100644
--- a/product_docs/docs/eprs/7/installing/windows.mdx
+++ b/product_docs/docs/eprs/7/installing/windows.mdx
@@ -12,7 +12,7 @@ EDB provides a graphical interactive installer for Windows. You can access it tw
 
 - Download the graphical installer from the [Downloads page](https://www.enterprisedb.com/software-downloads-postgres#replication-server) and invoke the installer directly. See [Installing directly](/eprs/latest/installing/windows/#installing-directly).
 
-- Use StackBuilder Plus (with EDB Postgres Advanced Server) to download the EDB installer package and invoke the graphical installer. See [Using StackBuilder Plus](/eprs/latest/installing/windows/#using-stack-builder-or-stackbuilder-plus).
+- Use StackBuilder Plus (with EDB Postgres Advanced Server) to download the EDB installer package and invoke the graphical installer. See [Using StackBuilder Plus](/eprs/latest/installing/windows/#using-stackbuilder-plus).
 
 
 ## Prerequisites
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx
index f3f99080c9e..08e22d13dfd 100644
--- a/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx
+++ b/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx
@@ -25,25 +25,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/hadoop_rhel_9), [RHEL 8](linux_x86_64/hadoop_rhel_8), [RHEL 7](linux_x86_64/hadoop_rhel_7)
+- [RHEL 9](linux_x86_64/hadoop_rhel_9), [RHEL 8](linux_x86_64/hadoop_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/hadoop_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/hadoop_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/hadoop_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/hadoop_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/hadoop_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/hadoop_other_linux_9), [Rocky Linux 8](linux_x86_64/hadoop_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/hadoop_other_linux_9), [AlmaLinux 8](linux_x86_64/hadoop_other_linux_8)
 
-- [CentOS 7](linux_x86_64/hadoop_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/hadoop_sles_15), [SLES 12](linux_x86_64/hadoop_sles_12)
+- [SLES 15](linux_x86_64/hadoop_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/hadoop_ubuntu_22), [Ubuntu 20.04](linux_x86_64/hadoop_ubuntu_20)
 
-- [Debian 12](linux_x86_64/hadoop_debian_12), [Debian 11](linux_x86_64/hadoop_debian_11), [Debian 10](linux_x86_64/hadoop_debian_10)
+- [Debian 12](linux_x86_64/hadoop_debian_12), [Debian 11](linux_x86_64/hadoop_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -53,7 +51,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/hadoop_sles_15), [SLES 12](linux_ppc64le/hadoop_sles_12)
+- [SLES 15](linux_ppc64le/hadoop_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx
deleted file mode 100644
index 6225bbc86b8..00000000000
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/hadoop_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Hadoop Foreign Data Wrapper on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-hdfs_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx
index 7bd79cfb573..4527c811187 100644
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - hadoop_rhel_9
   - hadoop_rhel_8
   - hadoop_sles_15
-  - hadoop_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,6 +27,4 @@ Operating system-specific install instructions are described in the correspondin
 
 - [SLES 15](hadoop_sles_15)
 
-- [SLES 12](hadoop_sles_12)
-
 After you complete the installation, see [Initial configuration](../../configuring).
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx
deleted file mode 100644
index 2f96e5b9792..00000000000
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_centos_7.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Hadoop Foreign Data Wrapper on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-hdfs_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx
deleted file mode 100644
index c2eacc80b93..00000000000
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_debian_10.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Hadoop Foreign Data Wrapper on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as15-hdfs_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx
deleted file mode 100644
index 16ad813e2b9..00000000000
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_rhel_7.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Hadoop Foreign Data Wrapper on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-hdfs_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx
deleted file mode 100644
index 0fdc3978e65..00000000000
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/hadoop_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Hadoop Foreign Data Wrapper on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-hdfs_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx
index f9e1db0ef85..808752b46b6 100644
--- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - hadoop_rhel_9
   - hadoop_rhel_8
-  - hadoop_rhel_7
   - hadoop_other_linux_9
   - hadoop_other_linux_8
-  - hadoop_centos_7
   - hadoop_sles_15
-  - hadoop_sles_12
   - hadoop_ubuntu_22
   - hadoop_ubuntu_20
   - hadoop_debian_12
   - hadoop_debian_11
-  - hadoop_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](hadoop_rhel_8)
 
-- [RHEL 7](hadoop_rhel_7)
-
 - [Oracle Linux (OL) 9](hadoop_rhel_9)
 
 - [Oracle Linux (OL) 8](hadoop_rhel_8)
 
-- [Oracle Linux (OL) 7](hadoop_rhel_7)
-
 - [Rocky Linux 9](hadoop_other_linux_9)
 
 - [Rocky Linux 8](hadoop_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](hadoop_other_linux_8)
 
-- [CentOS 7](hadoop_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](hadoop_sles_15)
 
-- [SLES 12](hadoop_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](hadoop_ubuntu_22)
@@ -67,6 +55,4 @@ Operating system-specific install instructions are described in the correspondin
 
 - [Debian 11](hadoop_debian_11)
 
-- [Debian 10](hadoop_debian_10)
-
 After you complete the installation, see [Initial configuration](../../configuring).
diff --git a/product_docs/docs/hadoop_data_adapter/2/uninstalling.mdx b/product_docs/docs/hadoop_data_adapter/2/uninstalling.mdx
index dd96bfab7f8..8c49a511745 100644
--- a/product_docs/docs/hadoop_data_adapter/2/uninstalling.mdx
+++ b/product_docs/docs/hadoop_data_adapter/2/uninstalling.mdx
@@ -8,10 +8,6 @@ redirects:
 
 You use the `remove` command to uninstall Hadoop Foreign Data Wrapper packages. To uninstall, open a terminal window, assume superuser privileges, and enter the command that applies to the operating system and package manager used for the installation:
 
--   On RHEL or CentOS 7:
-
-    `yum remove edb-as<xx>-hdfs_fdw`
-
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
     `dnf remove edb-as<xx>-hdfs_fdw`
diff --git a/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx b/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx
index fb4dd30d54b..171f728dc88 100644
--- a/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx
+++ b/product_docs/docs/hadoop_data_adapter/2/upgrading.mdx
@@ -21,7 +21,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
@@ -31,7 +30,6 @@ To upgrade to the latest product version, enter one of the following commands:
   |         Operating system         |                                  Upgrade command                                  |
   | -------------------------------- | --------------------------------------------------------------------------------- |
   | RHEL 8/9 and derivatives         | `sudo dnf upgrade edb-as<xx>-hdfs_fdw`                              |
-  | RHEL 7 and derivatives, CentOS 7 | `sudo yum upgrade edb-as<xx>-hdfs_fdw edb-hdfs-libs`           |
   | SLES                             | `sudo zypper upgrade edb-as<xx>-hdfs_fdw`                              |
   | Debian and Ubuntu                | `sudo apt-get --only-upgrade install edb-as<xx>-hdfs-fdw edb-hdfs` |
 
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/index.mdx
index 291a9633341..3752cff7a4c 100644
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/index.mdx
+++ b/product_docs/docs/jdbc_connector/42.5.4.2/installing/index.mdx
@@ -23,8 +23,8 @@ legacyRedirectsGenerated:
     _configuring_the_jdbc_connector.html"
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - windows
   - configuring_for_java
@@ -37,25 +37,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/jdbc_rhel_9), [RHEL 8](linux_x86_64/jdbc_rhel_8), [RHEL 7](linux_x86_64/jdbc_rhel_7)
+- [RHEL 9](linux_x86_64/jdbc_rhel_9), [RHEL 8](linux_x86_64/jdbc_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/jdbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/jdbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/jdbc_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/jdbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/jdbc_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/jdbc_other_linux_9), [Rocky Linux 8](linux_x86_64/jdbc_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/jdbc_other_linux_9), [AlmaLinux 8](linux_x86_64/jdbc_other_linux_8)
 
-- [CentOS 7](linux_x86_64/jdbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/jdbc_sles_15), [SLES 12](linux_x86_64/jdbc_sles_12)
+- [SLES 15](linux_x86_64/jdbc_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/jdbc_ubuntu_22), [Ubuntu 20.04](linux_x86_64/jdbc_ubuntu_20)
 
-- [Debian 12](linux_x86_64/jdbc_debian_12), [Debian 11](linux_x86_64/jdbc_debian_11), [Debian 10](linux_x86_64/jdbc_debian_10)
+- [Debian 12](linux_x86_64/jdbc_debian_12), [Debian 11](linux_x86_64/jdbc_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -65,7 +63,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/jdbc_sles_15), [SLES 12](linux_ppc64le/jdbc_sles_12)
+- [SLES 15](linux_ppc64le/jdbc_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/index.mdx
index f8f88dac9fe..03872eb79eb 100644
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - jdbc_rhel_9
   - jdbc_rhel_8
   - jdbc_sles_15
-  - jdbc_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](jdbc_sles_15)
-
-- [SLES 12](jdbc_sles_12)
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/jdbc_sles_12.mdx
deleted file mode 100644
index b8960c14d72..00000000000
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_ppc64le/jdbc_sles_12.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB JDBC Connector on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page.
-
-- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution).
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-jdbc
-```
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/index.mdx
index 1d57b1f7558..da35df33914 100644
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - jdbc_rhel_9
   - jdbc_rhel_8
-  - jdbc_rhel_7
   - jdbc_other_linux_9
   - jdbc_other_linux_8
-  - jdbc_centos_7
   - jdbc_sles_15
-  - jdbc_sles_12
   - jdbc_ubuntu_22
   - jdbc_ubuntu_20
   - jdbc_debian_12
   - jdbc_debian_11
-  - jdbc_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](jdbc_rhel_8)
 
-- [RHEL 7](jdbc_rhel_7)
-
 - [Oracle Linux (OL) 9](jdbc_rhel_9)
 
 - [Oracle Linux (OL) 8](jdbc_rhel_8)
 
-- [Oracle Linux (OL) 7](jdbc_rhel_7)
-
 - [Rocky Linux 9](jdbc_other_linux_9)
 
 - [Rocky Linux 8](jdbc_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](jdbc_other_linux_8)
 
-- [CentOS 7](jdbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](jdbc_sles_15)
 
-- [SLES 12](jdbc_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](jdbc_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](jdbc_debian_12)
 
 - [Debian 11](jdbc_debian_11)
-
-- [Debian 10](jdbc_debian_10)
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_centos_7.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_centos_7.mdx
deleted file mode 100644
index e23c85562cb..00000000000
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_centos_7.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB JDBC Connector on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page.
-
-- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution).
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-jdbc
-```
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_debian_10.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_debian_10.mdx
deleted file mode 100644
index d3a4030e635..00000000000
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_debian_10.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB JDBC Connector on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page.
-
-- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution).
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-jdbc
-```
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_rhel_7.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_rhel_7.mdx
deleted file mode 100644
index 0b87a5a6f5b..00000000000
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_rhel_7.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB JDBC Connector on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page.
-
-- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution).
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-jdbc
-```
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_sles_12.mdx
deleted file mode 100644
index 0bfc62fa4f5..00000000000
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/linux_x86_64/jdbc_sles_12.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB JDBC Connector on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page.
-
-- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution).
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-jdbc
-```
diff --git a/product_docs/docs/jdbc_connector/42.5.4.2/installing/upgrading.mdx b/product_docs/docs/jdbc_connector/42.5.4.2/installing/upgrading.mdx
index 94424a24bfd..3fa65a84d67 100644
--- a/product_docs/docs/jdbc_connector/42.5.4.2/installing/upgrading.mdx
+++ b/product_docs/docs/jdbc_connector/42.5.4.2/installing/upgrading.mdx
@@ -22,6 +22,5 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.10.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.10.0_rel_notes.mdx
index 2d5e4072b65..75a1cc6e6ad 100644
--- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.10.0_rel_notes.mdx
+++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.10.0_rel_notes.mdx
@@ -9,11 +9,11 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.1
 
 | Type         | Description                                                                                                                                                                                                                                               |
 |--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Enhancement  | Added support for Postgres `tablefunc` extension functions, such as `crosstab`, in user repairs of incompatible DDL objects. The `crosstab` function is commonly used as a workaround for the Oracle `PIVOT` operator, which is not available in Postgres. |
+| Enhancement  | Added support for Postgres `tablefunc` extension functions, such as `crosstab`, in user repairs of incompatible DDL objects. The `crosstab` function is commonly used as a workaround for the Oracle `PIVOT` operator, which isn't available in Postgres. |
 | Enhancement  | Added a Migration Portal Knowledge Base entry that describes the use of the Postgres `tablefunc` extension `crosstab` function as a workaround for the Oracle `PIVOT` operator.                                                                           |
 | Bug&nbsp;fix | Fixed the issue that caused the Migration Portal to refresh when selecting the **Projects** tab after selecting the **Portal Wiki** tab.                                                                                                                  |
-| Bug&nbsp;fix | Improved the error handling capabilities of AI Copilot. It now provides the user with better information about any errors returned from the backend server.                                                                                               |
-| Bug&nbsp;fix | Fixed the vertical scroll for AI Copilot so that it automatically scrolls as new information is displayed.                                                                                                                                                |
-| Bug&nbsp;fix | Fixed the error that caused AI Copilot to lose in-progress streaming response if the user navigates to a different tab.                                                                                                                                   |
-| Bug&nbsp;fix | Fixed the error that caused the Quick Help section on the workspace page to go blank when the user navigates from the AI Copilot tab.                                                                                                                     |
-| Bug&nbsp;fix | Improved AI Copilot to support adding line breaks in the AI Copilot text box using modifier keys (control, command, option, shift keys) along with Enter.                                                                                                 |
+| Bug&nbsp;fix | Improved the error handling capabilities of AI Copilot. It now provides better information about any errors returned from the backend server.                                                                                               |
+| Bug&nbsp;fix | Fixed the vertical scroll for AI Copilot so that it scrolls as new information is displayed.                                                                                                                                                |
+| Bug&nbsp;fix | Fixed the error that caused AI Copilot to lose in-progress streaming response when navigating to a different tab.                                                                                                                                   |
+| Bug&nbsp;fix | Fixed the error that caused the Quick Help section on the workspace page to go blank when navigating from the AI Copilot tab.                                                                                                                     |
+| Bug&nbsp;fix | Improved AI Copilot to support adding line breaks in the AI Copilot text box using modifier keys (Control, Command, Option, Shift keys) along with Enter.                                                                                                 |
diff --git a/product_docs/docs/migration_toolkit/55/installing/index.mdx b/product_docs/docs/migration_toolkit/55/installing/index.mdx
index 05d247f5fae..b920111c3d1 100644
--- a/product_docs/docs/migration_toolkit/55/installing/index.mdx
+++ b/product_docs/docs/migration_toolkit/55/installing/index.mdx
@@ -40,25 +40,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/mtk_rhel_9), [RHEL 8](linux_x86_64/mtk_rhel_8), [RHEL 7](linux_x86_64/mtk_rhel_7)
+- [RHEL 9](linux_x86_64/mtk_rhel_9), [RHEL 8](linux_x86_64/mtk_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/mtk_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mtk_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/mtk_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/mtk_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mtk_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/mtk_other_linux_9), [Rocky Linux 8](linux_x86_64/mtk_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/mtk_other_linux_9), [AlmaLinux 8](linux_x86_64/mtk_other_linux_8)
 
-- [CentOS 7](linux_x86_64/mtk_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/mtk_sles_15), [SLES 12](linux_x86_64/mtk_sles_12)
+- [SLES 15](linux_x86_64/mtk_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/mtk_ubuntu_22), [Ubuntu 20.04](linux_x86_64/mtk_ubuntu_20)
 
-- [Debian 11](linux_x86_64/mtk_debian_11), [Debian 10](linux_x86_64/mtk_debian_10)
+- [Debian 11](linux_x86_64/mtk_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -68,7 +66,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/mtk_sles_15), [SLES 12](linux_ppc64le/mtk_sles_12)
+- [SLES 15](linux_ppc64le/mtk_sles_15)
 
 ## Macintosh
 
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx
index 30eb9ec70de..7e4a52018e9 100644
--- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - mtk_rhel_9
   - mtk_rhel_8
   - mtk_sles_15
-  - mtk_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](mtk_sles_15)
-
-- [SLES 12](mtk_sles_12)
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx
deleted file mode 100644
index 0ff1cd89512..00000000000
--- a/product_docs/docs/migration_toolkit/55/installing/linux_ppc64le/mtk_sles_12.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Migration Toolkit on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/mtk55_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-migrationtoolkit
-```
-
-## Initial configuration
-
-Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details.
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx
index b7a1c56aab5..d5ae4414da2 100644
--- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/index.mdx
@@ -12,16 +12,12 @@ redirects:
 navigation:
   - mtk_rhel_9
   - mtk_rhel_8
-  - mtk_rhel_7
   - mtk_other_linux_9
   - mtk_other_linux_8
-  - mtk_centos_7
   - mtk_sles_15
-  - mtk_sles_12
   - mtk_ubuntu_22
   - mtk_ubuntu_20
   - mtk_debian_11
-  - mtk_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -32,14 +28,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](mtk_rhel_8)
 
-- [RHEL 7](mtk_rhel_7)
-
 - [Oracle Linux (OL) 9](mtk_rhel_9)
 
 - [Oracle Linux (OL) 8](mtk_rhel_8)
 
-- [Oracle Linux (OL) 7](mtk_rhel_7)
-
 - [Rocky Linux 9](mtk_other_linux_9)
 
 - [Rocky Linux 8](mtk_other_linux_8)
@@ -48,14 +40,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](mtk_other_linux_8)
 
-- [CentOS 7](mtk_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](mtk_sles_15)
 
-- [SLES 12](mtk_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](mtk_ubuntu_22)
@@ -63,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](mtk_ubuntu_20)
 
 - [Debian 11](mtk_debian_11)
-
-- [Debian 10](mtk_debian_10)
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx
deleted file mode 100644
index c43d583218b..00000000000
--- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_centos_7.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Migration Toolkit on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-migrationtoolkit
-```
-
-## Initial configuration
-
-Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details.
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx
deleted file mode 100644
index 068356c88a0..00000000000
--- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_debian_10.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Migration Toolkit on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-migrationtoolkit
-```
-
-## Initial configuration
-
-Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details.
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx
deleted file mode 100644
index 9a8a08a0924..00000000000
--- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_rhel_7.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Migration Toolkit on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Address other prerequisites:
-  ```shell
-  # Install the EPEL repository:
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-migrationtoolkit
-```
-
-## Initial configuration
-
-Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details.
diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx
deleted file mode 100644
index ff2e9f31ff1..00000000000
--- a/product_docs/docs/migration_toolkit/55/installing/linux_x86_64/mtk_sles_12.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Migration Toolkit on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/mtk55_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-migrationtoolkit
-```
-
-## Initial configuration
-
-Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details.
diff --git a/product_docs/docs/migration_toolkit/55/upgrading.mdx b/product_docs/docs/migration_toolkit/55/upgrading.mdx
index 23bdaefe093..41bd4cd60cf 100644
--- a/product_docs/docs/migration_toolkit/55/upgrading.mdx
+++ b/product_docs/docs/migration_toolkit/55/upgrading.mdx
@@ -21,6 +21,5 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |             Operating system     |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/index.mdx
index c5cb0377d98..a30fd831ccc 100644
--- a/product_docs/docs/mongo_data_adapter/5/installing/index.mdx
+++ b/product_docs/docs/mongo_data_adapter/5/installing/index.mdx
@@ -25,25 +25,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/mongo_rhel_9), [RHEL 8](linux_x86_64/mongo_rhel_8), [RHEL 7](linux_x86_64/mongo_rhel_7)
+- [RHEL 9](linux_x86_64/mongo_rhel_9), [RHEL 8](linux_x86_64/mongo_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/mongo_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mongo_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/mongo_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/mongo_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mongo_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/mongo_other_linux_9), [Rocky Linux 8](linux_x86_64/mongo_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/mongo_other_linux_9), [AlmaLinux 8](linux_x86_64/mongo_other_linux_8)
 
-- [CentOS 7](linux_x86_64/mongo_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/mongo_sles_15), [SLES 12](linux_x86_64/mongo_sles_12)
+- [SLES 15](linux_x86_64/mongo_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/mongo_ubuntu_22), [Ubuntu 20.04](linux_x86_64/mongo_ubuntu_20)
 
-- [Debian 12](linux_x86_64/mongo_debian_12), [Debian 11](linux_x86_64/mongo_debian_11), [Debian 10](linux_x86_64/mongo_debian_10)
+- [Debian 12](linux_x86_64/mongo_debian_12), [Debian 11](linux_x86_64/mongo_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -53,7 +51,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/mongo_sles_15), [SLES 12](linux_ppc64le/mongo_sles_12)
+- [SLES 15](linux_ppc64le/mongo_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx
index d2526dc4868..f5853770719 100644
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - mongo_rhel_9
   - mongo_rhel_8
   - mongo_sles_15
-  - mongo_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,6 +27,4 @@ Operating system-specific install instructions are described in the correspondin
 
 - [SLES 15](mongo_sles_15)
 
-- [SLES 12](mongo_sles_12)
-
 After you complete the installation, see [Initial configuration](../../configuring).
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx
deleted file mode 100644
index 4b8f4d52fe7..00000000000
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_ppc64le/mongo_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing MongoDB Foreign Data Wrapper on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-mongo_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx
index fde6ddcb490..394517bf3b0 100644
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - mongo_rhel_9
   - mongo_rhel_8
-  - mongo_rhel_7
   - mongo_other_linux_9
   - mongo_other_linux_8
-  - mongo_centos_7
   - mongo_sles_15
-  - mongo_sles_12
   - mongo_ubuntu_22
   - mongo_ubuntu_20
   - mongo_debian_12
   - mongo_debian_11
-  - mongo_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](mongo_rhel_8)
 
-- [RHEL 7](mongo_rhel_7)
-
 - [Oracle Linux (OL) 9](mongo_rhel_9)
 
 - [Oracle Linux (OL) 8](mongo_rhel_8)
 
-- [Oracle Linux (OL) 7](mongo_rhel_7)
-
 - [Rocky Linux 9](mongo_other_linux_9)
 
 - [Rocky Linux 8](mongo_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](mongo_other_linux_8)
 
-- [CentOS 7](mongo_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](mongo_sles_15)
 
-- [SLES 12](mongo_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](mongo_ubuntu_22)
@@ -67,6 +55,4 @@ Operating system-specific install instructions are described in the correspondin
 
 - [Debian 11](mongo_debian_11)
 
-- [Debian 10](mongo_debian_10)
-
 After you complete the installation, see [Initial configuration](../../configuring).
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx
deleted file mode 100644
index 763cecc9ab1..00000000000
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_centos_7.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing MongoDB Foreign Data Wrapper on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-mongo_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx
deleted file mode 100644
index 2c7cc87210d..00000000000
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_debian_10.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Debian 10
-title: Installing MongoDB Foreign Data Wrapper on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as15-mongo_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx
deleted file mode 100644
index fc4cbd61a5f..00000000000
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_rhel_7.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing MongoDB Foreign Data Wrapper on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-mongo_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx
deleted file mode 100644
index d508004896c..00000000000
--- a/product_docs/docs/mongo_data_adapter/5/installing/linux_x86_64/mongo_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing MongoDB Foreign Data Wrapper on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-mongo_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using.
diff --git a/product_docs/docs/mongo_data_adapter/5/uninstalling.mdx b/product_docs/docs/mongo_data_adapter/5/uninstalling.mdx
index 6d5647faf96..bf8f5b42cfa 100644
--- a/product_docs/docs/mongo_data_adapter/5/uninstalling.mdx
+++ b/product_docs/docs/mongo_data_adapter/5/uninstalling.mdx
@@ -9,10 +9,6 @@ redirects:
 
 You can use the `remove` command to uninstall MongoDB Foreign Data Wrapper packages. To uninstall, open a terminal window, assume superuser privileges, and enter the command that applies to the operating system and package manager used for the installation. `xx` is the EDB Postgres Advanced Server version number.
 
--   On RHEL or CentOS 7:
-
-    `yum remove edb-as<xx>-mongo_fdw`
-
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
     `dnf remove edb-as<xx>-mongo_fdw`
diff --git a/product_docs/docs/mongo_data_adapter/5/upgrading.mdx b/product_docs/docs/mongo_data_adapter/5/upgrading.mdx
index 2943e26e47a..28b5f8f0f41 100644
--- a/product_docs/docs/mongo_data_adapter/5/upgrading.mdx
+++ b/product_docs/docs/mongo_data_adapter/5/upgrading.mdx
@@ -22,7 +22,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
@@ -32,7 +31,6 @@ To upgrade to the latest product version, enter one of the following commands:
   |         Operating system         |                                  Upgrade command                                   |
   | -------------------------------- | ---------------------------------------------------------------------------------- |
   | RHEL 8/9 and derivatives         | `sudo dnf upgrade edb-as<xx>-mongo_fdw`                              |
-  | RHEL 7 and derivatives, CentOS 7 | `sudo yum upgrade edb-as<xx>-mongo_fdw edb-libmongoc-libs`           |
   | SLES                             | `sudo zypper upgrade edb-as<xx>-mongo_fdw`                              |
   | Debian and Ubuntu                | `sudo apt-get --only-upgrade install edb-as<xx>-mongo-fdw edb-libmongoc` |
 
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/index.mdx
index b6a984e11dc..df826a484c5 100644
--- a/product_docs/docs/mysql_data_adapter/2/installing/index.mdx
+++ b/product_docs/docs/mysql_data_adapter/2/installing/index.mdx
@@ -24,25 +24,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/mysql_rhel_9), [RHEL 8](linux_x86_64/mysql_rhel_8), [RHEL 7](linux_x86_64/mysql_rhel_7)
+- [RHEL 9](linux_x86_64/mysql_rhel_9), [RHEL 8](linux_x86_64/mysql_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/mysql_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mysql_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/mysql_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/mysql_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/mysql_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/mysql_other_linux_9), [Rocky Linux 8](linux_x86_64/mysql_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/mysql_other_linux_9), [AlmaLinux 8](linux_x86_64/mysql_other_linux_8)
 
-- [CentOS 7](linux_x86_64/mysql_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/mysql_sles_15), [SLES 12](linux_x86_64/mysql_sles_12)
+- [SLES 15](linux_x86_64/mysql_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/mysql_ubuntu_22), [Ubuntu 20.04](linux_x86_64/mysql_ubuntu_20)
 
-- [Debian 12](linux_x86_64/mysql_debian_12), [Debian 11](linux_x86_64/mysql_debian_11), [Debian 10](linux_x86_64/mysql_debian_10)
+- [Debian 12](linux_x86_64/mysql_debian_12), [Debian 11](linux_x86_64/mysql_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -52,7 +50,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/mysql_sles_15), [SLES 12](linux_ppc64le/mysql_sles_12)
+- [SLES 15](linux_ppc64le/mysql_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx
index fa25126dd00..b287cb3907b 100644
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - mysql_rhel_9
   - mysql_rhel_8
   - mysql_sles_15
-  - mysql_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](mysql_sles_15)
-
-- [SLES 12](mysql_sles_12)
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx
deleted file mode 100644
index 59abded9e62..00000000000
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_ppc64le/mysql_sles_12.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-navTitle: SLES 12
-title: Installing MySQL Foreign Data Wrapper on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/ibm_power_ppc64le/mysql_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the MySQL community repository:
-  ```shell
-  sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm
-  rpm --import /etc/RPM-GPG-KEY-mysql-2022
-  ```
-- Enable the MySQL8 repository and disable the MySQL 5 repository:
-
-  ```shell
-  sudo zypper modifyrepo -e mysql80-community
-  sudo zypper modifyrepo -d mysql57-community
-  ```
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-mysql8_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed.
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx
index 91d5bd81bb7..5caa0fdd5b0 100644
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - mysql_rhel_9
   - mysql_rhel_8
-  - mysql_rhel_7
   - mysql_other_linux_9
   - mysql_other_linux_8
-  - mysql_centos_7
   - mysql_sles_15
-  - mysql_sles_12
   - mysql_ubuntu_22
   - mysql_ubuntu_20
   - mysql_debian_12
   - mysql_debian_11
-  - mysql_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](mysql_rhel_8)
 
-- [RHEL 7](mysql_rhel_7)
-
 - [Oracle Linux (OL) 9](mysql_rhel_9)
 
 - [Oracle Linux (OL) 8](mysql_rhel_8)
 
-- [Oracle Linux (OL) 7](mysql_rhel_7)
-
 - [Rocky Linux 9](mysql_other_linux_9)
 
 - [Rocky Linux 8](mysql_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](mysql_other_linux_8)
 
-- [CentOS 7](mysql_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](mysql_sles_15)
 
-- [SLES 12](mysql_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](mysql_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](mysql_debian_12)
 
 - [Debian 11](mysql_debian_11)
-
-- [Debian 10](mysql_debian_10)
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx
deleted file mode 100644
index 45fdc7b0357..00000000000
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_centos_7.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing MySQL Foreign Data Wrapper on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Download and install the MySQL repo:
-  ```shell
-  sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm
-  ```
-- Enable the MySQL repo:
-
-  ```shell
-  # For MySQL 8:
-  sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as<xx>-mysql8_fdw
-
-  # For MySQL 5:
-  sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as<xx>-mysql5_fdw
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-mysql8_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed.
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx
deleted file mode 100644
index 7c1474ab184..00000000000
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-navTitle: Debian 10
-title: Installing MySQL Foreign Data Wrapper on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Download the GPG key to your APT keyring directly using the apt-key utility
-  ```shell
-  sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29
-  ```
-- Install and configure the MySQL repo:
-
-  ```shell
-  # For MySQL 8:
-  sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee  /etc/apt/sources.list.d/mysql.list
-
-  # For MySQL 5:
-  sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee  /etc/apt/sources.list.d/mysql.list
-
-  # Get the most up-to-date package information from the MySQL APT repository:
-  sudo apt-get update
-  ```
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as15-mysql8_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed.
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx
deleted file mode 100644
index ab6db5f89f3..00000000000
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_rhel_7.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing MySQL Foreign Data Wrapper on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-- Download and install the MYSQL repo:
-  ```shell
-  sudo yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm
-  ```
-- Enable the MYSQL repo:
-
-  ```shell
-  # For MySQL 8:
-  sudo yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as<xx>-mysql8_fdw
-
-  # For MySQL 5:
-  sudo yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as<xx>-mysql5_fdw
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as15-mysql8_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed.
diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx
deleted file mode 100644
index 572a531f1f4..00000000000
--- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_sles_12.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-navTitle: SLES 12
-title: Installing MySQL Foreign Data Wrapper on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/x86_amd64/mysql_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the MySQL community repository:
-  ```shell
-  sudo wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm
-  rpm --import /etc/RPM-GPG-KEY-mysql-2022
-  ```
-- Enable the MySQL8 repository and disable the MySQL 5 repository:
-
-  ```shell
-  sudo zypper modifyrepo -e mysql80-community
-  sudo zypper modifyrepo -d mysql57-community
-  ```
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as15-mysql8_fdw
-```
-
-Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed.
diff --git a/product_docs/docs/mysql_data_adapter/2/uninstalling.mdx b/product_docs/docs/mysql_data_adapter/2/uninstalling.mdx
index 694593cda25..a48821d8d43 100644
--- a/product_docs/docs/mysql_data_adapter/2/uninstalling.mdx
+++ b/product_docs/docs/mysql_data_adapter/2/uninstalling.mdx
@@ -9,18 +9,12 @@ redirects:
 
 You can use the `remove` command to uninstall MySQL Foreign Data Wrapper packages. To uninstall, open a terminal window, assume superuser privileges, and enter the command that applies to the operating system and package manager used for the installation:
 
--   On RHEL or CentOS 7:
-
-    `yum remove edb-as<xx>-mysql<x>_fdw`
-
-    Where:
-    - `<xx>` is the EDB Postgres Advanced Server version.
-    - `<x>` is the supported release version number of MySQL. 
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
     `dnf remove edb-as<xx>-mysql8_fdw`
    
     Where `<xx>` is the EDB Postgres Advanced Server version.
+ 
 -   On SLES:
 
     `zypper remove edb-as<xx>-mysql<x>_fdw`  
@@ -28,6 +22,7 @@ You can use the `remove` command to uninstall MySQL Foreign Data Wrapper package
     Where:
     - `<xx>` is the EDB Postgres Advanced Server version.
     - `<x>` is the supported release version number of MySQL. 
+     
 - On Debian or Ubuntu 
 
     `apt-get remove edb-as<xx>-mysql-fdw`
diff --git a/product_docs/docs/mysql_data_adapter/2/upgrading.mdx b/product_docs/docs/mysql_data_adapter/2/upgrading.mdx
index d1fda4d78ce..94691060274 100644
--- a/product_docs/docs/mysql_data_adapter/2/upgrading.mdx
+++ b/product_docs/docs/mysql_data_adapter/2/upgrading.mdx
@@ -22,7 +22,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
@@ -32,7 +31,6 @@ To upgrade to the latest product version, enter one of the following commands:
   |         Operating system         |                                  Upgrade command                                   |
   | -------------------------------- | ---------------------------------------------------------------------------------- |
   | RHEL 8/9 and derivatives         | `sudo dnf -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
-  | RHEL 7 and derivatives, CentOS 7 | `sudo yum -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
   | SLES                             | `sudo zypper -y upgrade edb-as<xx>-mysql<y>_fdw* mysql-community-devel` |
   | Debian and Ubuntu                | `sudo apt-get upgrade edb-as<xx>-mysql<y>-fdw`                           |
 
diff --git a/product_docs/docs/ocl_connector/14/installing/index.mdx b/product_docs/docs/ocl_connector/14/installing/index.mdx
index 309ca9af5ae..38ad5284927 100644
--- a/product_docs/docs/ocl_connector/14/installing/index.mdx
+++ b/product_docs/docs/ocl_connector/14/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
   - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - windows
   - upgrading
 ---
@@ -26,25 +26,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8), [RHEL 7](linux_x86_64/ocl_rhel_7)
+- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/ocl_other_linux_9), [Rocky Linux 8](linux_x86_64/ocl_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/ocl_other_linux_9), [AlmaLinux 8](linux_x86_64/ocl_other_linux_8)
 
-- [CentOS 7](linux_x86_64/ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/ocl_sles_15), [SLES 12](linux_x86_64/ocl_sles_12)
+- [SLES 15](linux_x86_64/ocl_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20)
 
-- [Debian 11](linux_x86_64/ocl_debian_11), [Debian 10](linux_x86_64/ocl_debian_10)
+- [Debian 11](linux_x86_64/ocl_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -54,7 +52,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/ocl_sles_15), [SLES 12](linux_ppc64le/ocl_sles_12)
+- [SLES 15](linux_ppc64le/ocl_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx
index 225be426ffb..f11f64e7e38 100644
--- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - ocl_rhel_9
   - ocl_rhel_8
   - ocl_sles_15
-  - ocl_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
-
-- [SLES 12](ocl_sles_12)
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx
deleted file mode 100644
index 877f4aa1ac4..00000000000
--- a/product_docs/docs/ocl_connector/14/installing/linux_ppc64le/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx
index f21105aa493..232c60d6995 100644
--- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/index.mdx
@@ -12,15 +12,11 @@ redirects:
 navigation:
   - ocl_rhel_9
   - ocl_rhel_8
-  - ocl_rhel_7
   - ocl_other_linux_9
   - ocl_other_linux_8
-  - ocl_centos_7
   - ocl_sles_15
-  - ocl_sles_12
   - ocl_ubuntu_20
   - ocl_debian_11
-  - ocl_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -31,14 +27,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](ocl_rhel_8)
 
-- [RHEL 7](ocl_rhel_7)
-
 - [Oracle Linux (OL) 9](ocl_rhel_9)
 
 - [Oracle Linux (OL) 8](ocl_rhel_8)
 
-- [Oracle Linux (OL) 7](ocl_rhel_7)
-
 - [Rocky Linux 9](ocl_other_linux_9)
 
 - [Rocky Linux 8](ocl_other_linux_8)
@@ -47,18 +39,12 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](ocl_other_linux_8)
 
-- [CentOS 7](ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
 
-- [SLES 12](ocl_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 20.04](ocl_ubuntu_20)
 
 - [Debian 11](ocl_debian_11)
-
-- [Debian 10](ocl_debian_10)
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx
deleted file mode 100644
index cddcd3b8cf2..00000000000
--- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_centos_7.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB OCL Connector on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx
deleted file mode 100644
index de9ff653a0f..00000000000
--- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_debian_10.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB OCL Connector on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-oci
-sudo apt-get -y install edb-oci-dev
-```
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx
deleted file mode 100644
index a6e12abe7aa..00000000000
--- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_rhel_7.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx
deleted file mode 100644
index 957bc8e9ac5..00000000000
--- a/product_docs/docs/ocl_connector/14/installing/linux_x86_64/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/14/installing/upgrading.mdx b/product_docs/docs/ocl_connector/14/installing/upgrading.mdx
index 46c1314c488..d6985681820 100644
--- a/product_docs/docs/ocl_connector/14/installing/upgrading.mdx
+++ b/product_docs/docs/ocl_connector/14/installing/upgrading.mdx
@@ -5,23 +5,11 @@ redirects:
   - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install/
 ---
 
-If you have an existing `OCL Connector` RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
+If you have an existing `OCL Connector` RPM installation, you can use dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter:
 
--   On RHEL or CentOS 7:
+    `dnf upgrade edb-repo`
 
-     `yum upgrade edb-repo`
-
--   On RHEL or Rocky Linux or AlmaLinux 8:
-
-     `dnf upgrade edb-repo`
-
-yum or dnf will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages:
-
--   On RHEL or CentOS 7:
-
-     `yum upgrade edb-oci`
-
-     `yum upgrade edb-oci-devel`
+dnf updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can upgrade any installed packages:
 
 -   On RHEL or Rocky Linux or AlmaLinux 8:
 
diff --git a/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx b/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx
index 6f749a2bf6e..338066e6851 100644
--- a/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx
+++ b/product_docs/docs/ocl_connector/15/03_libpq_compatibility.mdx
@@ -34,5 +34,4 @@ Where `<package-manager>` is the package manager used with your operating system
 | Package manager |         Operating system         |
 | --------------- | -------------------------------- |
 | dnf             | RHEL 8/9 and derivatives         |
-| yum             | RHEL 7 and derivatives, CentOS 7 |
 | zypper          | SLES                             |
\ No newline at end of file
diff --git a/product_docs/docs/ocl_connector/15/installing/index.mdx b/product_docs/docs/ocl_connector/15/installing/index.mdx
index efbe5f05427..718f25597e2 100644
--- a/product_docs/docs/ocl_connector/15/installing/index.mdx
+++ b/product_docs/docs/ocl_connector/15/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
   - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - windows
   - upgrading
 ---
@@ -26,25 +26,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8), [RHEL 7](linux_x86_64/ocl_rhel_7)
+- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/ocl_other_linux_9), [Rocky Linux 8](linux_x86_64/ocl_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/ocl_other_linux_9), [AlmaLinux 8](linux_x86_64/ocl_other_linux_8)
 
-- [CentOS 7](linux_x86_64/ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/ocl_sles_15), [SLES 12](linux_x86_64/ocl_sles_12)
+- [SLES 15](linux_x86_64/ocl_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/ocl_ubuntu_22), [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20)
 
-- [Debian 11](linux_x86_64/ocl_debian_11), [Debian 10](linux_x86_64/ocl_debian_10)
+- [Debian 11](linux_x86_64/ocl_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -54,7 +52,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/ocl_sles_15), [SLES 12](linux_ppc64le/ocl_sles_12)
+- [SLES 15](linux_ppc64le/ocl_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx
index 225be426ffb..f11f64e7e38 100644
--- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - ocl_rhel_9
   - ocl_rhel_8
   - ocl_sles_15
-  - ocl_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
-
-- [SLES 12](ocl_sles_12)
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx
deleted file mode 100644
index 44a3da2be2d..00000000000
--- a/product_docs/docs/ocl_connector/15/installing/linux_ppc64le/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx
index a3b59e3ab6c..d824d0b358f 100644
--- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/index.mdx
@@ -12,16 +12,12 @@ redirects:
 navigation:
   - ocl_rhel_9
   - ocl_rhel_8
-  - ocl_rhel_7
   - ocl_other_linux_9
   - ocl_other_linux_8
-  - ocl_centos_7
   - ocl_sles_15
-  - ocl_sles_12
   - ocl_ubuntu_22
   - ocl_ubuntu_20
   - ocl_debian_11
-  - ocl_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -32,14 +28,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](ocl_rhel_8)
 
-- [RHEL 7](ocl_rhel_7)
-
 - [Oracle Linux (OL) 9](ocl_rhel_9)
 
 - [Oracle Linux (OL) 8](ocl_rhel_8)
 
-- [Oracle Linux (OL) 7](ocl_rhel_7)
-
 - [Rocky Linux 9](ocl_other_linux_9)
 
 - [Rocky Linux 8](ocl_other_linux_8)
@@ -48,14 +40,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](ocl_other_linux_8)
 
-- [CentOS 7](ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
 
-- [SLES 12](ocl_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](ocl_ubuntu_22)
@@ -63,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](ocl_ubuntu_20)
 
 - [Debian 11](ocl_debian_11)
-
-- [Debian 10](ocl_debian_10)
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx
deleted file mode 100644
index 321d8dffcdc..00000000000
--- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_centos_7.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB OCL Connector on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx
deleted file mode 100644
index 987c46cda4d..00000000000
--- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_debian_10.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB OCL Connector on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-oci
-sudo apt-get -y install edb-oci-dev
-```
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx
deleted file mode 100644
index 6ea1e413da9..00000000000
--- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_rhel_7.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx
deleted file mode 100644
index c436545933c..00000000000
--- a/product_docs/docs/ocl_connector/15/installing/linux_x86_64/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx
index 376b5dbdcfa..26b0bdbaa23 100644
--- a/product_docs/docs/ocl_connector/15/installing/upgrading.mdx
+++ b/product_docs/docs/ocl_connector/15/installing/upgrading.mdx
@@ -25,7 +25,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
diff --git a/product_docs/docs/ocl_connector/16/03_libpq_compatibility.mdx b/product_docs/docs/ocl_connector/16/03_libpq_compatibility.mdx
index 6f749a2bf6e..338066e6851 100644
--- a/product_docs/docs/ocl_connector/16/03_libpq_compatibility.mdx
+++ b/product_docs/docs/ocl_connector/16/03_libpq_compatibility.mdx
@@ -34,5 +34,4 @@ Where `<package-manager>` is the package manager used with your operating system
 | Package manager |         Operating system         |
 | --------------- | -------------------------------- |
 | dnf             | RHEL 8/9 and derivatives         |
-| yum             | RHEL 7 and derivatives, CentOS 7 |
 | zypper          | SLES                             |
\ No newline at end of file
diff --git a/product_docs/docs/ocl_connector/16/installing/index.mdx b/product_docs/docs/ocl_connector/16/installing/index.mdx
index 6282e954d5e..4b1f1965ad5 100644
--- a/product_docs/docs/ocl_connector/16/installing/index.mdx
+++ b/product_docs/docs/ocl_connector/16/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
   - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - windows
   - upgrading
@@ -27,25 +27,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8), [RHEL 7](linux_x86_64/ocl_rhel_7)
+- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/ocl_other_linux_9), [Rocky Linux 8](linux_x86_64/ocl_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/ocl_other_linux_9), [AlmaLinux 8](linux_x86_64/ocl_other_linux_8)
 
-- [CentOS 7](linux_x86_64/ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/ocl_sles_15), [SLES 12](linux_x86_64/ocl_sles_12)
+- [SLES 15](linux_x86_64/ocl_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/ocl_ubuntu_22), [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20)
 
-- [Debian 12](linux_x86_64/ocl_debian_12), [Debian 11](linux_x86_64/ocl_debian_11), [Debian 10](linux_x86_64/ocl_debian_10)
+- [Debian 12](linux_x86_64/ocl_debian_12), [Debian 11](linux_x86_64/ocl_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -55,7 +53,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/ocl_sles_15), [SLES 12](linux_ppc64le/ocl_sles_12)
+- [SLES 15](linux_ppc64le/ocl_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/index.mdx
index 225be426ffb..f11f64e7e38 100644
--- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - ocl_rhel_9
   - ocl_rhel_8
   - ocl_sles_15
-  - ocl_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
-
-- [SLES 12](ocl_sles_12)
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx
deleted file mode 100644
index c8e2b1ab6eb..00000000000
--- a/product_docs/docs/ocl_connector/16/installing/linux_ppc64le/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/index.mdx
index bf47fa43368..a4cba53524f 100644
--- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - ocl_rhel_9
   - ocl_rhel_8
-  - ocl_rhel_7
   - ocl_other_linux_9
   - ocl_other_linux_8
-  - ocl_centos_7
   - ocl_sles_15
-  - ocl_sles_12
   - ocl_ubuntu_22
   - ocl_ubuntu_20
   - ocl_debian_12
   - ocl_debian_11
-  - ocl_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](ocl_rhel_8)
 
-- [RHEL 7](ocl_rhel_7)
-
 - [Oracle Linux (OL) 9](ocl_rhel_9)
 
 - [Oracle Linux (OL) 8](ocl_rhel_8)
 
-- [Oracle Linux (OL) 7](ocl_rhel_7)
-
 - [Rocky Linux 9](ocl_other_linux_9)
 
 - [Rocky Linux 8](ocl_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](ocl_other_linux_8)
 
-- [CentOS 7](ocl_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](ocl_sles_15)
 
-- [SLES 12](ocl_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](ocl_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](ocl_debian_12)
 
 - [Debian 11](ocl_debian_11)
-
-- [Debian 10](ocl_debian_10)
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx
deleted file mode 100644
index 9048e9eb984..00000000000
--- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_centos_7.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB OCL Connector on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx
deleted file mode 100644
index be6e734ddf1..00000000000
--- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_debian_10.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB OCL Connector on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-oci
-sudo apt-get -y install edb-oci-dev
-```
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx
deleted file mode 100644
index 2ff41af0dcb..00000000000
--- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_rhel_7.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-oci
-sudo yum -y install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx
deleted file mode 100644
index 00764c7c419..00000000000
--- a/product_docs/docs/ocl_connector/16/installing/linux_x86_64/ocl_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB OCL Connector on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-oci
-sudo zypper -n install edb-oci-devel
-```
diff --git a/product_docs/docs/ocl_connector/16/installing/upgrading.mdx b/product_docs/docs/ocl_connector/16/installing/upgrading.mdx
index 376b5dbdcfa..26b0bdbaa23 100644
--- a/product_docs/docs/ocl_connector/16/installing/upgrading.mdx
+++ b/product_docs/docs/ocl_connector/16/installing/upgrading.mdx
@@ -25,7 +25,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
diff --git a/product_docs/docs/odbc_connector/13/installing/index.mdx b/product_docs/docs/odbc_connector/13/installing/index.mdx
index c6819e92df6..734cb20cc69 100644
--- a/product_docs/docs/odbc_connector/13/installing/index.mdx
+++ b/product_docs/docs/odbc_connector/13/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
   - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - windows
   - upgrading
 ---
@@ -26,25 +26,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/odbc_rhel_9), [RHEL 8](linux_x86_64/odbc_rhel_8), [RHEL 7](linux_x86_64/odbc_rhel_7)
+- [RHEL 9](linux_x86_64/odbc_rhel_9), [RHEL 8](linux_x86_64/odbc_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/odbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/odbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/odbc_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/odbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/odbc_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/odbc_other_linux_9), [Rocky Linux 8](linux_x86_64/odbc_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/odbc_other_linux_9), [AlmaLinux 8](linux_x86_64/odbc_other_linux_8)
 
-- [CentOS 7](linux_x86_64/odbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/odbc_sles_15), [SLES 12](linux_x86_64/odbc_sles_12)
+- [SLES 15](linux_x86_64/odbc_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/odbc_ubuntu_22), [Ubuntu 20.04](linux_x86_64/odbc_ubuntu_20)
 
-- [Debian 11](linux_x86_64/odbc_debian_11), [Debian 10](linux_x86_64/odbc_debian_10)
+- [Debian 11](linux_x86_64/odbc_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -54,7 +52,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/odbc_sles_15), [SLES 12](linux_ppc64le/odbc_sles_12)
+- [SLES 15](linux_ppc64le/odbc_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx
index 2051bc77f7d..7b1b0fa0a28 100644
--- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - odbc_rhel_9
   - odbc_rhel_8
   - odbc_sles_15
-  - odbc_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](odbc_sles_15)
-
-- [SLES 12](odbc_sles_12)
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx
deleted file mode 100644
index ccb80ef335e..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB ODBC Connector on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-odbc
-sudo zypper -n install edb-odbc-devel
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx
index ea4234707aa..9ca8ffaa954 100644
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx
@@ -12,16 +12,12 @@ redirects:
 navigation:
   - odbc_rhel_9
   - odbc_rhel_8
-  - odbc_rhel_7
   - odbc_other_linux_9
   - odbc_other_linux_8
-  - odbc_centos_7
   - odbc_sles_15
-  - odbc_sles_12
   - odbc_ubuntu_22
   - odbc_ubuntu_20
   - odbc_debian_11
-  - odbc_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -32,14 +28,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](odbc_rhel_8)
 
-- [RHEL 7](odbc_rhel_7)
-
 - [Oracle Linux (OL) 9](odbc_rhel_9)
 
 - [Oracle Linux (OL) 8](odbc_rhel_8)
 
-- [Oracle Linux (OL) 7](odbc_rhel_7)
-
 - [Rocky Linux 9](odbc_other_linux_9)
 
 - [Rocky Linux 8](odbc_other_linux_8)
@@ -48,14 +40,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](odbc_other_linux_8)
 
-- [CentOS 7](odbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](odbc_sles_15)
 
-- [SLES 12](odbc_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](odbc_ubuntu_22)
@@ -63,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](odbc_ubuntu_20)
 
 - [Debian 11](odbc_debian_11)
-
-- [Debian 10](odbc_debian_10)
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx
deleted file mode 100644
index 1a2b3f5a2a9..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB ODBC Connector on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-odbc
-sudo yum -y install edb-odbc-devel
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx
deleted file mode 100644
index 4751538a48c..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB ODBC Connector on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-odbc
-sudo apt-get -y install edb-odbc-dev
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx
deleted file mode 100644
index d3a7625e92c..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB ODBC Connector on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-odbc
-sudo yum -y install edb-odbc-devel
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx
deleted file mode 100644
index 4eea918c602..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB ODBC Connector on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-odbc
-sudo zypper -n install edb-odbc-devel
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx
deleted file mode 100644
index f1a0276bace..00000000000
--- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Ubuntu 18.04
-title: Installing EDB ODBC Connector on Ubuntu 18.04 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-odbc
-sudo apt-get -y install edb-odbc-dev
-```
diff --git a/product_docs/docs/odbc_connector/13/installing/upgrading.mdx b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx
index f48c1d639a4..0900d3c289a 100644
--- a/product_docs/docs/odbc_connector/13/installing/upgrading.mdx
+++ b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx
@@ -27,7 +27,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
 
 ## Upgrading from Debian/Ubuntu installations
diff --git a/product_docs/docs/odbc_connector/16/installing/index.mdx b/product_docs/docs/odbc_connector/16/installing/index.mdx
index 5a2a6de27ec..adfc7806b5f 100644
--- a/product_docs/docs/odbc_connector/16/installing/index.mdx
+++ b/product_docs/docs/odbc_connector/16/installing/index.mdx
@@ -14,8 +14,8 @@ redirects:
   - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - windows
   - upgrading
@@ -27,25 +27,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/odbc_rhel_9), [RHEL 8](linux_x86_64/odbc_rhel_8), [RHEL 7](linux_x86_64/odbc_rhel_7)
+- [RHEL 9](linux_x86_64/odbc_rhel_9), [RHEL 8](linux_x86_64/odbc_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/odbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/odbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/odbc_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/odbc_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/odbc_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/odbc_other_linux_9), [Rocky Linux 8](linux_x86_64/odbc_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/odbc_other_linux_9), [AlmaLinux 8](linux_x86_64/odbc_other_linux_8)
 
-- [CentOS 7](linux_x86_64/odbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/odbc_sles_15), [SLES 12](linux_x86_64/odbc_sles_12)
+- [SLES 15](linux_x86_64/odbc_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/odbc_ubuntu_22), [Ubuntu 20.04](linux_x86_64/odbc_ubuntu_20)
 
-- [Debian 12](linux_x86_64/odbc_debian_12), [Debian 11](linux_x86_64/odbc_debian_11), [Debian 10](linux_x86_64/odbc_debian_10)
+- [Debian 12](linux_x86_64/odbc_debian_12), [Debian 11](linux_x86_64/odbc_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -55,7 +53,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/odbc_sles_15), [SLES 12](linux_ppc64le/odbc_sles_12)
+- [SLES 15](linux_ppc64le/odbc_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/index.mdx b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/index.mdx
index 2051bc77f7d..7b1b0fa0a28 100644
--- a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - odbc_rhel_9
   - odbc_rhel_8
   - odbc_sles_15
-  - odbc_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](odbc_sles_15)
-
-- [SLES 12](odbc_sles_12)
diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/index.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/index.mdx
index 99add000643..3240664ab83 100644
--- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - odbc_rhel_9
   - odbc_rhel_8
-  - odbc_rhel_7
   - odbc_other_linux_9
   - odbc_other_linux_8
-  - odbc_centos_7
   - odbc_sles_15
-  - odbc_sles_12
   - odbc_ubuntu_22
   - odbc_ubuntu_20
   - odbc_debian_12
   - odbc_debian_11
-  - odbc_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](odbc_rhel_8)
 
-- [RHEL 7](odbc_rhel_7)
-
 - [Oracle Linux (OL) 9](odbc_rhel_9)
 
 - [Oracle Linux (OL) 8](odbc_rhel_8)
 
-- [Oracle Linux (OL) 7](odbc_rhel_7)
-
 - [Rocky Linux 9](odbc_other_linux_9)
 
 - [Rocky Linux 8](odbc_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](odbc_other_linux_8)
 
-- [CentOS 7](odbc_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](odbc_sles_15)
 
-- [SLES 12](odbc_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](odbc_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](odbc_debian_12)
 
 - [Debian 11](odbc_debian_11)
-
-- [Debian 10](odbc_debian_10)
diff --git a/product_docs/docs/odbc_connector/16/installing/upgrading.mdx b/product_docs/docs/odbc_connector/16/installing/upgrading.mdx
index f48c1d639a4..0900d3c289a 100644
--- a/product_docs/docs/odbc_connector/16/installing/upgrading.mdx
+++ b/product_docs/docs/odbc_connector/16/installing/upgrading.mdx
@@ -27,7 +27,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |         Operating system         |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
 
 ## Upgrading from Debian/Ubuntu installations
diff --git a/product_docs/docs/pem/8/changing_default_port.mdx b/product_docs/docs/pem/8/changing_default_port.mdx
index 056b3c820e9..7f7f610c077 100644
--- a/product_docs/docs/pem/8/changing_default_port.mdx
+++ b/product_docs/docs/pem/8/changing_default_port.mdx
@@ -4,7 +4,7 @@ title: "Changing the default port"
 
 By default, the 8443 port is assigned for the web services at the time of configuration of the PEM server. You can change the port after configuration by changing a few parameters in the Apache configuration files. The Apache configuration files names and locations are platform specific.
 
-## For RHEL and CentOS
+## For RHEL
 
 
 1. Edit the file `/etc/httpd/conf.d/edb-ssl-pem.conf`, replacing 8443 with your port number in the following parameters:
diff --git a/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
index 6870969a8ca..fa251fd692f 100644
--- a/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
+++ b/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
@@ -110,7 +110,7 @@ Restart the database server to reflect the changes:
 systemctl restart <POSTGRES_SERVICE_NAME>
 ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 ## 5. Obtain and view the initial ticket
 
@@ -176,7 +176,7 @@ If the PEM server uses Kerberos authentication:
     systemctl reload <POSTGRES_SERVICE_NAME>
     ```
 
-    `POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+    `POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 !!! Note
     If you're using PostgreSQL or EDB Postgres Advanced Server 12 or later, then you can specify connection type as `hostgssenc` to allow only gss-encrypted connection.
diff --git a/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
index 35008f01176..3067089441e 100644
--- a/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
+++ b/product_docs/docs/pem/8/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
@@ -131,7 +131,7 @@ Restart the database server to reflect the changes:
     systemctl restart <POSTGRES_SERVICE_NAME>
     ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 ## 5. Obtain and view the initial ticket
 
@@ -197,7 +197,7 @@ Edit the entries at the top in `pg_hba.conf` to use the gss authentication metho
     systemctl reload <POSTGRES_SERVICE_NAME>
     ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 !!! Note
     You can't specify the connection type as `hostgssenc`. Windows doesn't support gss encrypted connection.
diff --git a/product_docs/docs/pem/8/installing/creating_pem_repository_in_isolated_network.mdx b/product_docs/docs/pem/8/installing/creating_pem_repository_in_isolated_network.mdx
index bee4f4d1251..d212a782741 100644
--- a/product_docs/docs/pem/8/installing/creating_pem_repository_in_isolated_network.mdx
+++ b/product_docs/docs/pem/8/installing/creating_pem_repository_in_isolated_network.mdx
@@ -54,18 +54,16 @@ To create and use a local repository:
     gpgcheck=0
     ```
 
-6.  After specifying the location and connection information for your local repository, you can use yum commands to install or upgrade PEM server:
+6.  After specifying the location and connection information for your local repository, you can use dnf commands to install or upgrade PEM server:
 
     To install PEM server:
 
     ```shell
-    yum install edb-pem
+    dnf install edb-pem
     ```
 
     To upgrade PEM server:
 
     ```shell
-    yum upgrade edb-pem
+    dnf upgrade edb-pem
     ```
-
-For more information about creating a local yum repository, see [Create Local Repos](https://wiki.centos.org/HowTos/CreateLocalRepos) in the Centos documentation.
diff --git a/product_docs/docs/pem/8/installing/index.mdx b/product_docs/docs/pem/8/installing/index.mdx
index 97aac47a38b..0e2ad9eb734 100644
--- a/product_docs/docs/pem/8/installing/index.mdx
+++ b/product_docs/docs/pem/8/installing/index.mdx
@@ -30,25 +30,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pem_rhel_9), [RHEL 8](linux_x86_64/pem_rhel_8), [RHEL 7](linux_x86_64/pem_rhel_7)
+- [RHEL 9](linux_x86_64/pem_rhel_9), [RHEL 8](linux_x86_64/pem_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pem_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pem_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pem_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pem_other_linux_9), [Rocky Linux 8](linux_x86_64/pem_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pem_other_linux_9), [AlmaLinux 8](linux_x86_64/pem_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pem_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pem_sles_15), [SLES 12](linux_x86_64/pem_sles_12)
+- [SLES 15](linux_x86_64/pem_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pem_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pem_ubuntu_20)
 
-- [Debian 11](linux_x86_64/pem_debian_11), [Debian 10](linux_x86_64/pem_debian_10)
+- [Debian 11](linux_x86_64/pem_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -58,7 +56,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pem_sles_15), [SLES 12](linux_ppc64le/pem_sles_12)
+- [SLES 15](linux_ppc64le/pem_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx b/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx
index bd416f10392..a0ca47f1991 100644
--- a/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pem/8/installing/linux_ppc64le/index.mdx
@@ -14,7 +14,6 @@ navigation:
   - pem_rhel_9
   - pem_rhel_8
   - pem_sles_15
-  - pem_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,5 +27,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_sles_15)
-
-- [SLES 12](pem_sles_12)
diff --git a/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx b/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx
index 9fbaa1650f9..3797145570b 100644
--- a/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pem/8/installing/linux_x86_64/index.mdx
@@ -13,16 +13,12 @@ redirects:
 navigation:
   - pem_rhel_9
   - pem_rhel_8
-  - pem_rhel_7
   - pem_other_linux_9
   - pem_other_linux_8
-  - pem_centos_7
   - pem_sles_15
-  - pem_sles_12
   - pem_ubuntu_22
   - pem_ubuntu_20
   - pem_debian_11
-  - pem_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pem_rhel_8)
 
-- [RHEL 7](pem_rhel_7)
-
 - [Oracle Linux (OL) 9](pem_rhel_9)
 
 - [Oracle Linux (OL) 8](pem_rhel_8)
 
-- [Oracle Linux (OL) 7](pem_rhel_7)
-
 - [Rocky Linux 9](pem_other_linux_9)
 
 - [Rocky Linux 8](pem_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pem_other_linux_8)
 
-- [CentOS 7](pem_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_sles_15)
 
-- [SLES 12](pem_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pem_ubuntu_22)
@@ -64,5 +52,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](pem_ubuntu_20)
 
 - [Debian 11](pem_debian_11)
-
-- [Debian 10](pem_debian_10)
diff --git a/product_docs/docs/pem/8/installing/prerequisites.mdx b/product_docs/docs/pem/8/installing/prerequisites.mdx
index 68b72c801fd..6ca5086b718 100644
--- a/product_docs/docs/pem/8/installing/prerequisites.mdx
+++ b/product_docs/docs/pem/8/installing/prerequisites.mdx
@@ -40,12 +40,6 @@ To install a PEM server on Linux, perform this preliminary configuration:
         dnf install edb-as<x>-server-sslutils
         ```
 
-        For RHEL/OL/CentOS 7:
-          
-        ```shell
-        yum install edb-as<x>-server-sslutils
-        ```
-
         For Debian/Ubuntu:
           
         ```shell
@@ -66,12 +60,6 @@ To install a PEM server on Linux, perform this preliminary configuration:
         dnf install sslutils_<x> postgresql<x>-contrib
         ```
 
-        For RHEL/OL/CentOS 7:
-          
-        ```shell
-        yum install sslutils_<x> postgresql<x>-contrib
-        ```
-
         For Debian/Ubuntu:
           
         ```shell
@@ -91,12 +79,6 @@ To install a PEM server on Linux, perform this preliminary configuration:
         dnf install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
         ```
 
-        For RHEL/OL/CentOS 7:
-          
-        ```shell
-        yum install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
-        ```
-
         For Debian/Ubuntu:
           
         ```shell
@@ -117,7 +99,7 @@ To install a PEM server on Linux, perform this preliminary configuration:
 
 4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
 
-     For RHEL/Rocky Linux/AlmaLinux/OL/CentOS/SLES:
+     For RHEL/Rocky Linux/AlmaLinux/SLES:
 
     ```shell
     firewall-cmd --permanent --zone=public --add-port=8443/tcp
@@ -139,12 +121,6 @@ To install a PEM server on Linux, perform this preliminary configuration:
      dnf upgrade
      ```
 
-     For RHEL/OL/CentOS 7:
-   
-     ```shell
-    yum upgrade
-    ```
-
     For Debian/Ubuntu:
    
     ```shell
diff --git a/product_docs/docs/pem/8/installing_pem_agent/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/index.mdx
index 3f9db80c7c1..77fa67c0278 100644
--- a/product_docs/docs/pem/8/installing_pem_agent/index.mdx
+++ b/product_docs/docs/pem/8/installing_pem_agent/index.mdx
@@ -25,25 +25,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pem_agent_rhel_9), [RHEL 8](linux_x86_64/pem_agent_rhel_8), [RHEL 7](linux_x86_64/pem_agent_rhel_7)
+- [RHEL 9](linux_x86_64/pem_agent_rhel_9), [RHEL 8](linux_x86_64/pem_agent_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pem_agent_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_agent_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pem_agent_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pem_agent_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_agent_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pem_agent_other_linux_9), [Rocky Linux 8](linux_x86_64/pem_agent_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pem_agent_other_linux_9), [AlmaLinux 8](linux_x86_64/pem_agent_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pem_agent_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pem_agent_sles_15), [SLES 12](linux_x86_64/pem_agent_sles_12)
+- [SLES 15](linux_x86_64/pem_agent_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pem_agent_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pem_agent_ubuntu_20)
 
-- [Debian 11](linux_x86_64/pem_agent_debian_11), [Debian 10](linux_x86_64/pem_agent_debian_10)
+- [Debian 11](linux_x86_64/pem_agent_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -53,7 +51,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pem_agent_sles_15), [SLES 12](linux_ppc64le/pem_agent_sles_12)
+- [SLES 15](linux_ppc64le/pem_agent_sles_15)
 
 ## Windows
 
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx
index 2313da49884..a574d6584c9 100644
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - pem_agent_rhel_9
   - pem_agent_rhel_8
   - pem_agent_sles_15
-  - pem_agent_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_agent_sles_15)
-
-- [SLES 12](pem_agent_sles_12)
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx
deleted file mode 100644
index 84a42ad39bf..00000000000
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager agent on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx
index 4e4e010e3bc..82b0ca793a9 100644
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx
+++ b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/index.mdx
@@ -12,16 +12,12 @@ redirects:
 navigation:
   - pem_agent_rhel_9
   - pem_agent_rhel_8
-  - pem_agent_rhel_7
   - pem_agent_other_linux_9
   - pem_agent_other_linux_8
-  - pem_agent_centos_7
   - pem_agent_sles_15
-  - pem_agent_sles_12
   - pem_agent_ubuntu_22
   - pem_agent_ubuntu_20
   - pem_agent_debian_11
-  - pem_agent_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -32,14 +28,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pem_agent_rhel_8)
 
-- [RHEL 7](pem_agent_rhel_7)
-
 - [Oracle Linux (OL) 9](pem_agent_rhel_9)
 
 - [Oracle Linux (OL) 8](pem_agent_rhel_8)
 
-- [Oracle Linux (OL) 7](pem_agent_rhel_7)
-
 - [Rocky Linux 9](pem_agent_other_linux_9)
 
 - [Rocky Linux 8](pem_agent_other_linux_8)
@@ -48,14 +40,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pem_agent_other_linux_8)
 
-- [CentOS 7](pem_agent_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_agent_sles_15)
 
-- [SLES 12](pem_agent_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pem_agent_ubuntu_22)
@@ -63,5 +51,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](pem_agent_ubuntu_20)
 
 - [Debian 11](pem_agent_debian_11)
-
-- [Debian 10](pem_agent_debian_10)
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx
deleted file mode 100644
index 52dbce6a9b5..00000000000
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Postgres Enterprise Manager agent on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx
deleted file mode 100644
index aad4f555112..00000000000
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Postgres Enterprise Manager agent on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx
deleted file mode 100644
index caf3b0362ce..00000000000
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Postgres Enterprise Manager agent on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx b/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx
deleted file mode 100644
index 6008b16539f..00000000000
--- a/product_docs/docs/pem/8/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager agent on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/8/managing_database_server.mdx b/product_docs/docs/pem/8/managing_database_server.mdx
index 4dc50d2a4ec..0ee4ed7d1d4 100644
--- a/product_docs/docs/pem/8/managing_database_server.mdx
+++ b/product_docs/docs/pem/8/managing_database_server.mdx
@@ -89,6 +89,6 @@ A service script for the database server allows the PEM server to start, stop, o
 The Postgres server on which the PEM server resides must contain a service script. Postgres installers in Windows generated by EDB create a service script for you. If you're using a Postgres server from another source like native packages, you must provide a service script.
 
 !!! Note 
-    On CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x, the service script resides in `/usr/lib/systemd/system`.
+    On Rocky Linux or RHEL, the service script resides in `/usr/lib/systemd/system`.
 
 For information about customizing a Postgres service, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/static/server-start.html).
\ No newline at end of file
diff --git a/product_docs/docs/pem/8/managing_pem_server.mdx b/product_docs/docs/pem/8/managing_pem_server.mdx
index 70ea10fed32..da45af163b6 100644
--- a/product_docs/docs/pem/8/managing_pem_server.mdx
+++ b/product_docs/docs/pem/8/managing_pem_server.mdx
@@ -44,7 +44,7 @@ Where `x` indicates the server version number.
 
 You can use the service script to control the service.
 
--   To control a service on RHEL or CentOS version 7.x or 8.x, at the command prompt, assume superuser privileges and issue the command:
+-   To control a service on RHEL 8.x, at the command prompt, assume superuser privileges and issue the command:
 
     ```shell
     systemctl <service_name> <action>
@@ -93,7 +93,7 @@ If Linux responds with an answer like the following, httpd isn't running:
 user 13321 13267 0 07:37 pts/1 00:00:00 grep httpd
 ```
 
-To start the service on a CentOS or RHEL 7.x or 8.x system, use the command:
+To start the service on a RHEL 8.x system, use the command:
 
 ```shell
 systemctl start httpd
diff --git a/product_docs/docs/pem/8/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx b/product_docs/docs/pem/8/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx
index 53e813fc902..c4e345a6502 100644
--- a/product_docs/docs/pem/8/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx
+++ b/product_docs/docs/pem/8/pem_online_help/02_toc_pem_agent/03_pem_agent_start_pem_agent.mdx
@@ -18,7 +18,7 @@ Where `action` specifies the action taken by the service. Specify:
 -   restart to stop and then start the service.
 -   status to check the status of the service.
 
-To determine if a service is running on RHEL or CentOS version 7.x, open a command line, and issue the command:
+To determine if a service is running on RHEL, open a command line, and issue the command:
 
 > `systemctl pemagent action`
 
diff --git a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/installing_the_sql_profiler_plugin.mdx b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/installing_the_sql_profiler_plugin.mdx
index 29f7798b145..513f0bb4557 100644
--- a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/installing_the_sql_profiler_plugin.mdx
+++ b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/installing_the_sql_profiler_plugin.mdx
@@ -30,20 +30,16 @@ You can use the graphical installer to install any version of SQL Profiler on th
 
 When the installation is complete, the SQL Profiler plugin is ready to configure.
 
-## Installing SQL Profiler on RHEL/CentOS/OL
+## Installing SQL Profiler on RHEL
 
 !!! Note
     You might need to add the `sslutils` package to your PostgreSQL database servers before installing SQL Profiler.
 
-If you already configured the EDB repository on your system, you can use `yum` or `dnf` to install SQL Profiler.
+If you already configured the EDB repository on your system, you can use `dnf` to install SQL Profiler.
 
 For PostgreSQL,
 
 ```shell
-yum install sqlprofiler_<X>
-
-or
-
 dnf install sqlprofiler_<X>
 ```
 
diff --git a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/uninstalling_sql_profiler.mdx b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/uninstalling_sql_profiler.mdx
index a168c5b3cd0..4254f158c7d 100644
--- a/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/uninstalling_sql_profiler.mdx
+++ b/product_docs/docs/pem/8/profiling_workloads/pem_sqlprofiler/uninstalling_sql_profiler.mdx
@@ -21,7 +21,7 @@ To stop the service:
 
 After stopping the Postgres server, delete the existing SQL Profiler query set on each node by invoking the `uninstall-sql-profiler.sql` script. By default, the script resides in the `share\contrib` directory under your EDB Postgres Advanced Server or PostgreSQL installation.
 
-## Uninstalling SQL Profiler from CentOS or RHEL hosts
+## Uninstalling SQL Profiler from RHEL hosts
 
 To uninstall a SQL Profiler installation that resides on a Linux host, delete the existing SQL Profiler query set on each node by invoking the `uninstall-sql-profiler.sql` script.
 
diff --git a/product_docs/docs/pem/8/tuning_performance/performance_diagnostic.mdx b/product_docs/docs/pem/8/tuning_performance/performance_diagnostic.mdx
index 89b35c0c654..1ac5df4a62b 100644
--- a/product_docs/docs/pem/8/tuning_performance/performance_diagnostic.mdx
+++ b/product_docs/docs/pem/8/tuning_performance/performance_diagnostic.mdx
@@ -11,9 +11,9 @@ redirects:
 The Performance Diagnostic dashboard analyzes the database performance for Postgres instances by monitoring the wait events. To display the diagnostic graphs, PEM uses the data collected by the EDB Wait States module.
 
 !!! Note
-    - For PostgreSQL databases, Performance Diagnostic is supported for version 10 or later installed on the supported CentOS or RHEL platforms.
+    - For PostgreSQL databases, Performance Diagnostic is supported for version 10 or later installed on the supported RHEL platforms.
 
-    - For EDB Postgres Extended databases, Performance Diagnostic is supported for version 11 or later on the supported CentOS or RHEL platforms.
+    - For EDB Postgres Extended databases, Performance Diagnostic is supported for version 11 or later on the supported RHEL platforms.
 
 For more information on EDB wait states, see [EDB wait states](/epas/latest/epas_guide/13_performance_analysis_and_tuning/#edb-wait-states).
 
diff --git a/product_docs/docs/pem/8/uninstalling/uninstalling_on_linux.mdx b/product_docs/docs/pem/8/uninstalling/uninstalling_on_linux.mdx
index 6914d51a49b..7caae918c58 100644
--- a/product_docs/docs/pem/8/uninstalling/uninstalling_on_linux.mdx
+++ b/product_docs/docs/pem/8/uninstalling/uninstalling_on_linux.mdx
@@ -16,9 +16,9 @@ If you uninstall the PEM server package from a host, the PEM Agent package insta
 !!! Note
     Before uninstalling the PEM Agent, you need to de-register the agent first. You can de-register the agent using the `pemworker` command-line utility. After that, you can proceed with the uninstallation steps.
 
-## Uninstalling PEM components from CentOS or RHEL or Rocky Linux or AlmaLinux hosts
+## Uninstalling PEM components from RHEL or Rocky Linux or AlmaLinux hosts
 
-You can use variations of the `rpm`, `yum remove`, or `yum erase` commands to remove the installed packages from CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory.
+You can use variations of the `rpm` command to remove the installed packages from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory.
 
 -   Include the `-e` option when invoking the rpm command to remove an installed package; the command syntax is:
 
@@ -26,18 +26,6 @@ You can use variations of the `rpm`, `yum remove`, or `yum erase` commands to re
     rpm -e package_name
     ```
 
--   You can use the `yum remove` command to remove the PEM Server or Agent package installed by yum. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
-
-    ```shell
-    yum remove package_name
-    ```
-
--   You can use the `yum erase` command to remove the pem server or Agent package along with the `edb-pem` and `edb-pem-docs` dependencies. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
-
-    ```shell
-    yum erase package_name
-    ```
-
 Where `package_name` is the name of the package that you would like to remove.
 
 -   You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on Rocky Linux or AlmaLinux or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
diff --git a/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx b/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx
index 9e1adf5f80f..43149fd72ff 100644
--- a/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx
+++ b/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx
@@ -182,7 +182,7 @@ Before starting the server migration, make sure that the firewalls between the s
 
 7.  Stop the database server on the target host.
 
-    To stop the PEM server on CentOS or RHEL 7.x or 8.x, use the command:
+    To stop the PEM server on RHEL 8.x, use the command:
 
     ```shell
     systemctl stop <service_name>
diff --git a/product_docs/docs/pem/8/upgrading/upgrading_backend_database.mdx b/product_docs/docs/pem/8/upgrading/upgrading_backend_database.mdx
index 6057064405c..43dc5fe5615 100644
--- a/product_docs/docs/pem/8/upgrading/upgrading_backend_database.mdx
+++ b/product_docs/docs/pem/8/upgrading/upgrading_backend_database.mdx
@@ -234,7 +234,7 @@ You can find more information about using pg_upgrade at [pg_upgrade](http://www.
 
 3.  Stop the services of both the old backend database and the new backend database.
 
-    On RHEL or CentOS 7.x or 8.x, open a command line and assume the identity of a superuser. Enter the command:
+    On RHEL 8.x, open a command line and assume the identity of a superuser. Enter the command:
 
     ```shell
     systemctl <service_name> stop
@@ -415,7 +415,7 @@ You can find more information about using pg_upgrade at [pg_upgrade](http://www.
 
 8.  Restart the service of the new backend database.
 
-    On RHEL or CentOS 7.x or 8.x, at the command line as superuser enter:
+    On RHEL 8.x, at the command line as superuser enter:
 
     ```shell
     systemctl stop <service_name>
diff --git a/product_docs/docs/pem/8/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx b/product_docs/docs/pem/8/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
index bc49e26a638..cfaad50ce2d 100644
--- a/product_docs/docs/pem/8/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
+++ b/product_docs/docs/pem/8/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
@@ -23,14 +23,7 @@ PEM depends on third-party components from the vendor repository, including pyth
 
 The minimum version required for openssl is 1.0.2k. If you're using a version of PostgreSQL or EDB Postgres Advanced Server earlier than version 10, before the upgrade you must install the `libs` package for version 10 or above on the system where the PEM server is installed. Use the following platform-specific commands to install the `libs` version 10 or above on your host.
 
-### Prerequisites to upgrade a PEM installation on a CentOS or RHEL host
-
-To upgrade packages on a CentOS or RHEL 7.x host:
-
-```shell
-yum update
-yum upgrade
-```
+### Prerequisites to upgrade a PEM installation on a RHEL host
 
 To upgrade packages on a Rocky Linux or AlmaLinux or RHEL 8.x host:
 
@@ -103,15 +96,9 @@ Where `<X>` is the PostgreSQL or EDB Postgres Advanced Server version whose `lib
 
 You can use native packages to upgrade existing PEM agents initially installed using native packages. The upgrade process doesn't update the PEM agent configuration file. After installing the new agent, you must manually copy the configuration file of the existing agent to the new installation location.
 
-### Upgrading the PEM agent on a CentOS or RHEL host
-
-For CentOS or RHEL 7.x or RHEL 8.x, to upgrade a PEM agent, use the following command:
-
-```shell
-yum upgrade edb-pem-agent
-```
+### Upgrading the PEM agent on a RHEL host
 
-For Rocky Linux or AlmaLinux or RHEL 8.x, you can also use the following command:
+For RHEL 8.x, to upgrade a PEM agent, use the following command:
 
 ```shell
 dnf upgrade edb-pem-agent
@@ -139,24 +126,15 @@ If you initially used native packages to install your PEM server, you can use na
 
 If you want to upgrade a PEM server that is installed on a machine in an isolated network, you need to create a PEM repository on that machine before you upgrade the PEM server. For more information about creating a PEM repository on an isolated network, see [Creating a PEM Repository on an Isolated Network](/pem/8/installing/creating_pem_repository_in_isolated_network/).
 
-### Upgrading a PEM server on a CentOS, Rocky Linux, AlmaLinux, or RHEL host
+### Upgrading a PEM server on a Rocky Linux, AlmaLinux, or RHEL host
 
-To use an RPM package to upgrade an existing RPM installation, you can use the `yum` package manager to upgrade the installed version of the PEM server on CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x:
-
-```shell
-yum upgrade edb-pem
-```
-
-You can also use the `dnf` command on Rocky Linux/AlmaLinux/RHEL 8.x:
+To use an RPM package to upgrade an existing RPM installation, you can use the `dnf` package manager to upgrade the installed version of the PEM server on Rocky Linux/AlmaLinux/RHEL 8.x:
 
 ```shell
 dnf upgrade edb-pem
 ```
 
-!!! Note
-    If you're doing a fresh installation of the PEM server on CentOS or RHEL 7.x host, the installer installs the `edb-python3-mod_wsgi` package along with the installation. The package is a requirement of the operating system. If you are upgrading the PEM server on CentOS or RHEL 7.x host, the`the edb-python3-mod_wsgi` packages replaces the `mod_wsgi package`  package to meet the requirements of the operating system.
-
-After upgrading the PEM server using yum or the `dnf` command, you must configure the PEM server. For detailed information, see [Configuring the PEM server](#configuring-the-pem-server).
+After upgrading the PEM server using the `dnf` command, you must configure the PEM server. For detailed information, see [Configuring the PEM server](#configuring-the-pem-server).
 
 ### Upgrading the PEM server on a Debian or Ubuntu host
 
diff --git a/product_docs/docs/pem/9/changing_default_port.mdx b/product_docs/docs/pem/9/changing_default_port.mdx
index cbbb6f419bd..d6764efa1d8 100644
--- a/product_docs/docs/pem/9/changing_default_port.mdx
+++ b/product_docs/docs/pem/9/changing_default_port.mdx
@@ -4,7 +4,7 @@ title: "Changing the default port"
 
 By default, the 8443 port is assigned for the web services at the time of configuration of the PEM server. You can change the port after configuration by changing a few parameters in the Apache configuration files. The Apache configuration files names and locations are platform specific.
 
-## For RHEL and CentOS
+## For RHEL
 
 
 1. Edit the file `/etc/httpd/conf.d/edb-ssl-pem.conf`, replacing 8443 with your port number in the following parameters:
diff --git a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
index 2c54a98aa69..8b296f9eb25 100644
--- a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
+++ b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_kerberos_authentication.mdx
@@ -109,7 +109,7 @@ Restart the database server to reflect the changes:
 systemctl restart <POSTGRES_SERVICE_NAME>
 ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on a `RHEL` or Rocky Linux platforms.
 
 ## 5. Obtain and view the initial ticket
 
@@ -175,7 +175,7 @@ If the PEM server uses Kerberos authentication:
     systemctl reload <POSTGRES_SERVICE_NAME>
     ```
 
-    `POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+    `POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on a `RHEL` or Rocky Linux platforms.
 
 !!! Note
     If you're using PostgreSQL or EDB Postgres Advanced Server 12 or later, then you can specify connection type as `hostgssenc` to allow only gss-encrypted connection.
diff --git a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
index 1fd3e75a9be..c7b270895d4 100644
--- a/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
+++ b/product_docs/docs/pem/9/considerations/authentication_options/configuring_the_pem_server_to_use_windows_kerberos_server.mdx
@@ -131,7 +131,7 @@ Restart the database server to reflect the changes:
     systemctl restart <POSTGRES_SERVICE_NAME>
     ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 ## 5. Obtain and view the initial ticket
 
@@ -197,7 +197,7 @@ Edit the entries at the top in `pg_hba.conf` to use the gss authentication metho
     systemctl reload <POSTGRES_SERVICE_NAME>
     ```
 
-`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on CentOS or `RHEL` or Rocky Linux platforms.
+`POSTGRES_SERVICE_NAME` is the service name of the Postgres (PostgreSQL/EDB Postgres Advanced Server) database, for example, `postgresql-13` for PostgreSQL 13 database on RHEL or Rocky Linux platforms.
 
 !!! Note
     You can't specify the connection type as `hostgssenc`. Windows doesn't support gss encrypted connection.
diff --git a/product_docs/docs/pem/9/installing/creating_pem_repository_in_isolated_network.mdx b/product_docs/docs/pem/9/installing/creating_pem_repository_in_isolated_network.mdx
index 60c01c76ea4..f7a127300a2 100644
--- a/product_docs/docs/pem/9/installing/creating_pem_repository_in_isolated_network.mdx
+++ b/product_docs/docs/pem/9/installing/creating_pem_repository_in_isolated_network.mdx
@@ -55,18 +55,16 @@ To create and use a local repository:
     gpgcheck=0
     ```
 
-6.  After specifying the location and connection information for your local repository, you can use yum commands to install or upgrade PEM server:
+6.  After specifying the location and connection information for your local repository, you can use dnf commands to install or upgrade PEM server:
 
     To install PEM server:
 
     ```shell
-    yum install edb-pem
+    dnf install edb-pem
     ```
 
     To upgrade PEM server:
 
     ```shell
-    yum upgrade edb-pem
+    dnf upgrade edb-pem
     ```
-
-For more information about creating a local yum repository, see [Create Local Repos](https://wiki.centos.org/HowTos/CreateLocalRepos) in the Centos documentation.
diff --git a/product_docs/docs/pem/9/installing/index.mdx b/product_docs/docs/pem/9/installing/index.mdx
index db45186dcdb..38af403dee0 100644
--- a/product_docs/docs/pem/9/installing/index.mdx
+++ b/product_docs/docs/pem/9/installing/index.mdx
@@ -31,25 +31,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pem_rhel_9), [RHEL 8](linux_x86_64/pem_rhel_8), [RHEL 7](linux_x86_64/pem_rhel_7)
+- [RHEL 9](linux_x86_64/pem_rhel_9), [RHEL 8](linux_x86_64/pem_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pem_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pem_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pem_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pem_other_linux_9), [Rocky Linux 8](linux_x86_64/pem_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pem_other_linux_9), [AlmaLinux 8](linux_x86_64/pem_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pem_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pem_sles_15), [SLES 12](linux_x86_64/pem_sles_12)
+- [SLES 15](linux_x86_64/pem_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pem_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pem_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pem_debian_12), [Debian 11](linux_x86_64/pem_debian_11), [Debian 10](linux_x86_64/pem_debian_10)
+- [Debian 12](linux_x86_64/pem_debian_12), [Debian 11](linux_x86_64/pem_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -59,7 +57,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pem_sles_15), [SLES 12](linux_ppc64le/pem_sles_12)
+- [SLES 15](linux_ppc64le/pem_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx
index 9f844d72be3..db0193ea82e 100644
--- a/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pem/9/installing/linux_ppc64le/index.mdx
@@ -14,7 +14,6 @@ navigation:
   - pem_rhel_9
   - pem_rhel_8
   - pem_sles_15
-  - pem_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,5 +27,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_sles_15)
-
-- [SLES 12](pem_sles_12)
diff --git a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx
deleted file mode 100644
index bf1021cf9ed..00000000000
--- a/product_docs/docs/pem/9/installing/linux_ppc64le/pem_sles_12.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager server on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_ppcle/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_ppcle/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_ppcle/
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database.
-
-   You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps.
-
-2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file.
-
-   Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).)
-
-   - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different.
-
-   - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`.
-
-   !!! Note
-   If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file).
-
-   If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
-   !!!
-
-3. Verify that the `sslutils` extension is installed on your Postgres server.
-
-   If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module.
-
-   - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `<x>` is the EDB Postgres Advanced server version.
-
-     ```shell
-     sudo zypper install edb-as<x>-server-sslutils
-     ```
-
-   - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version.
-     ```shell
-     sudo zypper install sslutils_<x> postgresql<x>-contrib
-     ```
-   - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version.
-     ```shell
-     sudo zypper install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
-     ```
-
-4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
-
-   ```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-
-   firewall-cmd --reload
-   ```
-
-5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below.
-   If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md).
-
-   ```shell
-   sudo zypper update
-   ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem
-```
-
-## Initial configuration
-
-```shell
-# You can configure the PEM server using the following command:
-sudo /usr/edb/pem/bin/configure-pem-server.sh
-```
-
-For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/).
-
-!!! Note
-
-    - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory.
-
-## Supported locales
-
-Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors.
diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx
index 68cc4bb8bda..17892bbd3b1 100644
--- a/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pem/9/installing/linux_x86_64/index.mdx
@@ -13,17 +13,13 @@ redirects:
 navigation:
   - pem_rhel_9
   - pem_rhel_8
-  - pem_rhel_7
   - pem_other_linux_9
   - pem_other_linux_8
-  - pem_centos_7
   - pem_sles_15
-  - pem_sles_12
   - pem_ubuntu_22
   - pem_ubuntu_20
   - pem_debian_12
   - pem_debian_11
-  - pem_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -34,14 +30,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pem_rhel_8)
 
-- [RHEL 7](pem_rhel_7)
-
 - [Oracle Linux (OL) 9](pem_rhel_9)
 
 - [Oracle Linux (OL) 8](pem_rhel_8)
 
-- [Oracle Linux (OL) 7](pem_rhel_7)
-
 - [Rocky Linux 9](pem_other_linux_9)
 
 - [Rocky Linux 8](pem_other_linux_8)
@@ -50,14 +42,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pem_other_linux_8)
 
-- [CentOS 7](pem_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_sles_15)
 
-- [SLES 12](pem_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pem_ubuntu_22)
@@ -67,5 +55,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pem_debian_12)
 
 - [Debian 11](pem_debian_11)
-
-- [Debian 10](pem_debian_10)
diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx
deleted file mode 100644
index 76642163e81..00000000000
--- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_centos_7.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Postgres Enterprise Manager server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_centos7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_centos7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_centos7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_centos7_x86/
----
-
-You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation.
-
-After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database.
-
-   You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps.
-
-2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file.
-
-   Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).)
-
-   - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different.
-
-   - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`.
-
-   !!! Note
-   If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file).
-
-   If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
-   !!!
-
-3. Verify that the `sslutils` extension is installed on your Postgres server.
-
-   If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module.
-
-   - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `<x>` is the EDB Postgres Advanced server version.
-
-     ```shell
-     sudo yum install edb-as<x>-server-sslutils
-     ```
-
-   - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version.
-     ```shell
-     sudo yum install sslutils_<x> postgresql<x>-contrib
-     ```
-   - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version.
-     ```shell
-     sudo yum install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
-     ```
-
-4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
-
-   ```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-
-   firewall-cmd --reload
-   ```
-
-5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below.
-   If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md).
-
-   ```shell
-   sudo yum upgrade
-   ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem
-```
-
-## Initial configuration
-
-```shell
-# You can configure the PEM server using the following command:
-sudo /usr/edb/pem/bin/configure-pem-server.sh
-```
-
-For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/).
-
-!!! Note
-
-    - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory.
-
-## Supported locales
-
-Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors.
-
-    - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system.
-
-    - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system.
diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx
deleted file mode 100644
index 65eb2600435..00000000000
--- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_debian_10.mdx
+++ /dev/null
@@ -1,102 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Postgres Enterprise Manager server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_deb10_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_deb10_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_deb10_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_deb10_x86/
----
-
-You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation.
-
-After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database.
-
-   You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps.
-
-2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file.
-
-   Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).)
-
-   - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different.
-
-   - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`.
-
-   !!! Note
-   If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file).
-
-   If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
-   !!!
-
-3. Verify that the `sslutils` extension is installed on your Postgres server.
-
-   If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module.
-
-   - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `<x>` is the EDB Postgres Advanced server version.
-
-     ```shell
-     sudo apt-get install edb-as<x>-server-sslutils
-     ```
-
-   - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version.
-     ```shell
-     sudo apt-get install postgresql-<x>-sslutils
-     ```
-   - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version.
-
-     ```shell
-     sudo apt-get install edb-postgresextended-sslutils-<x>
-     ```
-
-     !!! Note  
-     Debian 10 changed the requirements for accepting certificates.
-
-     - If you want to install the PEM agent on a machine with an old version of sslutils, then you must upgrade sslutils to 1.3. Version 1.3 has a 4096-bit RSA key and sha256 signature algorithm support added to it.
-     - If you don't upgrade sslutils to 1.3, then PEM agent might fail to connect to the PEM backend database server, and it might log the error "ca md too weak"
-
-4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
-
-   ```shell
-   iptables -t filter -A INPUT -p TCP --dport 8443 -j ACCEPT
-   ```
-
-5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below.
-   If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md).
-
-   ```shell
-   sudo apt-get update
-   ```
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-pem
-```
-
-## Initial configuration
-
-```shell
-# You can configure the PEM server using the following command:
-sudo /usr/edb/pem/bin/configure-pem-server.sh
-```
-
-For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/).
-
-!!! Note
-
-    - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory.
-
-## Supported locales
-
-Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors.
diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx
deleted file mode 100644
index dc1d2793526..00000000000
--- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_rhel_7.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Postgres Enterprise Manager server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_rhel7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel7_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel7_x86/
----
-
-You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation.
-
-After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database.
-
-   You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps.
-
-2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file.
-
-   Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).)
-
-   - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different.
-
-   - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`.
-
-   !!! Note
-   If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file).
-
-   If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
-   !!!
-
-3. Verify that the `sslutils` extension is installed on your Postgres server.
-
-   If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module.
-
-   - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `<x>` is the EDB Postgres Advanced server version.
-
-     ```shell
-     sudo yum install edb-as<x>-server-sslutils
-     ```
-
-   - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version.
-     ```shell
-     sudo yum install sslutils_<x> postgresql<x>-contrib
-     ```
-   - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version.
-     ```shell
-     sudo yum install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
-     ```
-
-4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
-
-   ```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-
-   firewall-cmd --reload
-   ```
-
-5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below.
-   If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md).
-
-   ```shell
-   sudo yum upgrade
-   ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem
-```
-
-## Initial configuration
-
-```shell
-# You can configure the PEM server using the following command:
-sudo /usr/edb/pem/bin/configure-pem-server.sh
-```
-
-For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/).
-
-!!! Note
-
-    - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory.
-
-## Supported locales
-
-Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors.
-
-    - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system.
-
-    - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system.
diff --git a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx b/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx
deleted file mode 100644
index cad96c6ef54..00000000000
--- a/product_docs/docs/pem/9/installing/linux_x86_64/pem_sles_12.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager server on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_sles12_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_sles12_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_sles12_x86/
-  - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_sles12_x86/
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database.
-
-   You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps.
-
-2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file.
-
-   Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](/pem/8/installing/configuring_the_pem_server_on_linux.mdx).)
-
-   - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different.
-
-   - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`.
-
-   !!! Note
-   If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file).
-
-   If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
-   !!!
-
-3. Verify that the `sslutils` extension is installed on your Postgres server.
-
-   If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module.
-
-   - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `<x>` is the EDB Postgres Advanced server version.
-
-     ```shell
-     sudo zypper install edb-as<x>-server-sslutils
-     ```
-
-   - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the PostgreSQL version.
-     ```shell
-     sudo zypper install sslutils_<x> postgresql<x>-contrib
-     ```
-   - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `<x>` is the EDB Postgres Extended Server version.
-     ```shell
-     sudo zypper install edb-postgresextended<x>-sslutils edb-postgresextended<x>-contrib
-     ```
-
-4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located:
-
-   ```shell
-   firewall-cmd --permanent --zone=public --add-port=8443/tcp
-
-   firewall-cmd --reload
-   ```
-
-5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below.
-   If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md).
-
-   ```shell
-   sudo zypper update
-   ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem
-```
-
-## Initial configuration
-
-```shell
-# You can configure the PEM server using the following command:
-sudo /usr/edb/pem/bin/configure-pem-server.sh
-```
-
-For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/).
-
-!!! Note
-
-    - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory.
-
-## Supported locales
-
-Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors.
diff --git a/product_docs/docs/pem/9/installing_pem_agent/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/index.mdx
index 2f6c773deb5..23f4bb5a93b 100644
--- a/product_docs/docs/pem/9/installing_pem_agent/index.mdx
+++ b/product_docs/docs/pem/9/installing_pem_agent/index.mdx
@@ -26,25 +26,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pem_agent_rhel_9), [RHEL 8](linux_x86_64/pem_agent_rhel_8), [RHEL 7](linux_x86_64/pem_agent_rhel_7)
+- [RHEL 9](linux_x86_64/pem_agent_rhel_9), [RHEL 8](linux_x86_64/pem_agent_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pem_agent_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_agent_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pem_agent_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pem_agent_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pem_agent_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pem_agent_other_linux_9), [Rocky Linux 8](linux_x86_64/pem_agent_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pem_agent_other_linux_9), [AlmaLinux 8](linux_x86_64/pem_agent_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pem_agent_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pem_agent_sles_15), [SLES 12](linux_x86_64/pem_agent_sles_12)
+- [SLES 15](linux_x86_64/pem_agent_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pem_agent_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pem_agent_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pem_agent_debian_12), [Debian 11](linux_x86_64/pem_agent_debian_11), [Debian 10](linux_x86_64/pem_agent_debian_10)
+- [Debian 12](linux_x86_64/pem_agent_debian_12), [Debian 11](linux_x86_64/pem_agent_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -54,7 +52,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pem_agent_sles_15), [SLES 12](linux_ppc64le/pem_agent_sles_12)
+- [SLES 15](linux_ppc64le/pem_agent_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx
index 31974f8eb70..12c459303f0 100644
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - pem_agent_rhel_9
   - pem_agent_rhel_8
   - pem_agent_sles_15
-  - pem_agent_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_agent_sles_15)
-
-- [SLES 12](pem_agent_sles_12)
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx
deleted file mode 100644
index 2c220ca8ac2..00000000000
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_ppc64le/pem_agent_sles_12.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager agent on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_sles12_ppcle
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx
index 551abcd20ec..cc42a2048e6 100644
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx
+++ b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - pem_agent_rhel_9
   - pem_agent_rhel_8
-  - pem_agent_rhel_7
   - pem_agent_other_linux_9
   - pem_agent_other_linux_8
-  - pem_agent_centos_7
   - pem_agent_sles_15
-  - pem_agent_sles_12
   - pem_agent_ubuntu_22
   - pem_agent_ubuntu_20
   - pem_agent_debian_12
   - pem_agent_debian_11
-  - pem_agent_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pem_agent_rhel_8)
 
-- [RHEL 7](pem_agent_rhel_7)
-
 - [Oracle Linux (OL) 9](pem_agent_rhel_9)
 
 - [Oracle Linux (OL) 8](pem_agent_rhel_8)
 
-- [Oracle Linux (OL) 7](pem_agent_rhel_7)
-
 - [Rocky Linux 9](pem_agent_other_linux_9)
 
 - [Rocky Linux 8](pem_agent_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pem_agent_other_linux_8)
 
-- [CentOS 7](pem_agent_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pem_agent_sles_15)
 
-- [SLES 12](pem_agent_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pem_agent_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pem_agent_debian_12)
 
 - [Debian 11](pem_agent_debian_11)
-
-- [Debian 10](pem_agent_debian_10)
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx
deleted file mode 100644
index 0cc1e4b04c2..00000000000
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_centos_7.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing Postgres Enterprise Manager agent on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx
deleted file mode 100644
index dd9d5a7b1fa..00000000000
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_debian_10.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: Debian 10
-title: Installing Postgres Enterprise Manager agent on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx
deleted file mode 100644
index 5258040f79d..00000000000
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_rhel_7.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing Postgres Enterprise Manager agent on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx
deleted file mode 100644
index 3dfe4adae6c..00000000000
--- a/product_docs/docs/pem/9/installing_pem_agent/linux_x86_64/pem_agent_sles_12.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-navTitle: SLES 12
-title: Installing Postgres Enterprise Manager agent on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pem/9/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_sles12_x86
----
-
-!!! Note
-
-    Postgres Enterprise Manager 8.3 and later is supported on SLES.
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pem-agent
-```
-
-After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/).
diff --git a/product_docs/docs/pem/9/managing_database_server.mdx b/product_docs/docs/pem/9/managing_database_server.mdx
index 936915aad2a..1d7ecd19852 100644
--- a/product_docs/docs/pem/9/managing_database_server.mdx
+++ b/product_docs/docs/pem/9/managing_database_server.mdx
@@ -89,6 +89,6 @@ A service script for the database server allows the PEM server to start, stop, o
 The Postgres server on which the PEM server resides must contain a service script. Postgres installers in Windows generated by EDB create a service script for you. If you're using a Postgres server from another source like native packages, you must provide a service script.
 
 !!! Note
-    On CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x, the service script resides in `/usr/lib/systemd/system`.
+    On Rocky Linux or RHEL 8.x, the service script resides in `/usr/lib/systemd/system`.
 
 For information about customizing a Postgres service, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/static/server-start.html).
\ No newline at end of file
diff --git a/product_docs/docs/pem/9/managing_pem_server.mdx b/product_docs/docs/pem/9/managing_pem_server.mdx
index 175d9a9d273..a9439534e6b 100644
--- a/product_docs/docs/pem/9/managing_pem_server.mdx
+++ b/product_docs/docs/pem/9/managing_pem_server.mdx
@@ -49,7 +49,7 @@ Where `x` indicates the server version number.
 
 You can use the service script to control the service.
 
-To control a service on RHEL or CentOS version 7.x or 8.x, at the command prompt, assume superuser privileges and issue the command:
+To control a service on RHEL 8.x, at the command prompt, assume superuser privileges and issue the command:
 
     ```shell
     systemctl <service_name> <action>
@@ -98,7 +98,7 @@ If Linux responds with an answer like the following, httpd isn't running:
 user 13321 13267 0 07:37 pts/1 00:00:00 grep httpd
 ```
 
-To start the service on a CentOS or RHEL 7.x or 8.x system, use the command:
+To start the service on a RHEL 8.x system, use the command:
 
 ```shell
 systemctl start httpd
diff --git a/product_docs/docs/pem/9/profiling_workloads/installing_sql_profiler.mdx b/product_docs/docs/pem/9/profiling_workloads/installing_sql_profiler.mdx
index c1e14936234..ce6cd2672cc 100644
--- a/product_docs/docs/pem/9/profiling_workloads/installing_sql_profiler.mdx
+++ b/product_docs/docs/pem/9/profiling_workloads/installing_sql_profiler.mdx
@@ -54,7 +54,6 @@ Where:
   | Package manager |             Operating system     |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8 and derivatives           |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and derivatives           |
 
diff --git a/product_docs/docs/pem/9/troubleshooting.mdx b/product_docs/docs/pem/9/troubleshooting.mdx
index 4a9aedf9db7..269e6d58eee 100644
--- a/product_docs/docs/pem/9/troubleshooting.mdx
+++ b/product_docs/docs/pem/9/troubleshooting.mdx
@@ -74,16 +74,6 @@ PL/pgSQL function pem.clear_job_zombies(integer) line 8 at SQL statement
 
   Restart the backend database server.
 
-### RHEL 7 ppc64le
-
-After installing the PEM server on RHEL 7 ppc64le, you might see the following cipher error in the worker log file:
-
-```text
-WARNING: ConnectToPEM: unable to connect to PEM database: could not create SSL context: library has no ciphers
-```
-
-To resolve this error, if you intend to stay on PostgreSQL version 12, upgrade to the latest available version. Then, restart the PEM agent.
-
 ## Reconfiguring the PEM server
 
 In some situations, you might need to uninstall the PEM server, reinstall it, and then configure the server again. To do so:
diff --git a/product_docs/docs/pem/9/uninstalling/uninstalling_on_linux.mdx b/product_docs/docs/pem/9/uninstalling/uninstalling_on_linux.mdx
index 7de3987de0f..32930f465a8 100644
--- a/product_docs/docs/pem/9/uninstalling/uninstalling_on_linux.mdx
+++ b/product_docs/docs/pem/9/uninstalling/uninstalling_on_linux.mdx
@@ -16,28 +16,16 @@ If you uninstall the PEM server package from a host, the PEM Agent package insta
 !!! Note
     Before uninstalling the PEM Agent, you need to de-register the agent first. You can de-register the agent using the `pemworker` command-line utility. After that, you can proceed with the uninstallation steps.
 
-## Uninstalling PEM components from CentOS or RHEL or Rocky Linux or AlmaLinux hosts
+## Uninstalling PEM components from RHEL or Rocky Linux or AlmaLinux hosts
 
-You can use variations of the `rpm`, `yum remove`, or `yum erase` commands to remove the installed packages from CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory.
+You can use variations of the `rpm` command to remove the installed packages from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory.
 
--   Include the `-e` option when invoking the rpm command to remove an installed package; the command syntax is:
+Include the `-e` option when invoking the rpm command to remove an installed package; the command syntax is:
 
     ```shell
     rpm -e package_name
     ```
 
--   You can use the `yum remove` command to remove the PEM Server or Agent package installed by yum. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
-
-    ```shell
-    yum remove package_name
-    ```
-
--   You can use the `yum erase` command to remove the pem server or Agent package along with the `edb-pem` and `edb-pem-docs` dependencies. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
-
-    ```shell
-    yum erase package_name
-    ```
-
 Where `package_name` is the name of the package that you would like to remove.
 
 -   You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on Rocky Linux or AlmaLinux or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
diff --git a/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx b/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx
index 1124bc7d3b8..bd3fd6c45ec 100644
--- a/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx
+++ b/product_docs/docs/pem/9/upgrading/moving_pem_server.mdx
@@ -183,7 +183,7 @@ Before starting the server migration, make sure that the firewalls between the s
 
 7.  Stop the database server on the target host.
 
-    To stop the PEM server on CentOS or RHEL 7.x or 8.x, use the command:
+    To stop the PEM server on RHEL 8.x, use the command:
 
     ```shell
     systemctl stop <service_name>
diff --git a/product_docs/docs/pem/9/upgrading/upgrading_backend_database.mdx b/product_docs/docs/pem/9/upgrading/upgrading_backend_database.mdx
index 940e595890e..4c61cd817a4 100644
--- a/product_docs/docs/pem/9/upgrading/upgrading_backend_database.mdx
+++ b/product_docs/docs/pem/9/upgrading/upgrading_backend_database.mdx
@@ -235,7 +235,7 @@ You can find more information about using pg_upgrade at [pg_upgrade](http://www.
 
 3.  Stop the services of both the old backend database and the new backend database.
 
-    On RHEL or CentOS 7.x or 8.x, open a command line and assume the identity of a superuser. Enter the command:
+    On RHEL 8.x, open a command line and assume the identity of a superuser. Enter the command:
 
     ```shell
     systemctl <service_name> stop
@@ -416,7 +416,7 @@ You can find more information about using pg_upgrade at [pg_upgrade](http://www.
 
 8.  Restart the service of the new backend database.
 
-    On RHEL or CentOS 7.x or 8.x, at the command line as superuser enter:
+    On RHEL 8.x, at the command line as superuser enter:
 
     ```shell
     systemctl stop <service_name>
diff --git a/product_docs/docs/pem/9/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx b/product_docs/docs/pem/9/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
index 32a22e6d05d..c7de456748c 100644
--- a/product_docs/docs/pem/9/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
+++ b/product_docs/docs/pem/9/upgrading/upgrading_pem_installation/upgrading_pem_installation_linux_rpm.mdx
@@ -35,14 +35,10 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |        Operating system          |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
 
-!!! Note
-    If you're doing a fresh installation of the PEM server on CentOS or RHEL 7.x host, the installer installs the `edb-python3-mod_wsgi` package with the installation. The package is a requirement of the operating system. If you're upgrading the PEM server on CentOS or RHEL 7.x host, the `edb-python3-mod_wsgi` package replaces the `mod_wsgi package` package to meet the requirements of the operating system.
-
 After upgrading the PEM server, you must configure the PEM server. For detailed information, see [Configuring the PEM server](#configuring-the-pem-server).
 
 !!! Note
@@ -90,7 +86,6 @@ Where `<package-manager>` is the package manager used with your operating system
   | Package manager |        Operating system          |
   | --------------- | -------------------------------- |
   | dnf             | RHEL 8/9 and derivatives         |
-  | yum             | RHEL 7 and derivatives, CentOS 7 |
   | zypper          | SLES                             |
   | apt-get         | Debian and Ubuntu                |
 
diff --git a/product_docs/docs/pgbouncer/1/02_configuration_and_usage.mdx b/product_docs/docs/pgbouncer/1/02_configuration_and_usage.mdx
index b95b273dcdc..f02c135406a 100644
--- a/product_docs/docs/pgbouncer/1/02_configuration_and_usage.mdx
+++ b/product_docs/docs/pgbouncer/1/02_configuration_and_usage.mdx
@@ -15,7 +15,7 @@ Configure EDB PgBouncer before you use it.
 
 When the EDB PgBouncer service is running, any Postgres client connecting to the EDB PgBouncer listener port specified in the configuration file uses connection pooling. EDB PgBouncer connection and configuration information is stored in the `.ini` file.
 
-On RedHat/Centos, Debian, and SLES 12 SP5, the `.ini` file is located in the following directory:
+On RedHat, Debian, and SLES, the `.ini` file is located in the following directory:
 
 `/etc/edb/pgbouncer<x.x>/`
 
diff --git a/product_docs/docs/pgbouncer/1/installing/03_uninstallation.mdx b/product_docs/docs/pgbouncer/1/installing/03_uninstallation.mdx
index ca0dbabb9fc..bedd5d77888 100644
--- a/product_docs/docs/pgbouncer/1/installing/03_uninstallation.mdx
+++ b/product_docs/docs/pgbouncer/1/installing/03_uninstallation.mdx
@@ -11,15 +11,7 @@ You can uninstall EDB PgBouncer.
 
 ## Uninstalling EDB PgBouncer on a RHEL/Rocky Linux/AlmaLinux host
 
-To uninstall EDB PgBouncer on a CentOS host, assume the identity of the root user and invoke the command.
-
-On RHEL/CentOS 7:
-
-```shell
-yum -y erase edb-pgbouncer<xx>
-```
-
-On RHEL/Rocky Linux/AlmaLinux 8:
+To uninstall EDB PgBouncer, assume the identity of the root user and invoke the following command:
 
 ```shell
 dnf -y erase edb-pgbouncer<xx>
@@ -37,9 +29,9 @@ apt-get remove edb-pgbouncer<xx>
 
 Where `<xx>` is the version you want to uninstall.
 
-## Uninstalling EDB PgBouncer on an SLES 12 host
+## Uninstalling EDB PgBouncer on an SLES host
 
-To uninstall PgBouncer on an SLES 12 host, assume the identity of the root user and invoke:
+To uninstall PgBouncer on an SLES host, assume the identity of the root user and invoke:
 
 ```shell
 zypper remove edb-pgbouncer<xx>
diff --git a/product_docs/docs/pgbouncer/1/installing/index.mdx b/product_docs/docs/pgbouncer/1/installing/index.mdx
index 5a91db4e3c2..8d2a4fad1be 100644
--- a/product_docs/docs/pgbouncer/1/installing/index.mdx
+++ b/product_docs/docs/pgbouncer/1/installing/index.mdx
@@ -15,8 +15,8 @@ redirects:
   - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/09_pgbouncer_rhel8_ppcle/
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - windows
 ---
@@ -27,25 +27,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pgbouncer_rhel_9), [RHEL 8](linux_x86_64/pgbouncer_rhel_8), [RHEL 7](linux_x86_64/pgbouncer_rhel_7)
+- [RHEL 9](linux_x86_64/pgbouncer_rhel_9), [RHEL 8](linux_x86_64/pgbouncer_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pgbouncer_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgbouncer_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pgbouncer_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pgbouncer_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgbouncer_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pgbouncer_other_linux_9), [Rocky Linux 8](linux_x86_64/pgbouncer_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pgbouncer_other_linux_9), [AlmaLinux 8](linux_x86_64/pgbouncer_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pgbouncer_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pgbouncer_sles_15), [SLES 12](linux_x86_64/pgbouncer_sles_12)
+- [SLES 15](linux_x86_64/pgbouncer_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pgbouncer_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pgbouncer_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pgbouncer_debian_12), [Debian 11](linux_x86_64/pgbouncer_debian_11), [Debian 10](linux_x86_64/pgbouncer_debian_10)
+- [Debian 12](linux_x86_64/pgbouncer_debian_12), [Debian 11](linux_x86_64/pgbouncer_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -55,7 +53,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pgbouncer_sles_15), [SLES 12](linux_ppc64le/pgbouncer_sles_12)
+- [SLES 15](linux_ppc64le/pgbouncer_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx
index db8e2247429..c0526fa58eb 100644
--- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/index.mdx
@@ -15,7 +15,6 @@ navigation:
   - pgbouncer_rhel_9
   - pgbouncer_rhel_8
   - pgbouncer_sles_15
-  - pgbouncer_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -29,5 +28,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgbouncer_sles_15)
-
-- [SLES 12](pgbouncer_sles_12)
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx
deleted file mode 100644
index af2481c478c..00000000000
--- a/product_docs/docs/pgbouncer/1/installing/linux_ppc64le/pgbouncer_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB pgBouncer on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgbouncer/1/01_installation/install_on_linux/ibm_power_ppc64le/pgbouncer_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pgbouncer<xx>
-```
-
-Where `<xx>` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`.
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx
index 9fd7d706780..7632d1eae4c 100644
--- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/index.mdx
@@ -14,17 +14,13 @@ redirects:
 navigation:
   - pgbouncer_rhel_9
   - pgbouncer_rhel_8
-  - pgbouncer_rhel_7
   - pgbouncer_other_linux_9
   - pgbouncer_other_linux_8
-  - pgbouncer_centos_7
   - pgbouncer_sles_15
-  - pgbouncer_sles_12
   - pgbouncer_ubuntu_22
   - pgbouncer_ubuntu_20
   - pgbouncer_debian_12
   - pgbouncer_debian_11
-  - pgbouncer_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -35,14 +31,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pgbouncer_rhel_8)
 
-- [RHEL 7](pgbouncer_rhel_7)
-
 - [Oracle Linux (OL) 9](pgbouncer_rhel_9)
 
 - [Oracle Linux (OL) 8](pgbouncer_rhel_8)
 
-- [Oracle Linux (OL) 7](pgbouncer_rhel_7)
-
 - [Rocky Linux 9](pgbouncer_other_linux_9)
 
 - [Rocky Linux 8](pgbouncer_other_linux_8)
@@ -51,14 +43,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pgbouncer_other_linux_8)
 
-- [CentOS 7](pgbouncer_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgbouncer_sles_15)
 
-- [SLES 12](pgbouncer_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pgbouncer_ubuntu_22)
@@ -68,5 +56,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pgbouncer_debian_12)
 
 - [Debian 11](pgbouncer_debian_11)
-
-- [Debian 10](pgbouncer_debian_10)
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx
deleted file mode 100644
index e1503a41982..00000000000
--- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_centos_7.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB pgBouncer on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pgbouncer<xx>
-```
-
-Where `<xx>` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`.
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx
deleted file mode 100644
index a86a0eb0aa0..00000000000
--- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_debian_10.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB pgBouncer on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-pgbouncer<xx>
-```
-
-Where `<xx>` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`.
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx
deleted file mode 100644
index 9b3fe7c0190..00000000000
--- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_rhel_7.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB pgBouncer on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pgbouncer<xx>
-```
-
-Where `<xx>` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`.
diff --git a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx b/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx
deleted file mode 100644
index b4fcec4af05..00000000000
--- a/product_docs/docs/pgbouncer/1/installing/linux_x86_64/pgbouncer_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB pgBouncer on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgbouncer/1/01_installation/install_on_linux/x86_amd64/pgbouncer_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pgbouncer<xx>
-```
-
-Where `<xx>` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`.
diff --git a/product_docs/docs/pgbouncer/1/upgrading.mdx b/product_docs/docs/pgbouncer/1/upgrading.mdx
index fa817fc4249..db09839c66b 100644
--- a/product_docs/docs/pgbouncer/1/upgrading.mdx
+++ b/product_docs/docs/pgbouncer/1/upgrading.mdx
@@ -34,7 +34,6 @@ To upgrade to a new minor release:
      | Package manager	| Operating system |
      | ---------------- | ---------------- |
      | dnf | RHEL 8 or later and derivatives | 
-     | yum | RHEL 7 and derivatives, CentOS 7 |
      | zypper | SLES |
      | apt-get | Debian and derivatives |
 
diff --git a/product_docs/docs/pge/15/installing/index.mdx b/product_docs/docs/pge/15/installing/index.mdx
index 5e1c9dcd999..dff461c6f16 100644
--- a/product_docs/docs/pge/15/installing/index.mdx
+++ b/product_docs/docs/pge/15/installing/index.mdx
@@ -12,18 +12,16 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8), [RHEL 7](linux_x86_64/pge_rhel_7)
+- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pge_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pge_other_linux_9), [Rocky Linux 8](linux_x86_64/pge_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pge_other_linux_9), [AlmaLinux 8](linux_x86_64/pge_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pge_centos_7)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20)
 
-- [Debian 11](linux_x86_64/pge_debian_11), [Debian 10](linux_x86_64/pge_debian_10)
+- [Debian 11](linux_x86_64/pge_debian_11)
diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx
index 3046d4f58c4..eb619be5849 100644
--- a/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pge/15/installing/linux_x86_64/index.mdx
@@ -5,14 +5,11 @@ navTitle: "On Linux x86"
 navigation:
   - pge_rhel_9
   - pge_rhel_8
-  - pge_rhel_7
   - pge_other_linux_9
   - pge_other_linux_8
-  - pge_centos_7
   - pge_ubuntu_22
   - pge_ubuntu_20
   - pge_debian_11
-  - pge_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -23,14 +20,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pge_rhel_8)
 
-- [RHEL 7](pge_rhel_7)
-
 - [Oracle Linux (OL) 9](pge_rhel_9)
 
 - [Oracle Linux (OL) 8](pge_rhel_8)
 
-- [Oracle Linux (OL) 7](pge_rhel_7)
-
 - [Rocky Linux 9](pge_other_linux_9)
 
 - [Rocky Linux 8](pge_other_linux_8)
@@ -39,8 +32,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pge_other_linux_8)
 
-- [CentOS 7](pge_centos_7)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pge_ubuntu_22)
@@ -48,5 +39,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Ubuntu 20.04](pge_ubuntu_20)
 
 - [Debian 11](pge_debian_11)
-
-- [Debian 10](pge_debian_10)
diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx
deleted file mode 100644
index ecde380f1eb..00000000000
--- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_centos_7.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Extended Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-postgresextended15-server edb-postgresextended15-contrib
-```
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-15-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge15/bin/edb-pge-15-setup initdb
-
-sudo systemctl start edb-pge-15
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx
deleted file mode 100644
index bb67caba19b..00000000000
--- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_debian_10.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Extended Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-postgresextended-15
-```
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-15-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/15/bin/edb-pge-15-setup initdb
-
-sudo systemctl start edb-pge-15
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx b/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx
deleted file mode 100644
index 834574e8529..00000000000
--- a/product_docs/docs/pge/15/installing/linux_x86_64/pge_rhel_7.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Extended Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-postgresextended15-server edb-postgresextended15-contrib
-```
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-15-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge15/bin/edb-pge-15-setup initdb
-
-sudo systemctl start edb-pge-15
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pge/16/installing/index.mdx b/product_docs/docs/pge/16/installing/index.mdx
index c0199097297..87c0027a579 100644
--- a/product_docs/docs/pge/16/installing/index.mdx
+++ b/product_docs/docs/pge/16/installing/index.mdx
@@ -13,21 +13,19 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8), [RHEL 7](linux_x86_64/pge_rhel_7)
+- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pge_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pge_other_linux_9), [Rocky Linux 8](linux_x86_64/pge_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pge_other_linux_9), [AlmaLinux 8](linux_x86_64/pge_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pge_centos_7)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pge_debian_12), [Debian 11](linux_x86_64/pge_debian_11), [Debian 10](linux_x86_64/pge_debian_10)
+- [Debian 12](linux_x86_64/pge_debian_12), [Debian 11](linux_x86_64/pge_debian_11)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pge/16/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/16/installing/linux_x86_64/index.mdx
index ae742a510e4..0ec9f379e21 100644
--- a/product_docs/docs/pge/16/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pge/16/installing/linux_x86_64/index.mdx
@@ -5,15 +5,12 @@ navTitle: "On Linux x86"
 navigation:
   - pge_rhel_9
   - pge_rhel_8
-  - pge_rhel_7
   - pge_other_linux_9
   - pge_other_linux_8
-  - pge_centos_7
   - pge_ubuntu_22
   - pge_ubuntu_20
   - pge_debian_12
   - pge_debian_11
-  - pge_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -24,14 +21,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pge_rhel_8)
 
-- [RHEL 7](pge_rhel_7)
-
 - [Oracle Linux (OL) 9](pge_rhel_9)
 
 - [Oracle Linux (OL) 8](pge_rhel_8)
 
-- [Oracle Linux (OL) 7](pge_rhel_7)
-
 - [Rocky Linux 9](pge_other_linux_9)
 
 - [Rocky Linux 8](pge_other_linux_8)
@@ -40,8 +33,6 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pge_other_linux_8)
 
-- [CentOS 7](pge_centos_7)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pge_ubuntu_22)
@@ -51,5 +42,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pge_debian_12)
 
 - [Debian 11](pge_debian_11)
-
-- [Debian 10](pge_debian_10)
diff --git a/product_docs/docs/pge/16/installing/linux_x86_64/pge_centos_7.mdx b/product_docs/docs/pge/16/installing/linux_x86_64/pge_centos_7.mdx
deleted file mode 100644
index 8d2f3140cfb..00000000000
--- a/product_docs/docs/pge/16/installing/linux_x86_64/pge_centos_7.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Postgres Extended Server on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-postgresextended16-server edb-postgresextended16-contrib
-```
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb
-
-sudo systemctl start edb-pge-16
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pge/16/installing/linux_x86_64/pge_debian_10.mdx b/product_docs/docs/pge/16/installing/linux_x86_64/pge_debian_10.mdx
deleted file mode 100644
index a569043a544..00000000000
--- a/product_docs/docs/pge/16/installing/linux_x86_64/pge_debian_10.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Postgres Extended Server on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-postgresextended-16
-```
-
-## Initial configuration
-
-This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb
-
-sudo systemctl start edb-pge-16
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pge/16/installing/linux_x86_64/pge_rhel_7.mdx b/product_docs/docs/pge/16/installing/linux_x86_64/pge_rhel_7.mdx
deleted file mode 100644
index 5060174c43f..00000000000
--- a/product_docs/docs/pge/16/installing/linux_x86_64/pge_rhel_7.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Postgres Extended Server on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-postgresextended16-server edb-postgresextended16-contrib
-```
-
-## Initial configuration
-
-Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.
-
-First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster.
-
-```shell
-sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb
-
-sudo systemctl start edb-pge-16
-```
-
-To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.
-
-```shell
-sudo -iu postgres
-
-psql postgres
-```
-
-The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file.
-
-Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file).
-
-```sql
-ALTER ROLE postgres with PASSWORD 'password';
-```
-
-## Experiment
-
-Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.
-
-First, use psql to create a database named `hr` to hold human resource information.
-
-```sql
-# running in psql
-CREATE DATABASE hr;
-__OUTPUT__
-CREATE DATABASE
-```
-
-Connect to the `hr` database inside psql:
-
-```
-\c hr
-__OUTPUT__
-You are now connected to database "hr" as user "postgres".
-```
-
-Create columns to hold department numbers, unique department names, and locations:
-
-```
-CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
-PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
-varchar(13));
-__OUTPUT__
-CREATE TABLE
-```
-
-Insert values into the `dept` table:
-
-```
-INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
-__OUTPUT__
-INSERT 0 1
-```
-
-```
-INSERT into dept VALUES (20,'RESEARCH','DALLAS');
-__OUTPUT__
-INSERT 0 1
-```
-
-View the table data by selecting the values from the table:
-
-```
-SELECT * FROM dept;
-__OUTPUT__
-deptno  |   dname    |   loc
---------+------------+----------
-10      | ACCOUNTING | NEW YORK
-20      | RESEARCH   | DALLAS
-(2 rows)
-```
diff --git a/product_docs/docs/pgpool/4/03_configuring_connection_pooling.mdx b/product_docs/docs/pgpool/4/03_configuring_connection_pooling.mdx
index 697faee4a8e..6358f82963c 100644
--- a/product_docs/docs/pgpool/4/03_configuring_connection_pooling.mdx
+++ b/product_docs/docs/pgpool/4/03_configuring_connection_pooling.mdx
@@ -176,13 +176,13 @@ Modify the `postgresql.conf` file (located in `/var/lib/edb/as14/data`), adding
 
 Save the configuration file, and restart the server:
 
- To restart on RHEL/CentOS 7 and RHEL/Rocky Linux/AlmaLinux 8 platforms:
+ To restart on RHEL/Rocky Linux/AlmaLinux 8 platforms:
 
  ```shell
  systemctl restart edb-as-14
  ```
 
- To restart on Debian 10.x or Ubuntu 18.04 | 20.04 platforms:
+ To restart on Debian 20.04 platform:
 
  ```shell
  /usr/edb/as14/bin/epas_ctlcluster 14 main restart
diff --git a/product_docs/docs/pgpool/4/installing/index.mdx b/product_docs/docs/pgpool/4/installing/index.mdx
index 20975beda94..527aa99a1a1 100644
--- a/product_docs/docs/pgpool/4/installing/index.mdx
+++ b/product_docs/docs/pgpool/4/installing/index.mdx
@@ -18,8 +18,8 @@ legacyRedirectsGenerated:
     guring_the_pgpool-II.html"
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - upgrading
   - uninstalling
@@ -31,25 +31,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pgpool_rhel_9), [RHEL 8](linux_x86_64/pgpool_rhel_8), [RHEL 7](linux_x86_64/pgpool_rhel_7)
+- [RHEL 9](linux_x86_64/pgpool_rhel_9), [RHEL 8](linux_x86_64/pgpool_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pgpool_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgpool_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pgpool_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pgpool_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgpool_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pgpool_other_linux_9), [Rocky Linux 8](linux_x86_64/pgpool_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pgpool_other_linux_9), [AlmaLinux 8](linux_x86_64/pgpool_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pgpool_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pgpool_sles_15), [SLES 12](linux_x86_64/pgpool_sles_12)
+- [SLES 15](linux_x86_64/pgpool_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pgpool_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pgpool_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pgpool_debian_12), [Debian 11](linux_x86_64/pgpool_debian_11), [Debian 10](linux_x86_64/pgpool_debian_10)
+- [Debian 12](linux_x86_64/pgpool_debian_12), [Debian 11](linux_x86_64/pgpool_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -59,7 +57,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pgpool_sles_15), [SLES 12](linux_ppc64le/pgpool_sles_12)
+- [SLES 15](linux_ppc64le/pgpool_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx
index 864faa4347b..e12699567b0 100644
--- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pgpool/4/installing/linux_ppc64le/index.mdx
@@ -14,7 +14,6 @@ navigation:
   - pgpool_rhel_9
   - pgpool_rhel_8
   - pgpool_sles_15
-  - pgpool_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -28,5 +27,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgpool_sles_15)
-
-- [SLES 12](pgpool_sles_12)
diff --git a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx b/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx
deleted file mode 100644
index fcf195ae82e..00000000000
--- a/product_docs/docs/pgpool/4/installing/linux_ppc64le/pgpool_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Pgpool-II on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/01_installing_and_configuring_the_pgpool-II/ibm_power_ppc64le/pgpool_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pgpool<xx>
-```
-
-Where `<xx>` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`.
diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx
index 8f7d84d6b93..2bdd95c2789 100644
--- a/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/pgpool/4/installing/linux_x86_64/index.mdx
@@ -17,17 +17,13 @@ legacyRedirectsGenerated:
 navigation:
   - pgpool_rhel_9
   - pgpool_rhel_8
-  - pgpool_rhel_7
   - pgpool_other_linux_9
   - pgpool_other_linux_8
-  - pgpool_centos_7
   - pgpool_sles_15
-  - pgpool_sles_12
   - pgpool_ubuntu_22
   - pgpool_ubuntu_20
   - pgpool_debian_12
   - pgpool_debian_11
-  - pgpool_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -38,14 +34,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pgpool_rhel_8)
 
-- [RHEL 7](pgpool_rhel_7)
-
 - [Oracle Linux (OL) 9](pgpool_rhel_9)
 
 - [Oracle Linux (OL) 8](pgpool_rhel_8)
 
-- [Oracle Linux (OL) 7](pgpool_rhel_7)
-
 - [Rocky Linux 9](pgpool_other_linux_9)
 
 - [Rocky Linux 8](pgpool_other_linux_8)
@@ -54,14 +46,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pgpool_other_linux_8)
 
-- [CentOS 7](pgpool_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgpool_sles_15)
 
-- [SLES 12](pgpool_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pgpool_ubuntu_22)
@@ -71,5 +59,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pgpool_debian_12)
 
 - [Debian 11](pgpool_debian_11)
-
-- [Debian 10](pgpool_debian_10)
diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx
deleted file mode 100644
index 41c332538d3..00000000000
--- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_centos_7.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Pgpool-II on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pgpool<xx>
-```
-
-Where `<xx>` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`.
diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx
deleted file mode 100644
index 0a92aa450e9..00000000000
--- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_debian_10.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Pgpool-II on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-pgpool<xx>
-```
-
-Where `<xx>` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`.
diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx
deleted file mode 100644
index 37415238d28..00000000000
--- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_rhel_7.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Pgpool-II on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-pgpool<xx>
-```
-
-Where `<xx>` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`.
diff --git a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx b/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx
deleted file mode 100644
index b73d47dae4a..00000000000
--- a/product_docs/docs/pgpool/4/installing/linux_x86_64/pgpool_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Pgpool-II on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/01_installing_and_configuring_the_pgpool-II/x86_amd64/pgpool_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-pgpool<xx>
-```
-
-Where `<xx>` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`.
diff --git a/product_docs/docs/pgpool/4/installing/uninstalling.mdx b/product_docs/docs/pgpool/4/installing/uninstalling.mdx
index 6b5e6421d1c..fb6718ce0a6 100644
--- a/product_docs/docs/pgpool/4/installing/uninstalling.mdx
+++ b/product_docs/docs/pgpool/4/installing/uninstalling.mdx
@@ -12,15 +12,7 @@ For information about uninstallling extensions, see [Uninstalling EDB Pgpool-II
 
 ## Uninstalling EDB Pgpool-II on an RHEL//Rocky Linux/AlmaLinux host
 
-To uninstall EDB Pgpool-II, assume the identity of the root user and invoke the appropriate command.
-
-On RHEL/CentOS 7:
-
-```shell
-yum erase edb-pgpool<xx>
-```
-
-On RHEL/Rocky Linux/AlmaLinux 8:
+To uninstall EDB Pgpool-II, assume the identity of the root user and invoke the following command:
 
 ```shell
 dnf erase edb-pgpool<xx>
@@ -38,7 +30,7 @@ apt-get remove -y edb-pgpool<xx>
 
 Where `<xx>` is the EDB Pgpool-II version you want to uninstall.
 
-## Uninstalling EDB Pgpool-II on a SLES 12 host
+## Uninstalling EDB Pgpool-II on a SLES host
 
 To uninstall EDB Pgpool-II on a SLES host, assume the identity of the root user and invoke:
 
diff --git a/product_docs/docs/pgpool/4/installing/upgrading.mdx b/product_docs/docs/pgpool/4/installing/upgrading.mdx
index 976f1c454ab..eddfee41188 100644
--- a/product_docs/docs/pgpool/4/installing/upgrading.mdx
+++ b/product_docs/docs/pgpool/4/installing/upgrading.mdx
@@ -30,7 +30,6 @@ Where:
    | Package manager |         Operating system         |
    | --------------- | -------------------------------- |
    | dnf             | RHEL 8/9 and derivatives         |
-   | yum             | RHEL 7 and derivatives, CentOS 7 |
    | zypper          | SLES                             |
    | apt-get         | Debian and Ubuntu                |
  
diff --git a/product_docs/docs/pgpool/4/installing_extensions/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/index.mdx
index 61bb018e831..52a68de8565 100644
--- a/product_docs/docs/pgpool/4/installing_extensions/index.mdx
+++ b/product_docs/docs/pgpool/4/installing_extensions/index.mdx
@@ -14,8 +14,8 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/pgpool-ii/user-guides/pgpool-ii-guide/1.0/extensions.html"
 
 navigation:
-  - linux_x86_64
   - linux_ppc64le
+  - linux_x86_64
   - linux_arm64
   - creating_pgpool_extensions
   - upgrading_extensions
@@ -28,25 +28,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/pgpoolext_rhel_9), [RHEL 8](linux_x86_64/pgpoolext_rhel_8), [RHEL 7](linux_x86_64/pgpoolext_rhel_7)
+- [RHEL 9](linux_x86_64/pgpoolext_rhel_9), [RHEL 8](linux_x86_64/pgpoolext_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/pgpoolext_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgpoolext_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/pgpoolext_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/pgpoolext_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pgpoolext_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/pgpoolext_other_linux_9), [Rocky Linux 8](linux_x86_64/pgpoolext_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/pgpoolext_other_linux_9), [AlmaLinux 8](linux_x86_64/pgpoolext_other_linux_8)
 
-- [CentOS 7](linux_x86_64/pgpoolext_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/pgpoolext_sles_15), [SLES 12](linux_x86_64/pgpoolext_sles_12)
+- [SLES 15](linux_x86_64/pgpoolext_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/pgpoolext_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pgpoolext_ubuntu_20)
 
-- [Debian 12](linux_x86_64/pgpoolext_debian_12), [Debian 11](linux_x86_64/pgpoolext_debian_11), [Debian 10](linux_x86_64/pgpoolext_debian_10)
+- [Debian 12](linux_x86_64/pgpoolext_debian_12), [Debian 11](linux_x86_64/pgpoolext_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -56,7 +54,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/pgpoolext_sles_15), [SLES 12](linux_ppc64le/pgpoolext_sles_12)
+- [SLES 15](linux_ppc64le/pgpoolext_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx
index b4083bf8847..682734c7023 100644
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx
+++ b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - pgpoolext_rhel_9
   - pgpoolext_rhel_8
   - pgpoolext_sles_15
-  - pgpoolext_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgpoolext_sles_15)
-
-- [SLES 12](pgpoolext_sles_12)
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx
deleted file mode 100644
index f87d8f121ad..00000000000
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_ppc64le/pgpoolext_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Pgpool-II Extensions on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/02_extensions/ibm_power_ppc64le/pgpoolext_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-pgpool<yy>-extensions
-```
-
-Where `<xx>` is the EDB Postgres Advanced Server version and `<yy>` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`.
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx
index 1b7bba6f48c..dfef9b5f8e6 100644
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx
+++ b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/index.mdx
@@ -16,17 +16,13 @@ legacyRedirectsGenerated:
 navigation:
   - pgpoolext_rhel_9
   - pgpoolext_rhel_8
-  - pgpoolext_rhel_7
   - pgpoolext_other_linux_9
   - pgpoolext_other_linux_8
-  - pgpoolext_centos_7
   - pgpoolext_sles_15
-  - pgpoolext_sles_12
   - pgpoolext_ubuntu_22
   - pgpoolext_ubuntu_20
   - pgpoolext_debian_12
   - pgpoolext_debian_11
-  - pgpoolext_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -37,14 +33,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](pgpoolext_rhel_8)
 
-- [RHEL 7](pgpoolext_rhel_7)
-
 - [Oracle Linux (OL) 9](pgpoolext_rhel_9)
 
 - [Oracle Linux (OL) 8](pgpoolext_rhel_8)
 
-- [Oracle Linux (OL) 7](pgpoolext_rhel_7)
-
 - [Rocky Linux 9](pgpoolext_other_linux_9)
 
 - [Rocky Linux 8](pgpoolext_other_linux_8)
@@ -53,14 +45,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](pgpoolext_other_linux_8)
 
-- [CentOS 7](pgpoolext_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](pgpoolext_sles_15)
 
-- [SLES 12](pgpoolext_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](pgpoolext_ubuntu_22)
@@ -70,5 +58,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](pgpoolext_debian_12)
 
 - [Debian 11](pgpoolext_debian_11)
-
-- [Debian 10](pgpoolext_debian_10)
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx
deleted file mode 100644
index 7b346a93f1a..00000000000
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_centos_7.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing EDB Pgpool-II Extensions on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/02_extensions/x86_amd64/pgpoolext_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-pgpool<yy>-extensions
-```
-
-Where `<xx>` is the EDB Postgres Advanced Server version and `<yy>` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`.
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx
deleted file mode 100644
index ae7b4190d07..00000000000
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_debian_10.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-navTitle: Debian 10
-title: Installing EDB Pgpool-II Extensions on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/02_extensions/x86_amd64/pgpoolext_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-sudo apt-get -y install edb-as<xx>-pgpool<yy>-extensions
-```
-
-Where `<xx>` is the EDB Postgres Advanced Server version and `<yy>` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`.
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx
deleted file mode 100644
index ffcc4d5a99c..00000000000
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_rhel_7.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing EDB Pgpool-II Extensions on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/02_extensions/x86_amd64/pgpoolext_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-sudo yum -y install edb-as<xx>-pgpool<yy>-extensions
-```
-
-Where `<xx>` is the EDB Postgres Advanced Server version and `<yy>` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`.
diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx
deleted file mode 100644
index 1f2d95c7843..00000000000
--- a/product_docs/docs/pgpool/4/installing_extensions/linux_x86_64/pgpoolext_sles_12.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-navTitle: SLES 12
-title: Installing EDB Pgpool-II Extensions on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /pgpool/4/02_extensions/x86_amd64/pgpoolext_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-sudo zypper -n install edb-as<xx>-pgpool<yy>-extensions
-```
-
-Where `<xx>` is the EDB Postgres Advanced Server version and `<yy>` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`.
diff --git a/product_docs/docs/pgpool/4/installing_extensions/uninstalling_extensions.mdx b/product_docs/docs/pgpool/4/installing_extensions/uninstalling_extensions.mdx
index 56d133bbfa6..647ceae0b5e 100644
--- a/product_docs/docs/pgpool/4/installing_extensions/uninstalling_extensions.mdx
+++ b/product_docs/docs/pgpool/4/installing_extensions/uninstalling_extensions.mdx
@@ -7,17 +7,9 @@ legacyRedirectsGenerated:
 ---
 
 
-## Uninstalling EDB Pgpool-II extensions on an RHEL/CentOS/Rocky Linux/AlmaLinux host
+## Uninstalling EDB Pgpool-II extensions on an RHEL/Rocky Linux/AlmaLinux host
 
-To remove extensions from the server, execute the appropriate command.
-
-On RHEL/CentOS 7:
-
-```shell
-yum erase edb-as<xx>-pgpool<yy>-extensions
-```
-
-On RHEL/Rocky Linux/AlmaLinux 8:
+To remove extensions from the server, execute the following command:
 
 ```shell
 dnf erase edb-as<xx>-pgpool<yy>-extensions
@@ -25,7 +17,7 @@ dnf erase edb-as<xx>-pgpool<yy>-extensions
 
 Where `<xx>` is the EDB Postgres Advanced Server version, and `<yy>` is the EDB Pgpool-II extension version.
 
-## Uninstalling EDB Pgpool-II extensions on a SLES 12 host
+## Uninstalling EDB Pgpool-II extensions on a SLES host
 
 To uninstall EDB Pgpool-II extensions on a SLES host, assume the identity of the root user and invoke:
 
diff --git a/product_docs/docs/pgpool/4/installing_extensions/upgrading_extensions.mdx b/product_docs/docs/pgpool/4/installing_extensions/upgrading_extensions.mdx
index 19314344950..1269125245d 100644
--- a/product_docs/docs/pgpool/4/installing_extensions/upgrading_extensions.mdx
+++ b/product_docs/docs/pgpool/4/installing_extensions/upgrading_extensions.mdx
@@ -28,7 +28,6 @@ Where:
    | Package manager |         Operating system         |
    | --------------- | -------------------------------- |
    | dnf             | RHEL 8/9 and derivatives         |
-   | yum             | RHEL 7 and derivatives, CentOS 7 |
    | zypper          | SLES                             |
    | apt-get         | Debian and Ubuntu                | 
 
diff --git a/product_docs/docs/postgis/3/installing/index.mdx b/product_docs/docs/postgis/3/installing/index.mdx
index 145c9c50903..e1c63fe9183 100644
--- a/product_docs/docs/postgis/3/installing/index.mdx
+++ b/product_docs/docs/postgis/3/installing/index.mdx
@@ -27,25 +27,23 @@ Select a link to access the applicable installation instructions:
 
 ### Red Hat Enterprise Linux (RHEL) and derivatives
 
-- [RHEL 9](linux_x86_64/postgis_rhel_9), [RHEL 8](linux_x86_64/postgis_rhel_8), [RHEL 7](linux_x86_64/postgis_rhel_7)
+- [RHEL 9](linux_x86_64/postgis_rhel_9), [RHEL 8](linux_x86_64/postgis_rhel_8)
 
-- [Oracle Linux (OL) 9](linux_x86_64/postgis_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/postgis_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/postgis_rhel_7)
+- [Oracle Linux (OL) 9](linux_x86_64/postgis_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/postgis_rhel_8)
 
 - [Rocky Linux 9](linux_x86_64/postgis_other_linux_9), [Rocky Linux 8](linux_x86_64/postgis_other_linux_8)
 
 - [AlmaLinux 9](linux_x86_64/postgis_other_linux_9), [AlmaLinux 8](linux_x86_64/postgis_other_linux_8)
 
-- [CentOS 7](linux_x86_64/postgis_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_x86_64/postgis_sles_15), [SLES 12](linux_x86_64/postgis_sles_12)
+- [SLES 15](linux_x86_64/postgis_sles_15)
 
 ### Debian and derivatives
 
 - [Ubuntu 22.04](linux_x86_64/postgis_ubuntu_22), [Ubuntu 20.04](linux_x86_64/postgis_ubuntu_20)
 
-- [Debian 12](linux_x86_64/postgis_debian_12), [Debian 11](linux_x86_64/postgis_debian_11), [Debian 10](linux_x86_64/postgis_debian_10)
+- [Debian 12](linux_x86_64/postgis_debian_12), [Debian 11](linux_x86_64/postgis_debian_11)
 
 ## Linux [IBM Power (ppc64le)](linux_ppc64le)
 
@@ -55,7 +53,7 @@ Select a link to access the applicable installation instructions:
 
 ### SUSE Linux Enterprise (SLES)
 
-- [SLES 15](linux_ppc64le/postgis_sles_15), [SLES 12](linux_ppc64le/postgis_sles_12)
+- [SLES 15](linux_ppc64le/postgis_sles_15)
 
 ## Linux [AArch64 (ARM64)](linux_arm64)
 
diff --git a/product_docs/docs/postgis/3/installing/linux_ppc64le/index.mdx b/product_docs/docs/postgis/3/installing/linux_ppc64le/index.mdx
index b3b33500ce8..4d205bf3a31 100644
--- a/product_docs/docs/postgis/3/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/postgis/3/installing/linux_ppc64le/index.mdx
@@ -13,7 +13,6 @@ navigation:
   - postgis_rhel_9
   - postgis_rhel_8
   - postgis_sles_15
-  - postgis_sles_12
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -27,5 +26,3 @@ Operating system-specific install instructions are described in the correspondin
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](postgis_sles_15)
-
-- [SLES 12](postgis_sles_12)
diff --git a/product_docs/docs/postgis/3/installing/linux_ppc64le/postgis_sles_12.mdx b/product_docs/docs/postgis/3/installing/linux_ppc64le/postgis_sles_12.mdx
deleted file mode 100644
index 5838140353f..00000000000
--- a/product_docs/docs/postgis/3/installing/linux_ppc64le/postgis_sles_12.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-navTitle: SLES 12
-title: Installing PostGIS on SLES 12 ppc64le
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /postgis/latest/01a_installing_postgis/installing_on_linux/ibm_power_ppc64le/postgis_sles12_ppcle
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/ppc64le
-  sudo SUSEConnect -p sle-sdk/12.5/ppc64le
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-# To install PostGIS 3.4:
-zypper -n install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-zypper -n install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 12:
-zypper -n install edb-as12-postgis
-```
-
-Where `<xx>` is the version of EDB Postgres Advanced Server. Replace `<xx>` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`.
diff --git a/product_docs/docs/postgis/3/installing/linux_x86_64/index.mdx b/product_docs/docs/postgis/3/installing/linux_x86_64/index.mdx
index 69b22078d89..a7640d3c2b3 100644
--- a/product_docs/docs/postgis/3/installing/linux_x86_64/index.mdx
+++ b/product_docs/docs/postgis/3/installing/linux_x86_64/index.mdx
@@ -12,17 +12,13 @@ redirects:
 navigation:
   - postgis_rhel_9
   - postgis_rhel_8
-  - postgis_rhel_7
   - postgis_other_linux_9
   - postgis_other_linux_8
-  - postgis_centos_7
   - postgis_sles_15
-  - postgis_sles_12
   - postgis_ubuntu_22
   - postgis_ubuntu_20
   - postgis_debian_12
   - postgis_debian_11
-  - postgis_debian_10
 ---
 
 Operating system-specific install instructions are described in the corresponding documentation:
@@ -33,14 +29,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [RHEL 8](postgis_rhel_8)
 
-- [RHEL 7](postgis_rhel_7)
-
 - [Oracle Linux (OL) 9](postgis_rhel_9)
 
 - [Oracle Linux (OL) 8](postgis_rhel_8)
 
-- [Oracle Linux (OL) 7](postgis_rhel_7)
-
 - [Rocky Linux 9](postgis_other_linux_9)
 
 - [Rocky Linux 8](postgis_other_linux_8)
@@ -49,14 +41,10 @@ Operating system-specific install instructions are described in the correspondin
 
 - [AlmaLinux 8](postgis_other_linux_8)
 
-- [CentOS 7](postgis_centos_7)
-
 ### SUSE Linux Enterprise (SLES)
 
 - [SLES 15](postgis_sles_15)
 
-- [SLES 12](postgis_sles_12)
-
 ### Debian and derivatives
 
 - [Ubuntu 22.04](postgis_ubuntu_22)
@@ -66,5 +54,3 @@ Operating system-specific install instructions are described in the correspondin
 - [Debian 12](postgis_debian_12)
 
 - [Debian 11](postgis_debian_11)
-
-- [Debian 10](postgis_debian_10)
diff --git a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_centos_7.mdx b/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_centos_7.mdx
deleted file mode 100644
index 41a5473ba93..00000000000
--- a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_centos_7.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-navTitle: CentOS 7
-title: Installing PostGIS on CentOS 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /postgis/latest/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_centos7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-## Install the package
-
-```shell
-# To install PostGIS 3.4:
-sudo yum -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo yum -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 10-12:
-sudo yum -y install edb-as<xx>-postgis
-```
-
-Where `<xx>` is the version of EDB Postgres Advanced Server. Replace `<xx>` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`.
diff --git a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_debian_10.mdx b/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_debian_10.mdx
deleted file mode 100644
index 26032725bb3..00000000000
--- a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_debian_10.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-navTitle: Debian 10
-title: Installing PostGIS on Debian 10 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /postgis/latest/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_deb10_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `apt-cache search enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-## Install the package
-
-```shell
-
-# To install PostGIS 3.4 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo apt-get -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 12:
-sudo apt-get -y install edb-as12-postgis-3.1
-```
-
-Where `<xx>` is the version of EDB Postgres Advanced Server. Replace `<xx>` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`.
diff --git a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_rhel_7.mdx b/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_rhel_7.mdx
deleted file mode 100644
index 1fe455ae7c0..00000000000
--- a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_rhel_7.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-navTitle: RHEL 7 or OL 7
-title: Installing PostGIS on RHEL 7 or OL 7 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /postgis/latest/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_rhel7_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `dnf repolist | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Install the EPEL repository:
-
-  ```shell
-  sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-  ```
-
-- Enable additional repositories to resolve dependencies:
-  ```shell
-  subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel-*-server-rpms"
-  ```
-
-## Install the package
-
-```shell
-# To install PostGIS 3.4:
-sudo yum -y install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo yum -y install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 10-11:
-sudo yum -y install edb-as<xx>-postgis
-```
-
-Where `<xx>` is the version of EDB Postgres Advanced Server. Replace `<xx>` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`.
diff --git a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_sles_12.mdx b/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_sles_12.mdx
deleted file mode 100644
index 2ce94a7c6df..00000000000
--- a/product_docs/docs/postgis/3/installing/linux_x86_64/postgis_sles_12.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-navTitle: SLES 12
-title: Installing PostGIS on SLES 12 x86_64
-# This topic is generated from templates. If you have feedback on it, instead of
-# editing the page and creating a pull request, please enter a GitHub issue and
-# the documentation team will update the templates accordingly.
-
-redirects:
-  - /postgis/latest/01a_installing_postgis/installing_on_linux/x86_amd64/postgis_sles12_x86
----
-
-## Prerequisites
-
-Before you begin the installation process:
-
-- Install Postgres on the same host. See:
-
-  - [Installing EDB Postgres Advanced Server](/epas/latest/installing/)
-
-  - [Installing PostgreSQL](https://www.postgresql.org/download/)
-
-- Set up the EDB repository.
-
-  Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step.
-
-  To determine if your repository exists, enter this command:
-
-  `zypper lr -E | grep enterprisedb`
-
-  If no output is generated, the repository isn't installed.
-
-  To set up the EDB repository:
-
-  1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads).
-
-  1. Select the button that provides access to the EDB repository.
-  1. Select the platform and software that you want to download.
-
-  1. Follow the instructions for setting up the EDB repository.
-
-- Activate the required SUSE module:
-  ```shell
-  sudo SUSEConnect -p PackageHub/12.5/x86_64
-  sudo SUSEConnect -p sle-sdk/12.5/x86_64
-
-  ```
-- Refresh the metadata:
-  ```shell
-  sudo zypper refresh
-  ```
-
-## Install the package
-
-```shell
-# To install PostGIS 3.4:
-sudo zypper -n install edb-as<xx>-postgis34
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15:
-sudo zypper -n install edb-as<xx>-postgis3
-
-# To install PostGIS 3.1 using EDB Postgres Advanced Server 12:
-sudo zypper -n install edb-as12-postgis
-```
-
-Where `<xx>` is the version of EDB Postgres Advanced Server. Replace `<xx>` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`.
diff --git a/product_docs/docs/postgis/3/installing/upgrading.mdx b/product_docs/docs/postgis/3/installing/upgrading.mdx
index 558756020ba..e0d5897b54e 100644
--- a/product_docs/docs/postgis/3/installing/upgrading.mdx
+++ b/product_docs/docs/postgis/3/installing/upgrading.mdx
@@ -42,7 +42,7 @@ To avoid accidental upgrades, PostGIS versions 3.1 and 3.2 use different package
 
    For more information, see [Uninstalling PostGIS](/postgis/latest/installing/uninstalling/).
 
-1. Install PostGIS version 3.2. For instructions, see [Installing PostGIS on RHEL 7/OL 7 x86](/postgis/latest/installing/linux_x86_64/postgis_rhel_7/).
+1. Install PostGIS version 3.2. For instructions, see [Installing PostGIS](/postgis/latest/installing/).
 
 1. Upgrade the PostGIS extensions: