IONOS as a leading public cloud service provider recognizes the crucial role of adaptability and security in today's ever-evolving market. Red Hat Enterprise Linux (RHEL) stands out for its robust security features and unwavering reliability, making it ideal for hybrid and multi-cloud environments. With RHEL, seamless workload migration, simplified management, and enhanced visibility pave the way for smooth transitions from development to production across public, private, and hybrid cloud landscapes. This combination of flexibility and reliability empowers our customers to uphold existing skills, standards, and best practices while efficiently deploying applications for your customers both in the cloud and on-premises.

The existing pricing model for RHEL in public cloud settings was initially established in 2011. Since then, cloud adoption has accelerated, and the pricing structure, based on the size of the cloud instance, has remained unchanged. To accommodate the evolution of cloud services and their varying instance sizes, Red Hat has embarked on a modernization journey, transitioning from the dated two-tiered pricing system ("small" and "large") to a more flexible and modular approach.

In response to the expanding array of flexible instance sizes offered by cloud providers, the new RHEL pricing model now scales based on vCPU or Core count, aligning with the prevalent pricing model for cloud Virtual Machines (VMs) and software. This strategic shift aims to better address the diverse requirements of partners and customers operating in the public cloud arena. At the core of this transformation is a commitment to enhancing the user experience and optimizing pricing structures in line with industry trends and customer needs.

This documentation guides you through the changes and ensures a seamless transition. Subsequent topics will delve deeper into the specifics of the subscription model alterations.

What are the details of the subscription model change?

The previous pricing structure featured a two-tiered system that categorized VMs as either "small" or "large" based on the number of cores, or vCPUs, with fixed prices assigned to each category regardless of the VM's actual size. The duration of VM allocation determined subscription fees, as the number of cores or vCPUs did not influence the pricing, resulting in a capped cost for RHEL subscriptions.

In the new subscription model, while retaining a similar approach, VM size becomes a key factor in determining subscription costs, making the pricing model more modular. Unlike before, the cost of a subscription will no longer be capped. The revamped model introduces a three-tier pricing system that classifies VMs as "small," "medium," or "large," based on the number of cores, or vCPUs. Each category is associated with a price per vCPU or core rather than per VM. This results in a calculation that multiplies the price by the size category and the number of vCPUs or cores, and the duration of VM allocation.

How are the new RHEL subscription fees calculated?

As previously mentioned, Red Hat has introduced a pricing mechanism that adjusts according to the number of vCPUs or cores allocated to a VM. Consequently, the subscription price now directly correlates with the resources utilized. The new three-tier pricing model offers discounts per vCPU or cores for larger instances.

The updated pricing structure brings about two notable outcomes. In particular, subscription fees for smaller instances can decrease as charges are based on consumed resources rather than a fixed rate. On the contrary, pricing now scales without any limitations, potentially leading to significant costs, especially for larger instances.

For detailed insights and cost estimations, the table below represents various configuration examples and cost calculations in Euro (€). Calculations are done on a monthly basis (30 days = 720 hours). Please ensure to confirm pricing details specific to your currency by referencing the updated price list corresponding to your regional IONOS entity.

Which services are affected by the RHEL subscription model change?

IONOS offers RHEL versions 8 and 9 as public images across all locations, with the new subscription structure applying to both versions.

These public images are compatible with IONOS Compute Engine featuring dedicated cores and vCPUs, as well as IONOS Cubes with exposed vCPUs. The updated subscription model is standardized across all types of compute resources, whether dedicated cores or vCPUs, aligning with the pricing outlined in the current price lists.

Additionally, IONOS maintains a Red Hat Update Infrastructure (RHUI) to facilitate update and patch requests for RHEL workloads deployed within the IONOS Public Cloud. The use of the IONOS RHUI service for update management remains complimentary and will continue to be offered without any additional charges.

When does the new RHEL subscription model become effective?

Red Hat has provided a transition window for partners to adjust to the new subscription model. IONOS has opted to implement the transition to the updated subscription model by August 1, 2024. Until July 31, 2024, the existing subscription model and prices will continue to apply to all provisioned workloads.

Which steps do you need to take to address your RHEL workloads?

No action is needed on your part concerning your RHEL workloads. The transition to the new RHEL subscription model is a commercial adjustment, handled seamlessly by IONOS through our billing services.

Your RHEL workloads will operate without disruption. There is no requirement for you or IONOS to make any modifications to your VM settings or infrastructure setup in response to the subscription model change. No alterations to deployment scripts or automation processes are necessary. You can continue to utilize IONOS services for deploying and managing your workloads as usual.

What are the options to manage RHEL subscription costs?

With the removal of cost caps in the new subscription model, factoring in the actual VM size becomes crucial, recommending a deeper dive into infrastructure planning to explore avenues for enhanced cost efficiency.

With the evolving subscription structure where costs may vary based on VM size, we recommend an evaluation of your VM sizing strategy to drive optimal cost-effectiveness. Highlighted by the illustrative calculations in the above table, smaller instances stand to gain advantages from this updated model, offering fairness by accommodating individual sizing requirements and favoring compact deployments.

One strategy to optimize expenses involves distributing workloads across multiple smaller VMs rather than consolidating them into a few large deployments.

While this approach suits many scenarios, it may not align with all workloads. Consider evaluating if instance performance optimization is feasible. For instance, transitioning from a Compute Engine based on vCPUs to one based on Dedicated Cores can offer dedicated power to workloads, potentially leading to reduced number of dedicated cores requirements and subsequently lowering subscription costs.

IONOS provides a variety of operating system block storage images and different versions of it that are ready to be used on any block storage type.

All images get updated frequently to include the latest updates, patches, and security fixes. IONOS will not inform about image updates separately. Once a new patch or update is provided, a new image is built and provided while the previous version is removed from the software catalog. The currently available version number is displayed in the image name that you can retrieve from the image selection within the block storage selection.

For more information about using public images for your Block Storage, see .

Available operating system images

The following list provides an overview of the operating systems and their corresponding distributions supplied by IONOS.

Open Source Linux

• Alma Linux

• CentOS Linux (deprecation announced for June, 30th 2024)

• Debian Linux

• Rocky Linux

• Ubuntu Linux

Enterprise Linux

• Red Hat Enterprise Linux. For more information, see .

Microsoft Server

• Microsoft Windows Server

IONOS is a certified partner of Red Hat and is entitled to offer and operate Red Hat Enterprise Linux (RHEL) within the IONOS public cloud.

Compatible versions

Currently, the entitlement is valid for RHEL 8 and RHEL 9 public images that IONOS provides.

Red Hat subscription

Currently, IONOS does not provide any Bring-Your-Own-Subscription (BYOS) option for subscription-based operating systems like Red Hat Enterprise Linux. You still need an IONOS subscription if you want to use your images. IONOS will charge you each time a boots from the private RHEL image. For more information about the charges, see .

Please ensure not to subscribe to or unsubscribe from sources of third-party subscription services to avoid duplicate charges for your Red Hat deployment. The subscription fee also includes access to the IONOS Red Hat Update Infrastructure (RHUI) instance.

IONOS Red Hat Update Infrastructure (RHUI)

IONOS operates its own instance of a Red Hat Update Infrastructure (RHUI). It is accessible by all public IONOS IP addresses. IONOS public RHEL images are preconfigured to access the IONOS RHUI setup as long as the VM has access to the internet.

With the entitlement, RHUI enables IONOS to provide the following services to end-users with an RHEL deployment:

• Mirror repositories hosted by Red Hat.

• Provide repositories with custom content supplied by IONOS.

• Publish content to VMs running RHEL workloads.

Select an RHEL image

Access internet

• that is connected to a public LAN. The network interface has a public IP address. If you have a firewall configured, you may need to allow access to the subscription endpoint and service port.

• that is connected to a private LAN containing other VMs that could act as a proxy to the public internet. Connectivity must be configured manually via the routing settings within the VM.

Access information for the IONOS RHUI service

IONOS offers a wide range of readily available public images that you can use instantly. In addition, you can also use your private images by uploading them into the IONOS Cloud infrastructure via the . Your IONOS account supports numerous block storage and ISO image types using an emulated CD-ROM drive, from which you can install an operating system or software directly.

Furthermore, you can create snapshots of provisioned block storage. Each snapshot is a separate instance, representing the state of the source block storage device while capturing the snapshot.

For Linux images, IONOS supports Cloud-Init to automate software package installations and instance configurations.

Recommended How-Tos

Get started with images and snapshots via the DCD.

Overview

are images generated from any block storage that have already been provisioned. You can use snapshots on any block storage type, regardless of the storage type from which the snapshot was created.

You can also use snapshots for other storages. This feature is useful, for example, if you want to quickly roll out multiple with the same or similar configuration or when you need a recovery point.

You can create snapshots from provisioned and storages, regardless of the underlying storage type (HDD or SSD). After creation, a snapshot utilizes the complete HDD storage space assigned to your IONOS account. Therefore, ensure that you have enough HDD quotas available before you create a snapshot.

A snapshot covers the entire capacity of the block storage device. It will also contain the volume part with no data written to it. For example, if you have a block storage with a volume of 100GiB containing 10GiB of data written to it and the remaining volume is empty, the snapshot will still be for the entire 100GiB volume. Consequently, a new block storage volume must at least be the same size as the snapshot. If the new block storage volume is large, you may need to extend the partition manually after booting the s and mounting the respective volume to the VM.

Snapshots are not incremental. Each snapshot is a separate instance representing the state of the source block storage device during the snapshot creation.

Snapshots can be shared with groups so that the users in that specific group can receive access to the snapshot. However, snapshots are limited to use only at the data center location where they were originally created. They can be utilized in several as long as they operate at the exact data center location as the snapshot creation.

Snapshots have no usage quota and can be used as often as you want. Furthermore, snapshots do not have a retention period; hence, they are not deleted automatically.

Prerequisite

Only contract administrators, owners, and users with the Create Snapshot permission can create a snapshot. Ensure that you have the necessary permission and sufficient memory available.

Snapshot authentication

You can create snapshots from provisioned block storage volumes only. It includes the authentication you specified during the creation of the snapshot. IONOS does not modify snapshots at any time. If you want to change the authentication configurations, we recommend doing it before reusing the snapshot on a new block storage device.

Create a Snapshot

You can create snapshots from any provisioned block storage, regardless of the underlying storage type. After creation, a snapshot utilizes the complete HDD storage space assigned to your IONOS account. Therefore, ensure that you have enough HDD quotas available before you create a snapshot.

The VM can be switched on or off when creating a snapshot. If you want to ensure that data that is still in the RAM of the VM is included in the snapshot, it is recommended that you synchronize the data (with sync under Linux) or shut down the guest operating system (with shutdown -h now under Linux) before creating the snapshot.

To create a snapshot, follow these steps:

1. Open the required data center.

2. (Optional) Shut down the server. Creating a snapshot while the server is running takes longer.

3. Open the context menu of the storage element and select Create Snapshot.

4. (Optional) Change the name and the description of the snapshot.

5. Click Create Snapshot to start the process.

Delete a Snapshot

If you no longer need a snapshot and want to save your resources, you can delete it. You cannot restore a snapshot after it is deleted.

To delete a snapshot, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to Menu > Management > Images & Snapshots.

3. Open the Snapshots tab and select the snapshot you would like to delete.

4. Click Delete.

5. In the dialog that appears, confirm your action by entering your password and clicking OK.

Overview

Cloud-init is a software package that automates the initialization of servers during system boot. When you deploy a new Linux server from an image, cloud-init gives you the option to set default user data.

User data must be written in shell scripts or cloud-config directives using YAML syntax. You can modify IONOS cloud-init's behavior via user-data. You can pass the user data in various formats to the IONOS cloud-init at launch time. Typically, this happens as a template, a parameter in the CLI, etc. This method is highly compatible across platforms and fully secure.

Compatibility: This service is supported on all public IONOS Cloud Linux distributions. You may submit user data through the DCD or via Cloud API. Existing cloud-init configurations from other providers are compatible with IONOS Cloud.

Limitations: Cloud-init is available on all public Linux images supplied by IONOS Cloud. If you wish to use your own Linux image, please make sure that it is cloud-init supported first. Otherwise, there is no guarantee that the package will function as intended. Windows images are currently out of scope; adding them may be considered at a later stage.

Provisioning: Cloud-init can only be set at initial provisioning. It cannot be applied to instances that have already been provisioned. Settings cannot be changed once provisioned.

Laptops: When using a laptop, scroll down the properties panel of the block storage volume that you want to create and configure, as additional fields are not immediately visible on a small screen. Clout-Init may only become visible when an supported image has been selected.

Supported user data formats

The following table demonstrates the use of cloud-config and user-data scripts. However, the cloud-init package supports a variety of formats.

Configuring user data via the DCD

1. Log in to the DCD with your username and password.

2. In the Workspace, create a new virtual instance and attach any storage device to it.

3. Select the storage device and from the Inspector pane associate an Image with it.

   • To associate a private image, select Own Images from the drop-down list.

   • To associate a public image, select IONOS Images from the drop-down list. Once you choose an image, additional fields will appear in the Inspector pane.

1. Enter a Password. It is required for Remote Console access. You may change it later.

2. (Optional) Upload a new SSH key or use an existing file. SSH Keys can also be injected as user data utilizing cloud-init.

3. (Optional) Add a specific key to the Ad-hoc SSH Key field.

4. Select No configuration for Cloud-Init user data and the Cloud-Init User Data window appears.

5. Enter your User Data either using a bash script or a cloud-config file with a YAML syntax. For sample scripts, see Use shell scripts, Use cloud-config directives, and Configure user data via API.

1. To complete setup, return to the Inspector pane and click Provision Changes.

Use shell scripts

Using shell scripts is an easy way to bootstrap a server. The code creates, installs, and configures our CentOS web server in the following example. It also rewrites the default index.html file.

#!/bin/bash
# Use this for your user data (script from top to bottom)
# install httpd (Linux 2 version)
yum update -y
yum install -y httpd
systemctl start httpd
systemctl enable httpd
echo "<h1>Hello World from $(hostname -f)</h1>" > /var/www/html/index.html

To test if the cloud-init bootstrapped your VM successfully, you can open the corresponding IP address in your browser. You will be greeted with a “Hello World” message from your web server.

Use cloud-config directives

You can also bootstrap cloud-init images using cloud-config directives. The cloud-init website outlines all the supported modules and provides examples of basic directives.

Example 1: Create a swap partition

The following script is an example of how to create a swap partition with second block storage using a YAML script:

#cloud-config
fs_setup:
  - label: mylabel
    device: /dev/vda
    filesystem: ext4
  - label: swap
    device: /dev/vdb
    filesystem: swap
mounts:
- [ /dev/vda, /, ext4, defaults, 0, 0 ]
- [ /dev/vdb, none, swap, sw, 0, 0 ]

Example 2: Resize the file system

The following script is an example of how to resize your file system according to the chosen size of the block storage. It will also create a user with an SSH key using a cloud-config YAML script:

#cloud-config
resize_rootfs: True
users:
  - name: pb-user
    gecos: Demo User
    sudo: ALL=(ALL) NOPASSWD:ALL
    groups: users, admin
    ssh_import_id: None
    lock_passwd: true
    ssh_authorized_keys:
      - ssh-rsa AAAA...

Output log files

The cloud-init output log file (/var/log/cloud-init-output.log) captures console output. Depending on the default configuration for logging, a second log file exists within /var/log/cloud-init.log. This provides a comprehensive record based on the user data.

Configure user data via API

The cloud API offers increased convenience if you want to automate the provisioning and configuration of cloud instances. Enter the following details:

• Name: Enter the userData.

• Type: Enter the type in the form of a string.

• Description: The cloud-init configuration for the volume as base64 encoded string. The property is immutable and is only allowed to be set on a new volume creation. It is mandatory to provide either public image or imageAliasthat has cloud-init compatibility in conjunction with this property.

Cloud-init is configured on the volume resource for cloud API V6 or later versions. For more information, see CLOUD API (6.0).

Curl example

The following script is an example of how to configure userData using curl:

curl --include \
     --request POST \
     --user '<user:password>' \
     --header "Content-Type: application/json" \
     --data-binary '{
         "properties": {
             "name": "Server-01",
             "ram": 2048,
             "cores": 1,
             "availabilityZone": "ZONE_1",
             "cpuFamily": "INTEL_SKYLAKE"
         },
         "entities": {
             "volumes": {
                 "items": [ {
                    "properties": {
                      "size": 10,
                      "type": "HDD",
                      "name": "Server-01_HDD",
                      "image": "bf4d1400-b48d-11eb-b9b3-d2869b2d44d9",
                      "imagePassword": "<pAsSW0rD>",
                      "sshKeys": ["<ssh_key>"],
                      "userData": "I2Nsb3VkLWNvbmZpZwoKcGFja2FnZXM6CiAgLSBodHRwZAogIC0gZmlyZXdhbGxkCgpydW5jbWQ6CiAgLSAvYmluL3N5c3RlbWN0bCBlbmFibGUgaHR0cGQKICAtIC9iaW4vc3lzdGVtY3RsIHN0YXJ0IGh0dHBkCiAgLSAvYmluL2ZpcmV3YWxsLW9mZmxpbmUtY21kIC0tYWRkLXBvcnQ9ODAvdGNwCiAgLSAvYmluL3N5c3RlbWN0bCBlbmFibGUgZmlyZXdhbGxkCiAgLSAvYmluL3N5c3RlbWN0bCBzdGFydCBmaXJld2FsbGQKICAtIGxvYWRrZXlzIGRlCgp3cml0ZV9maWxlczoKLSBjb250ZW50OiB8CiAgICA8IURPQ1RZUEUgaHRtbD4KICAgIDxodG1sPgogICAgICA8aGVhZD4KICAgICAgPC9oZWFkPgogICAgICA8Ym9keT4KICAgICAgICA8cD5XZWxjb21lIHRvIHlvdXIgbmV3IHdlYiBzZXJ2ZXIuPC9wPgogICAgICA8L2JvZHk+CiAgICA8L2h0bWw+CiAgcGF0aDogL3Zhci93d3cvaHRtbC9pbmRleC5odG1sCgpmaW5hbF9tZXNzYWdlOiAiVGhlIHN5c3RlbSBpcyBmaW5hbGx5IHVwLCBhZnRlciAkVVBUSU1FIHNlY29uZHMiCg=="
                    }
                 } ]
             },
             "nics": {
                 "items": [ {
                    "properties": {
                      "name": "NIC001",
                      "dhcp": true,
                      "lan": 1
                      }
                    } ]
             }
        }
        }' \
 https://api.ionos.com/cloudapi/v6/datacenters/<datacenter_id>/servers

You can migrate your images into the IONOS cloud infrastructure by uploading them via the FTP. For more information, see Block Storage FAQs. Your IONOS account supports many types of block storage images as well as ISO images, using an emulated CD-Rom drive, from which you can install an operating system or software directly.

Image types

The following image types are supported; hence, you can upload any of these:

FTP access endpoints

The list below contains the FTP access endpoints for corresponding locations:

Alternatively, you can also find the FTP addresses on the DCD. To retrieve the details, log in to the DCD with your credentials, and click:

• Menu > Help (Question Mark icon) > FTP Image Upload

• Menu > Management > Images & Snapshots > FTP Upload Image

License

Currently, IONOS does not support the Bring-Your-Own-License (BYOL) option for license or subscription based operating systems like Microsoft Windows Server or Red Hat Enterprise Linux. If you want to use one of these two options for private images, IONOS will still grant you the license and charge you when a virtual machine boots from the private image.

Private image authentication

Private images inherit the same authentication defined during their creation. Therefore, the option to set an administrator password or apply an SSH key is not displayed when using a private image.

You can create snapshots from provisioned block storage volumes only. It includes the authentication you specified during the creation of the snapshot. IONOS does not modify snapshots at any time. If you want to change the authentication configurations, we recommend doing it before reusing the snapshot on a new block storage device.

Upload an image via the FTP

IONOS offers you FTP access to each data center location so you can upload your own images. Access to images is location-specific, meaning if you have uploaded an image from location A, it can be accessed only from that specific location. You can also set access rights to only allow authorized users to access and use them. Only images and snapshots to which you have access are displayed.

To upload an image, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to either of the following:

   • Menu > Help (Question Mark icon) > FTP Image Upload.

   • Menu > Management > Images & Snapshots > FTP Upload Image.

1. Set up a connection from your computer to the IONOS FTP server. You can use an FTP client such as FileZilla or tools from your operating system to establish a connection. Enter the following details:

   • Protocol: Select FTP - File Transfer Protocol from the drop-down list.

   • Host: Paste the appropriate FTP server address to the corresponding IONOS data center location. For example, ftp-txl.ionos.com for Berlin.

   • Encryption: Select Require explicit FTP over TLS to establish a connection. Upon selecting this option, the FTP client connects securely to the data center location using port 21, which is the default.

   • Port: By default, the client-to-server connection is established over port 21 for the specified encryption.

   • User: Enter your IONOS username to establish a secure client-to-server connection.

   • Password: Enter your IONOS password to authenticate your credentials in order to establish a client-to-server connection.

2. Upload the image.

3. The image is changed to a RAW format after upload. As a result, dynamic HDD images are always used at their maximum size. A dynamic image, for example, whose file size is 3 GB but which comes from a 50 GB hard disk, will be a 50 GB image again after conversion to the IONOS format. The conversion process generally takes a few minutes based on the size of your image.

Alternatively, you can also use the IonosCTL CLI to upload images directly from the command line to the FTP server using the FTP over TLS (FTPS) setting. Note that the option can be used only if 2-Factor Authentication is disabled for your IONOS account.

Establish an FTP connection to upload images via the Windows Explorer

In Windows 10, you can upload an image, without additional software. To establish an FTP connection, follow these steps:

1. Open Windows Explorer.

2. Select Add a network location from the context menu.

3. Enter the IONOS FTP address as the location of the website. Example: ftps://ftps-fkb.ionos.com. An image is only available at the location where it was uploaded.

4. Select Log on anonymously in the next dialog box that appears.

5. Enter a name for the connection in the following dialog box. The name will later be visible in Windows Explorer. Example: upload_fkb.

6. Click Finish to confirm your action.

Upload your image through the established FTP connection

1. Open the FTP access on your local computer.

2. In the login dialog box, enter the credentials of your IONOS account.

3. Copy the image from your local computer and paste it to a folder in the data center. The image type must be, either HDD or iso.

Access and manage a private image

After completing the upload and conversion process, you can manage your uploaded images via the DCD.

To access and manage your images, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to the Menu > Management > Images & Snapshots.

3. Modify the following details, if necessary:

   • Name: Rename the image, if required.

   • Live Vertical Scaling: Enable this option if your image supports live vertical scaling, so that the Virtual Machine (VM) boots from this image.

   • License Type: Specify the license type of the image that will be propagated to the VM when booting from this image.

Delete a private image

You can delete your private image if you no longer need it, thus saving resources.

To delete an image, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to the Menu > Management > Images & Snapshots.

3. Open the Image tab and select the private image you would like to delete.

4. Click Delete.

5. In the dialog that appears, confirm your action by entering your password and clicking OK.