+++ This bug was initially created as a clone of Bug #2076401 +++

Description of problem:

Red Hat ships an outdated version of the AWS CLI via the awscli package. It's major version 1. Meanwhile, Amazon provides an up-to-date version (currently on major version 2) via the AWS web site.

• Installing or updating the latest version of the AWS CLI (https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html#cliv2-linux-install)

It would be convenient to direct customers to these installation instructions, rather than maintaining our own awscli package. This would ensure that our customers have access to the latest fixes and improvements with minimal effort on our part. It would allow us to work more smoothly with AWS support when issues arise. For example, AWS support may ask that a customer experiencing connection issues try with an up-to-date CLI version (as they have in fact requested on at least one occasion). Currently, this is not possible without installing directly from Amazon.

Alternatively, we could regularly build, test, and release updated awscli packages. The obvious advantage is that changes to the CLI would go through our QA process. The disadvantages as mentioned above are additional dev/QE/release work, delayed updates relative to Amazon, and potentially less smooth collaboration with AWS support.

Until 14 Apr 2022, our HA installation on AWS article directed users to install the awscli package. On 14 Apr, this was updated to point to Amazon's procedure. We should test this more thoroughly.

• Installing and Configuring a Red Hat Enterprise Linux 7.4 (and later) High-Availability Cluster on Amazon Web Services (https://access.redhat.com/articles/3354781)

If z-streams are required, then we need to hit at least 7.6, 7.7, and 7.9 for SAP support.