Support Policies for RHEL High Availability Clusters - Amazon Web Services (AWS) EC2 Instances as Cluster Members
Contents
Overview
Applicable Environments
- Red Hat Enterprise Linux (RHEL) with the High Availability Add-On
- Using Amazon EC2 to provide instances that may serve as High Availability cluster members
Recommended Prior Reading
Useful References and Guides
Introduction
This guide offers Red Hat's policies, requirements, and limitations applicable to the use of Amazon Web Services (EC2) instances as members of a RHEL High Availability cluster. Users of RHEL High Availability software components should adhere to these policies by installing only on the approved platforms in order to be eligible to receive assistance from Red Hat Support with the appropriate support subscriptions.
Policies
Consider general conditions for support of RHEL High Availability in virtualization environments
Supported releases for Amazon AWS EC2 instances as High Availability members: Red Hat supports RHEL High Availability cluster members running on Amazon Web Services (AWS) EC2 instances with the following RHEL releases or later:
- RHEL 7.4.z - Supported with packages
resource-agents-3.9.5-105.el7_4.13
,fence-agents-4.0.11-66.el7_4.6
and the most up to date 7.4.z corosync and pacemaker packages - RHEL 7.5 or later - Supported with packages
pacemaker-1.1.18-11.el7
,corosync-2.4.3-2.el7
,fence-agents-*-4.0.11-86.el7
or later.
Amazon AWS EC2 instances cluster members have to be all in the same region: Red Hat does not support having cluster members in different AWS regions, all cluster members have to be in the same AWS region. We do support having cluster members running in different availability zones within the same region.
Supported transport protocols: RHEL 7 High Availability clusters with members that run on the Amazon EC2 platform can only use the udpu
transport protocol - which is the default in RHEL 7 clusters. Azure VNETs do not support multicast traffic, preventing the usage of the udp
transport protocol.
Red Hat only supports the knet
transport in RHEL 8, regardless of platform.
For more information, see:
- Support policies - Transport protocols
- Explore features - Overview of transport protocols
- Design guidance - Selecting the transport protocol
Shared storage: RHEL High Availability clusters support shared storage with LVM (including tagging, clvmd, etc) on the following versions of RHEL below.
- RHEL 8.3 or later
- RHEL 7.9
For more information, see:
- Support Policies for RHEL Resilient Storage Clusters - Resilient Storage on Amazon Web Services (AWS) EC2 Instances
- aws.amazon.com - Amazon VPC FAQs
- Explore features - Overview of transport protocols
- Design guidance - Selecting the transport protocol
- Support Policies for RHEL Resilient Storage Clusters - Resilient Storage on Amazon Web Services (AWS) EC2 Instances
- Installing and Configuring a Red Hat Enterprise Linux 7.4 (and later) High-Availability Cluster on Amazon Web Services
Support for pacemaker
managing Amazon Elastic File System (EFS). Support for managing Amazon Elastic File System (EFS) with pacemaker
was added with the following releases below. For more information see: pacemaker cluster resources are unable to mount EFS with EFS Mount helper.
- RHEL 8.9 or later: Currently not supported. We are tracking this issue with the bug: 2049319.
- RHEL 9.3 or later:
resource-agents-4.10.0-44.el9_3
No support for AWS GovCloud VMs as RHEL High Availability cluster members: Red Hat does not support RHEL High Availability deployments consisting of members that are virtual machines running on the AWS GovCloud platform.
Support for AWS Outposts VMs as RHEL High Availability cluster members: Red Hat only supports RHEL High Availability deployments consisting of members that are virtual machines running on the AWS Outposts on-premises cloud platform on the following releases below:
- RHEL 8.4 or later.
- RHEL 9.4 or later.
Comments