Supported Cloud Platforms

Supported Cloud Platforms

• Amazon Web Services
• AWS Outposts
• Microsoft Azure
  • Azure Shared Disk
• Google Cloud
• Oracle Cloud Infrastructure
• Virtustream – Dell Technologies

Please see each section for environment-specific restrictions and notations.

Amazon Web Services (AWS)

!On SLES v12 or later running on AWS, the dynamic change of the virtual IP address by the cloud network plug-in may affect the operation of the LifeKeeper cluster. For detailed information, see LifeKeeper Core – Known Issues / Restrictions.

AWS Outposts

AWS services generally offered as cloud services are referred to as Region, and AWS Outposts are referred to as Outposts.
Additionally, clients on Outposts or in a region under the same account are referred to as internal clients, and clients on-premise or on a different account are referred to as external clients.

Available configurations

With the exception of some ARKs, features available on Regions can also be used on Outposts by meeting the equivalent requirements.
The ARKs that have Outposts-specific restrictions are as follows:

• Recovery Kit for EC2 (RK for EC2)
• Recovery Kit for Route53 (RK for Route53)
• LB Health Check Kit (LBHC Kit)

When connecting from an external client, the use of these ARKs is restricted by the Outposts routing mode.

For availability reasons, it is recommended that each LifeKeeper cluster node be located on a different Outposts server.

Configuration notes for using the Recovery Kit for Route53 in CoIP mode

To communicate with the LifeKeeper cluster from external clients in CoIP mode, use RK for Route53.
Please make the OS recognize CoIP in order for RK for Route53 to rewrite the IP address corresponding to the A record of the Route53 Hosted Zone.
CoIP is not recognized by the OS even if it is assigned to an EC2 instance or ENI on the AWS console. Therefore, a private IP address equivalent to CoIP must be statically assigned on the OS. However, if a static IP address is assigned on the OS that is not assigned in the AWS console, it may cause problems with other communications using the corresponding NIC. Therefore, you should either assign a dedicated ENI that is not used for actual communications or create a dummy NIC, and then statically assign the CoIP to the NIC.

Microsoft Azure

!On SLES v12 or later running on Azure, the dynamic change of the virtual IP address by the cloud network plug-in may affect the operation of the LifeKeeper cluster. For detailed information, see LifeKeeper Core – Known Issues / Restrictions.

Oracle Cloud Infrastructure

Refer to Known Issues/Restrictions when using LifeKeeper on Oracle Cloud Infrastructure for the supported configuration and the restrictions.