1

Ensure that the virtual machines that you plan to use to deploy Avaya Aura® Device Services comply with the requirements for software-only installation.

Avaya Aura® Device Services supports the c4.2xlarge AWS instance type. For more information, see Resources profile specifications for Avaya Aura Device Services on Amazon Web Services.

2

Download the Avaya Aura® Device Services software-only installation package from PLDS.

The software-only installation package includes the following files:

• Software-only system layer installer.

• Avaya Aura® Device Services application installer.

The package file name has the aads-swonly-AADS_VERSION.tgz format.

For more information about the software downloading process, see Downloading software from PLDS.

3

Prepare your AWS instance for software-only installation.

See Prerequisites for software-only deployment on AWS.

4

Create security groups on AWS.

See Creating security groups.

5

Install RHEL 8.4 or RHEL 8.10 on AWS.

Avaya Aura® Device Services Release 10.2.x requires RHEL 8.4 or RHEL 8.10. For more information about installation, see Installing RHEL 8.4 or RHEL 8.10 on AWS.

6

Configure security groups for the eth1 secondary network interface.

See Configuring security groups for the secondary eth1 interface.

7

Enable root access to RHEL.

RHEL deployed on AWS does not have the root user enabled by default. For more information, see Enabling root access.

8

Create disk partitioning on RHEL.

Avaya Aura® Device Services requires specific disk partitioning to organize data storage. For more information about creating disk partitioning, see Creating disk partitioning for software-only deployments on AWS and Disk partitions for software-only deployments.

9

Create a non-root Linux user.

The installation and administration of the Avaya Aura® Device Services server is more secure when performed by non-root users with sudo privileges. For more information, see Creating an administrative user.

10

Enable the YUM package manager on RHEL.

The YUM package manager is used to install the required packages. For more information about enabling YUM, see the Red Hat YUM documentation.

11

Install additional packages required by Avaya Aura® Device Services.

By default, RHEL 8.4 or RHEL 8.10 does not contain certain packages that Avaya Aura® Device Services requires. You must install these packages manually. For more information, see Additional packages required by Avaya Aura Device Services and Installing additional RHEL 8.4 or RHEL 8.10 packages manually.

12

Enable the Haveged service.

See Enabling the Haveged service.

13

Enable FIPS mode (optional).

For software-only deployments, you can only enable FIPS mode before installing the system layer. For more information about enabling FIPS, see Enabling FIPS for software-only systems.

14

For more information, see RHEL packages management and Enabling required RHEL repositories.

Registering your RHEL instance to the Red Hat subscription is the preferred option.

15

Prepare you RHEL system for installing the software-only system layer.

See Prerequisites for installing the system layer on AWS.

16

Install the software-only system layer on your RHEL.

The system layer is low-level software that forms the required operational environment for Avaya Aura® Device Services.

For more information, see Installing the system layer.

17

In cluster deployments, create target groups for the load balancer.

See Creating target groups.

18

In cluster deployments, configure Elastic load balancers.

See Creating and configuring Elastic load balancers.

19

Ensure that:

• The chronyd service is up and running.

• System Manager and Session Manager are reachable from your virtual machine. This is only required if you deploy Avaya Aura® Device Services in Avaya Aura® environment.

Perform these checks to ensure that the system layer is installed successfully so you can install the Avaya Aura® Device Services application.

For more information, see Checking the Chrony service status and Checking the connection to System Manager and Session Manager.