Chapter 1. Introducing RHEL on public cloud platforms
Public cloud platforms provide computing resources as a service. Instead of maintaining on-premise hardware, you can run IT workloads as public cloud instances. This includes Red Hat Enterprise Linux (RHEL) systems.
1.1. Benefits of using RHEL in a public cloud Copy linkLink copied to clipboard!
Running Red Hat Enterprise Linux (RHEL) on public cloud platforms provides flexible resource allocation, cost efficiency, and software-controlled configurations to optimize your infrastructure without managing physical hardware.
RHEL as a cloud instance located on a public cloud platform has the following benefits over RHEL on-premise physical systems or virtual machines (VMs):
- Flexible and fine-grained allocation of resources
A RHEL instance runs as a VM on a cloud platform. The cloud platform is a cluster of remote servers maintained by the cloud service provider. Therefore, on the software level, allocating hardware resources to the instance is easily customizable, such as a specific type of CPU or storage.
In contrast to local RHEL systems, your resource options are not restricted by the limitations of physical hardware. Instead, you can select from a wide range of features and configurations that the cloud provider makes available.
- Space and cost efficiency
You do not need to own any on-premise servers to host cloud workloads. This avoids the space, power, and maintenance requirements associated with physical hardware.
Instead, you pay the cloud provider directly for using a cloud instance. The cost is based on allocation of hardware and usage time. Therefore, you can optimize your costs based on the requirements.
- Software-controlled configurations
You can save the entire configuration of a cloud instance as data. Also, you can control it with software through the cloud platform. Therefore, create, remove, clone, or migrate the instance. You also operate a cloud instance remotely in a cloud provider console, and it connects to remote storage by default.
In addition, you can back up the current state of a cloud instance as a snapshot at any time. Afterwards, you can load the snapshot to restore the instance to the saved state.
- Separation from the host and software compatibility
Similarly to a local VM, the RHEL guest operating system on a cloud instance runs on a Kernel-based Virtual Machine (KVM). KVM is a loadable kernel module that transforms the local RHEL kernel into a
TYPE-1 hypervisor. KVM is separate from the host operating system. It is also separate from the client system, which you can connect to the instance.Therefore, you can install any operating system on the cloud instance. This means that on a RHEL public cloud instance, you can run RHEL-specific applications that might not be usable on your local operating system. In addition, even if the operating system of the instance becomes unstable or compromised, it does not affect your client system.
1.2. Public cloud use cases for RHEL Copy linkLink copied to clipboard!
Deploying applications on a public cloud depends on the use case. Consider the advantages for your Red Hat Enterprise Linux (RHEL) deployments when evaluating if it is beneficial to migrate your deployments to the public cloud.
- Beneficial use cases
Public cloud instances effectively scale your computing power on and off based on-demand. This is known as scaling up and scaling down. You can use RHEL on public cloud in the following scenarios:
- Clusters with peak workloads and low general performance requirements benefit from flexible scaling. Scaling up and down based on your demands can be highly efficient in terms of resource costs.
- Quickly setting up or expanding your clusters. This avoids high upfront costs of setting up local servers.
- Changes in your local environment do not affect cloud instances. Therefore, you can use them for backup and disaster recovery.
- Potentially problematic use cases
- You are running an existing environment that you cannot adjust. Customizing a cloud instance to fit existing deployment needs might not be economically efficient. Your current host platform might be more cost-effective.
- You are operating with a hard limit on your budget. Local data centers typically provide less flexibility than public clouds. However, they offer more control over maximum resource costs.
1.3. Frequent concerns when migrating to a public cloud Copy linkLink copied to clipboard!
Moving your RHEL workloads from a local environment to a public cloud platform might raise concerns about the changes involved. The following are the most commonly asked questions:
- Will my RHEL work differently as a cloud instance than as a local virtual machine?
In most respects, RHEL instances on a public cloud platform work the same as RHEL virtual machines on a local host, such as an on-premise server. Notable exceptions include:
- Instead of private orchestration interfaces, public cloud instances use provider-specific console interfaces for managing your cloud resources.
- Certain features, such as nested virtualization, might not work correctly. If a specific feature is critical for your deployment, check the feature’s compatibility in advance with your chosen public cloud provider.
- Will my data stay safe in a public cloud as opposed to a local server?
The data in your RHEL cloud instances remains in your ownership. Your public cloud provider does not have access to it. Major cloud providers support data encryption in transit. This improves data security when migrating your virtual machines to the public cloud. Security of RHEL public cloud instances can be summarized as follows:
- Your public cloud provider is responsible for the security of the cloud hypervisor
- Red Hat provides the security features of the RHEL guest operating systems in your instances
- You manage the specific security settings and practices in your cloud infrastructure
- What effect does my geographic region have on the functionality of RHEL public cloud instances?
- You can use RHEL instances on a public cloud platform regardless of your geographical location. Therefore, you can run your instances in the same region as your on-premise server. However, hosting your instances in a physically distant region might lead to high latency and reduced performance. In addition, depending on the public cloud provider, certain regions might offer additional features or be more cost-efficient. Before creating your RHEL instances, review the properties of the hosting regions available for your chosen cloud provider.
1.4. Obtaining RHEL for public cloud deployments Copy linkLink copied to clipboard!
To deploy Red Hat Enterprise Linux (RHEL) in a public cloud environment, you must select a certified cloud service provider (CCSP) and create a RHEL cloud instance.
Based on your requirements and the current offerings in the market, select the optimal CCSP for your use case to run RHEL instances are Amazon Web Services (AWS), Google Cloud, and Microsoft Azure.
NoteThis document specifically addresses the process of deploying RHEL on Azure.
- Create a RHEL cloud instance on your cloud platform.
- Use Red Hat Update Infrastructure (RHUI) to keep your RHEL deployment up-to-date.
1.5. Methods for creating RHEL cloud instances Copy linkLink copied to clipboard!
You can create a Red Hat Enterprise Linux (RHEL) system image and import it to the cloud platform.
To build the system image, you can use either RHEL image builder or purchase the image from the cloud service provider marketplace. You can then deploy the RHEL image as a cloud instance.
To deploy a RHEL instance on a public cloud platform, you can use either of the following methods:
- Create a RHEL system image and import it to the cloud platform
- To create the system image, you can use the RHEL image builder or build the image manually.
- "This method uses your existing RHEL subscription (bring your own subscription (BYOS).
- You pre-pay a yearly subscription, and you can use your Red Hat customer discount.
- Red Hat provides customer service.
-
For creating many images effectively, you can use the
cloud-initutility.
- Purchase a RHEL instance directly from the cloud provider marketplace
- You post-pay an hourly rate for using the service. This method is also referred to as pay as you go (PAYG).
- The cloud service provider provides customer service.