Creating RHEL instance on Amazon Web Services

Last Updated : Sep 24, 2026 |
Prolog information
Metadata
Keywords:
Use this procedure to create RHEL virtual machine on Amazon Web Services.
Note:
Avaya recommends installing only required RPMs to the system for security and stability. Do not install complete Red Hat system.
In a software-only installation, the customer installs the Red Hat provided RPM updates. To avoid possible issues or incompatibilities with new RPMs, check the list of tested RPMs and follow the instructions in the PSN020617u that Avaya publishes periodically on the Avaya Support website.
Also, note that the steps provided in this section are for reference purpose only. For the most up-to-date information, see the Amazon Web Services documentation.
  1. Sign in to the Amazon Web Services Management console.
  2. Under AWS services, navigate to All servicesComputeEC2.
    STEP RESULT:
    The system displays the EC2 Management Console page.
  3. Click Launch an Instance.
  4. Under Name and tags, for Name, enter a descriptive name for your instance.
    ADDITIONAL INFORMATION:
    Note:
    Remember the name entered for the tag. The name entered for the tag is used to identify the RHEL instance after the instance is created.
  5. Under Application and OS Images (Amazon Machine Image), search for the supported RHEL version in Community AMIs, and click Select.
    ADDITIONAL INFORMATION:
    For the supported RHEL version, see Third party software requirements section.
  6. Under Instance type, select the instance type according to your required footprints.
    ADDITIONAL INFORMATION:
    For more information, see Supported footprints of Communication Manager ISO on Amazon Web Services.
    Note:
    Do the following configuration on Amazon Web Services platform only.
    • For Simplex Communication Manager, do the following:
      1. In the Network field, click a VPC network.
      2. In the Subnet field, select the appropriate subnet.
      3. In the Network Interfaces section, assign an IP address.
        This IP address must be in the subnet.
    • For Duplex Communication Manager, do the following:
      1. In the Network field, click a VPC network.
      2. In the Subnet field, select the appropriate subnet.
      3. Select the Add instance to placement group check box.
        Note:
        If you have an existing placement group, select Add to existing placement group option and select the placement group which you already created.
        To add a new placement group, do the following:
        1. Select Add to a new placement group option.
        2. In the Name field, enter the name of the placement group.
        3. Under Placement Strategy, choose the Spread option.
        4. Click Create group button.
        Note:
        Duplex deployment of Communication Manager for shared placement group is available for both ISO and OVA deployment types.
        If there is an existing system with a dedicated host and you want to have a shared placement group instance, follow the given steps to retain all the existing users and configurations:
        • Create a backup of the existing Communication Manager. For more information on creating a backup, see Creating a backup in Upgrading Avaya Aura® Communication Manager.
        • Delete all the existing duplex Communication Manager instances from your system.
        • Deploy Communication Manager and create a new Communication Manager instance in the Shared Placement group with the same IP. For more information about shared placement, please refer to chapter 5 Deploying in this guide.
        • Restore the full backup created of the existing Communication Manager. For more information on restoring a backup, see Restoring backup in Upgrading Avaya Aura® Communication Manager.
        • Generate a CSR certificate signed with CA and install it in the Communication Manager. For more information on generating a CSR, see Generating a CSR in Administering Avaya Aura® Communication Manager.
      4. In the IAM role field, add role with policy AmazonEC2FullAccess.
        Note:
        Communication Manager only uses the capabilities of AssignPrivateIpAddress and UnassignPrivateIpAddress for the EC2 instances. The customer may want to create a more restrictive IAM policy than what is provided by the EC2FullAccess policy for these EC2 instances.
      5. In the Network Interfaces section, for DuplexCM1, do the following:
        1. In the Primary IP field of eth0, assign an IP address in the subnet.
        2. In the Secondary IP addresses field of eth0, assign an IP address in the subnet.
          Note:
          The secondary IP address is the alias/floating IP address that moves from one server to another during the interchange.
        3. Add an additional network interface eth1, and assign an IP address in a different network than the Secondary IP address.
      6. In the Network Interfaces section, for DuplexCM2, do the following:
        1. In the Primary IP field of eth0, assign an IP address in the subnet.
        2. Add an additional network interface eth1, and assign an IP address in a different network than the Secondary IP address.
  7. Under Key pair (login), select an existing key pair or create a new key pair dialog box using the following options:
    • Choose an existing key pair.
    • Create a new key pair.
  8. If you select the Choose an existing key pair option, from the Select a key pair drop-down list, and select a key pair.
  9. If you select the Create a new key pair option, perform the following:
    1. In the Key pair name field, type a name for the private key file. The extension of the private key file is .pem.
    2. Click Create key pair. The key pair will automatically download to the system after clicking on Create key pair.
    3. Save the file in a secure and accessible location.
      ADDITIONAL INFORMATION:
      Note:
      You will not be able to download the file again.
  10. Under Network settings, choose Edit. For Security group name, select Create security group for creating a new security group or Select existing security group to select an existing security group.
    ADDITIONAL INFORMATION:
    If you select an existing security group, from Common security groups dropdown, choose your security group from the list of existing security groups.
  11. Click Configure storage.
    ADDITIONAL INFORMATION:
    Ensure that the hard disk size must be minimum 64 GiB. For more information, see Disk partitioning.
    The partitions size can be larger than the value specified.
  12. Review the details of each configuration in the Summary panel.
  13. Click Launch Instances.
    STEP RESULT:
    The system creates the RHEL instance.
  14. Click on the hyperlink of the instance ID to view the details of your instance.
    ADDITIONAL INFORMATION:
    When the system creates an instance, the Status Checks column displays the message: 2/2 checks passed.