|
| 1 | +--- |
| 2 | +title: Using a Red Hat Enterprise Linux (RHEL) Bring Your Own Subscription (BYOS) on a Scaleway Instance |
| 3 | +description: Find out how to use a Red Hat Enterprise Linux (RHEL) Bring Your Own Subscription (BYOS) on a Scaleway Instance. |
| 4 | +dates: |
| 5 | + validation: 2025-11-05 |
| 6 | + posted: 2025-11-05 |
| 7 | +tags: Instance red hat byos |
| 8 | +--- |
| 9 | +import Requirements from '@macros/iam/requirements.mdx' |
| 10 | + |
| 11 | +Bring Your Own Subscription (BYOS) allows you to deploy Red Hat Enterprise Linux on Scaleway Instances using your existing Red Hat subscription. |
| 12 | +This means you can deploy a RHEL Instance directly from the Scaleway console, but you must activate it with your own Red Hat subscription to receive updates, security patches and support. |
| 13 | + |
| 14 | +This guide explains how to deploy a RHEL Instance and attach your existing Red Hat subscription. |
| 15 | + |
| 16 | +<Requirements /> |
| 17 | + |
| 18 | +- A Scaleway account logged into the [console](https://console.scaleway.com) |
| 19 | +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization |
| 20 | +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) for Instance access |
| 21 | +- An active Red Hat subscription eligible for [Red Hat Cloud Access](https://access.redhat.com/management/cloud). |
| 22 | +- A Red Hat Customer Portal account |
| 23 | + |
| 24 | +## Deploying a RHEL Instance |
| 25 | + |
| 26 | + |
| 27 | +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. |
| 28 | +2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. |
| 29 | +3. Configure the Instance: |
| 30 | + |
| 31 | + * Choose an Availability Zone |
| 32 | + * Select an Instance type |
| 33 | + * Select **Red Hat Enterprise Linux (BYOS)** as OS image |
| 34 | + * Add and configure storage volumes |
| 35 | + * Configure the network connectivity of the Instance |
| 36 | + * Verify the SSH keys that are allowed to connect |
| 37 | +4. Click **Create Instance**. |
| 38 | + Your RHEL Instance will be provisioned. |
| 39 | + It will boot successfully but will not yet have access to Red Hat software repositories until activated. |
| 40 | + |
| 41 | +<Message type="important"> |
| 42 | + Your Instance runs unentitled to Red Hat Cloud Access for updates directly from Red Hat repositories until you attach your subscription with Red Hat Subscription Manager. |
| 43 | +</Message> |
| 44 | + |
| 45 | +<Message type="note"> |
| 46 | + For more detailed information about creating an Instance, refer to [How to create an Instance](/instances/how-to/create-an-instance/). |
| 47 | +</Message> |
| 48 | + |
| 49 | +## Connecting to your Instance |
| 50 | + |
| 51 | +Once created, connect to your Instance over SSH: |
| 52 | + |
| 53 | + ```bash |
| 54 | + ssh root@<your_instance_ip> |
| 55 | + ``` |
| 56 | + Replace `<your_instance_ip>` with the actual public IP address of your Instance. |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | +## Registering your Instance with Red Hat |
| 61 | + |
| 62 | +After logging in, you must register the Instance to enable repositories and updates. |
| 63 | + |
| 64 | +### Option A — Register with username/password |
| 65 | + |
| 66 | +Run the following command to register your Instance using your Red Hat username and password: |
| 67 | + ```bash |
| 68 | + sudo subscription-manager register |
| 69 | + ``` |
| 70 | + Enter your Red Hat Customer Portal credentials when prompted. |
| 71 | + |
| 72 | +### Option B — Register with activation key |
| 73 | + |
| 74 | +If you have an activation key to register your Instance, run the following command |
| 75 | + ```bash |
| 76 | + sudo subscription-manager register \ |
| 77 | + --org=<RED_HAT_ORGANIZATION_ID> \ |
| 78 | + --activationkey=<RED_HAT_KEY> |
| 79 | + ``` |
| 80 | + Replace `RED_HAT_ORGANIZATION_ID` with your Red Hat organization ID and `RED_HAT_KEY` with your secret key issued by Red Hat. |
| 81 | + |
| 82 | +## Attach a subscription |
| 83 | + |
| 84 | +If your subscription is not automatically assigned, attach one manually: |
| 85 | + ```bash |
| 86 | + sudo subscription-manager attach --auto |
| 87 | + ``` |
| 88 | + |
| 89 | +Alternatively, you can list available subscriptions: |
| 90 | + ```bash |
| 91 | + sudo subscription-manager list --available |
| 92 | + ``` |
| 93 | + |
| 94 | +Chose a license and attach one: |
| 95 | + ```bash |
| 96 | + sudo subscription-manager attach --pool=<RED_HAT_POOL_ID> |
| 97 | + ``` |
| 98 | + Replace `RED_HAT_POOL_ID` with the ID of the license pool you want to activate. |
| 99 | + |
| 100 | +## Confirm registration |
| 101 | + |
| 102 | +Run the following command to verify that the subscription and repositories are active: |
| 103 | + ```bash |
| 104 | + sudo subscription-manager status |
| 105 | + sudo yum repolist |
| 106 | + ``` |
| 107 | + |
| 108 | +You should now see enabled repositories such as: |
| 109 | + ``` |
| 110 | + rhel-8-baseos-rpms |
| 111 | + rhel-8-appstream-rpms |
| 112 | + ``` |
| 113 | + |
| 114 | +## Updating packages |
| 115 | + |
| 116 | +After registration, update your system to ensure it is up to date: |
| 117 | + ```bash |
| 118 | + sudo dnf update -y |
| 119 | + ``` |
| 120 | + |
| 121 | +## Unregistering (optional) |
| 122 | + |
| 123 | +If you plan to delete the Instance or move your subscription, unregister it first: |
| 124 | + ```bash |
| 125 | + sudo subscription-manager remove --all |
| 126 | + sudo subscription-manager unregister |
| 127 | + sudo subscription-manager clean |
| 128 | + ``` |
| 129 | + |
| 130 | +--- |
| 131 | + |
| 132 | +## FAQ |
| 133 | + |
| 134 | +### Do I need to provide a license during Instance creation? |
| 135 | + |
| 136 | +No. You can deploy the RHEL image without a license, but the Instance will not have access to updates or repositories until registration. |
| 137 | + |
| 138 | +### Is Red Hat support included with Scaleway? |
| 139 | + |
| 140 | +No. RHEL on Scaleway is **BYOS** (Bring Your Own Subscription): support is provided directly through your Red Hat subscription. |
| 141 | + |
| 142 | +## Can I order a RHEL license directly from Scaleway? |
| 143 | + |
| 144 | +No. You have to order the RHEL license directly from Red Hat using your Red Hat Customer Portal |
0 commit comments