Append RHEL ELS licenses Stay organized with collections Save and categorize content based on your preferences.
This document shows you how to append the ELS Add-On to RHEL compute instancesthat have on-demand licenses for their images and have reached end ofmaintenance.
When a Red Hat Enterprise Linux (RHEL) versionreaches end of maintenance and your OS image usesan on-demand license, support and access to these Compute Engine instancesare limited according to theMaintenance policy for lifecycle stage.
For extended support, which provides critical impact security fixes and selectedurgent priority bug fixes, you can append the RHEL Extended Life Cycle Support(ELS) Add-On. The ELS Add-On applies to the last minor release of a majorrelease as follows:
- For RHEL 7, the ELS Add-On applies to the latest minor release which is RHEL7.9 or RHEL 7.9 for SAP. The ELS Add-On for RHEL 7 is available until June 30, 2028.
- For RHEL 6, the ELS Add-On applies to the latest minor release which is RHEL6.10. The ELS Add-On for RHEL 6 is available until June 30, 2024. The ELSAdd-On is appended automatically to the RHEL 6.10 instanceswhen you migrate them to Google Cloud.
For more information, see theRHEL Life Cycle and theFAQ.
Overview
You append the ELS license by doing the following for each compute instance:
Stop the instance and append the license to the boot disk.
Caution: Google recommends usingreservations to ensuremachine availability while the compute instance is shut down.Validate the license and start the instance.
Install the Red Hat Update Infrastructure (RHUI) ELS client package on theinstance.
Before you begin
The ELS Add-On only applies to the latest minor release. For each RHEL instance, update to the latest minor release byconnecting to the VM and running the following command:
sudo yum -y update
- If you haven't already, set upauthentication. Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:
gcloudinit
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.- Set a default region and zone.
Required roles
To get the permissions that you need to append the ELS license to your instance, ask your administrator to grant you the following IAM roles on the project:
- Compute Instance Admin (v1) (
roles/compute.instanceAdmin.v1) - To connect to an instance that can run as a service account:Service Account User (v1) (
roles/iam.serviceAccountUser)
For more information about granting roles, seeManage access to projects, folders, and organizations.
These predefined roles contain the permissions required to append the ELS license to your instance. To see the exact permissions that are required, expand theRequired permissions section:
Required permissions
The following permissions are required to append the ELS license to your instance:
- To start and stop the instance:
compute.instances.stopon the projectcompute.instances.starton the project
- To view the disks attached to the instance:
compute.instances.geton the instancecompute.disks.geton the instancecompute.disks.liston the instance
- To update the boot disk of the instance:
compute.disks.geton the boot diskcompute.disks.updateon the boot disk
You might also be able to get these permissions withcustom roles or otherpredefined roles.
Billing
After you attach RHEL ELS to a disk, Compute Engine adds anadditional SKU to your bill.
For example if you are using RHEL 7,your billincludes one line item for RHEL 7 and another for RHEL 7 ELS.
You are billed for RHEL instances according to thepricing for premium images.
Limitations
You must stop the instance before appending a license.
Append the RHEL ELS license
Append the RHEL ELS license to the Linux VM's boot disk by using the followingprocedure:
Caution: Google recommends usingreservations to ensuremachine availability while the VM is shut down.Stop the VM by using the
gcloud compute instances stopcommand:gcloud compute instances stopVM_NAME
Replace
VM_NAMEwith the name of the VM to stop.List the disks associated with the VM by using the
gcloudcompute instances describecommand:gcloud compute instances describeVM_NAME --format="yaml(disks)"
Replace
VM_NAMEwith the name of the VM.Verify that the output is similar to the following:
disks:- autoDelete: true boot: true deviceName: persistent-disk-0 diskSizeGb: '20' index: 0 interface: SCSI kind: compute#attachedDisk licenses: - https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/RHEL_VERSION - https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/RHEL_ELS_VERSION mode: READ_WRITE source: https://www.googleapis.com/compute/v1/projects/PROJECT_NAME/zones/ZONE/disks/VM_NAME type: PERSISTENTNote that no
Licenseshave been appended yet.Get the name of the boot disk by running the
gcloud compute disks listcommand:gcloud compute disks list
Update the boot disk with the RHEL ELS license URI by using the
gcloud compute disks updatecommand:gcloud compute disks updateBOOT_DISK_NAME \ --zoneZONE \ --append-licenses="https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/RHEL_ELS_VERSION"
Replace the following:
RHEL_VERSION: the RHEL version. For example,rhel-7-server.BOOT_DISK_NAME: the name of the boot disk obtainedin the previous stepZONE: the zone containing the boot diskRHEL_ELS_VERSION: the RHEL ELS version. For example,rhel-7-els.
Validate the RHEL ELS license
Check that the RHEL ELS license is appended to the Linux VM boot disk byusing the following procedure:
Get information about the boot disk by using the
gcloud compute disks describecommand:gcloud compute disks describeBOOT_DISK_NAME \ --zoneZONE
Replace the following:
BOOT_DISK_NAME: the name of the boot disk to checkfor the appended licenseZONE: the zone containing the boot disk
Verify that the output is similar to the following:
creationTimestamp: '2021-05-05T15:26:27.835-07:00'id: '727854272460268924'interface: SCSIkind: compute#disklabelFingerprint: 42WmSpB8rSM=lastAttachTimestamp: '2021-05-05T15:26:27.836-07:00'licenseCodes:- '1000006'- '6213885950785916969'licenses:- https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/RHEL_VERSION- https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/RHEL_ELS_VERSIONmultiWriter: falsename:VM_NAMEphysicalBlockSizeBytes: '4096'selfLink: https://www.googleapis.com/compute/projects/PROJECT_NAME/zones/ZONE/disks/DISK_NAMEselfLinkWithId: https://www.googleapis.com/compute/projects/PROJECT_NAME/zones/ZONE/disks/DISK_IDsizeGb: '20'sourceImage: https://www.googleapis.com/compute/projects/IMAGE_PROJECT/global/images/IMAGEsourceImageId: '7397991294075835597'status: READYtype: https://www.googleapis.com/compute/projects/PROJECT_NAME/zones/ZONE/diskTypes/DISK_TYPEusers:- https://www.googleapis.com/compute/projects/PROJECT_NAME/zones/ZONE/instances/VM_NAMEzone: https://www.googleapis.com/compute/projects/PROJECT_NAME/zones/ZONEValidate that the RHEL ELS license is appended to the Linux VM boot disk bychecking the output of the previous step for the
Licensesfield for theappropriate license string.If the
Licensesfield doesn't contain the intended licensing string,you might need to clear and then update the user licenses.For more information, see thegcloud compute disks updatecommand.Start the VM by using the
gcloud compute instances startcommand:gcloud compute instances startVM_NAME \ [--csek-key-fileENCRYPTION_KEY]
Replace the following:
VM_NAME: the name of the VM to startENCRYPTION_KEY: an optional flag that specifies thepath to the Customer-Supplied Encryption Key (CSEK) file if the boot diskis encrypted
Install the RHUI ELS client package
After appending the license string to the RHEL disk, install the RHUI ELSclient package on the VM byconnecting to the VM and running the following commands:
RHEL 7
Check that you are using RHEL 7.9 or RHEL 7.9 for SAP:
cat /etc/redhat-release
Download and install the latest update:
sudo yum -y update
Remove the RHUI client packages and install the RHUI ELS client package:
sudo yum -y remove google-rhui-client-rhel7 google-rhui-client-rhel79-sap google-rhui-client-rhel7-sap sudo yum makecache sudo yum -y install google-rhui-client-rhel7-els
RHEL 6
Check that you are using RHEL 6.10:
cat /etc/redhat-release
Download and install the latest update:
sudo yum -y update
Remove the RHUI client package and install the RHUI ELS client package:
sudo yum -y remove google-rhui-client-rhel6 sudo yum makecache sudo yum -y install google-rhui-client-rhel6-els
View audit logs
View the history of license updates for compute instances by using thefollowing procedure:
In the Google Cloud console, go to theLogs Explorer page.
In the toolbar, ensure thatShow query is enabled.
Copy the following expression into the query editor:
resource.type="gce_disk" logName="projects/PROJECT_NAME/logs/cloudaudit.googleapis.com%2Factivity" severity>=NOTICE protoPayload.request.@type="type.googleapis.com/compute.disks.update" protoPayload.request.licenses:*ReplacePROJECT_NAME with the name of your project.
ClickRun query.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.