You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/enterprise-support-for-almalinux/README.md
+84-38Lines changed: 84 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,44 +144,6 @@ Then you will have to run `tuxctl` like this:
144
144
145
145
:::
146
146
147
-
### SaaS usage
148
-
149
-
If you are using ESU with our SaaS license in AWS, then the instructions are slightly different. You should login to your instance and run the following as root (use of `--fips` is optional depending on your needs):
If you want to reclaim a license when you terminate an instance, you should first run:
158
-
159
-
```text
160
-
# tuxctl --delete
161
-
162
-
De-registration successful
163
-
```
164
-
165
-
Then you can use that license to register another instance.
166
-
167
-
If you want to check if you've already registered an instance, you can run the following to display your token:
168
-
169
-
```text
170
-
# tuxctl --validate
171
-
172
-
Server is registered with token EXTENDED_SECURITY_UPDATES-SERVER-xxxxx
173
-
```
174
-
175
-
If the instance has no license installed, it will return:
176
-
177
-
```text
178
-
Server is not registered
179
-
```
180
-
181
-
:::warning
182
-
We can provide a systemd unit file and instructions, should you want to incorporate installing tuxcare-release and registering using tuxctl into your AMI, so that when you spin-up an instance its ready to receive patches, simply email [[email protected]]([email protected])
183
-
:::
184
-
185
147
### Enabling FIPS 140-3 mode
186
148
187
149
First please ensure you have installed the `tuxcare-release` package as described above. If you haven't already registered your ESU license using `tuxctl` the next step will also do that for you.
@@ -267,6 +229,90 @@ Then run the following:
267
229
# dnf upgrade
268
230
```
269
231
232
+
### Migrating from CentOS
233
+
234
+
This guide contains steps on how to upgrade from CentOS 7 or Stream 8 [ELS](https://tuxcare.com/endless-lifecycle-support/centos-stream-8-eol-support/) to AlmaLinux 9.2 [ESU](https://tuxcare.com/fips-for-almalinux/).
235
+
236
+
You will require an ESU license key from [https://tuxcare.com/buy/almalinux/](https://tuxcare.com/buy/almalinux/) or talk to your Account Manager about our ELS-to-ESU migration bundle offer.
237
+
238
+
:::warning
239
+
Ensure that you have a non-root user who can SSH and elevate privileges to root using su/sudo as this process will disable root SSH login. FIPS mode will also disable non-RSA SSH keys. Console access is recommended.
240
+
:::
241
+
242
+
Choose **one** of the migrations below (1a or 1b) based on your CentOS ELS version. Once you have migrated to AlmaLinux 8, the instructions for getting to 9.2 and enabling ESU/FIPS are the same.
0 commit comments