AlmaLinux 8.10 AMI - RHEL 8 Compatible Server User Guide
Overview
This guide covers the cloudimg AlmaLinux 8.10 AMI on AWS Marketplace, listed as "AlmaLinux 8.10 AMI - RHEL 8 Compatible Enterprise Linux Server". AlmaLinux 8 is a community enterprise Linux distribution, binary compatible with Red Hat Enterprise Linux 8.
The listing has one software version, "Alma Linux 8 - 30-04-2026". Every fact in this guide was checked on a fresh launch of that version on 14 November 2026.
What's on the image:
| Component | Detail |
|---|---|
| Operating system | AlmaLinux 8.10 (Cerulean Leopard) |
| Kernel | 4.18.0-553.120.1 (the April 2026 build) |
| Packages | 618 RPMs, including gcc, make, wget, curl, unzip, tar, bind-utils, net-tools and tuned |
| Repositories | baseos, appstream, extras and EPEL |
| AWS CLI | v2 (2.7.7) |
| AWS Systems Manager Agent | Installed and running at boot |
| Amazon CloudWatch agent | Installed, not configured |
| Root EBS volume | 80 GB, of which 50 GB is partitioned (see "Disk Layout" below) |
- Key-only SSH as
ec2-user, a member of thewheelgroup withsudo; password authentication is off - A security update that runs at every boot (see "On Startup" below)
- SELinux is disabled and firewalld is not running. Your security group is the network control until you enable them (see "SELinux and firewalld" below)
gitandpython3are not installed (the system'splatform-pythonis); install them withdnfwhen you need them
Licensing
AlmaLinux is free and open source software, built by the AlmaLinux OS Foundation; its packages carry their own open source licences. No Red Hat subscription is needed. The hourly charge on the listing is cloudimg's, for patching, configuring and packaging this image.
AlmaLinux is a trademark of the AlmaLinux OS Foundation. Red Hat and RHEL are trademarks of Red Hat, Inc. cloudimg is not affiliated with or endorsed by the AlmaLinux OS Foundation or Red Hat.
Prerequisites
- An active AWS account and a subscription to the AlmaLinux 8.10 AMI listing on AWS Marketplace
- An EC2 key pair for SSH access
Instance type: t3.medium (2 vCPU, 4 GB RAM) or larger, depending on your workload.
Step 1: Launch the AMI
- Open the listing on AWS Marketplace, click Continue to Subscribe, accept the terms, then Continue to Configuration
- Choose your Region and the software version "Alma Linux 8 - 30-04-2026", then Continue to Launch and Launch through EC2
- Choose your instance type
- In your Security Group, allow:
| Port | Protocol | Source | Purpose |
|---|---|---|---|
| 22 | TCP | Your IP | SSH access |
Add rules for the ports your own services use (for example 80 or 443) when you need them.
- Select your key pair and launch the instance
Step 2: Connect via SSH
When the instance has passed both status checks (2/2), connect as ec2-user:
ssh -i your-key.pem ec2-user@<public-ip-address>
Password authentication is off, so the key pair is the only way in over SSH. At every boot a script reads the instance's public key from the instance metadata service (it supports IMDSv2) and installs it for ec2-user.
For administration, use sudo, or open a root shell:
sudo su -
Step 3: Check the System
cat /etc/almalinux-release
uname -r
dnf repolist
The release file shows AlmaLinux 8.10 and uname -r shows the running kernel (4.18.0-553.120.1 until you update it).
On Startup
At every boot, root's crontab runs /stage/scripts/initial_boot_update.sh (an @reboot entry). It applies AlmaLinux security errata only, with the kernel excluded:
yum -y update --security --exclude=kernel*
Its output goes to /stage/scripts/initial_boot_update.log. The script stays in place, so it runs again at every start-up, not only the first.
Right after a boot, wait for it to finish before you use dnf yourself:
sudo tail -f /stage/scripts/initial_boot_update.log
pgrep -af initial_boot_update # no output means it has finished
What it does not update:
- The kernel. See "Updating the Kernel" below.
- Packages with no security advisory. For a full update, run
sudo dnf update.
To stop the boot update, remove its crontab entry. List root's crontab first:
sudo crontab -l
Then edit it and delete only the @reboot line that runs /stage/scripts/initial_boot_update.sh; leave any other line in place:
sudo crontab -e
If you stop it, schedule your own updates (for example dnf-automatic, or AWS Systems Manager Patch Manager).
Updating the Kernel
The boot update never touches the kernel, so a new instance runs the kernel the image was built with. To bring it current:
sudo dnf update kernel
sudo reboot
Or update everything at once with sudo dnf update, then reboot. After the reboot, uname -r shows the new kernel.
Disk Layout
The root EBS volume is 80 GB, but only 50 GB of it is partitioned:
| Partition | Size |
|---|---|
| /boot | 2 GB |
| / (root filesystem) | 38 GB |
| swap | 10 GB |
| Unallocated | 30 GB |
See the layout and filesystem types on your instance:
lsblk -f
df -hT / /boot
swapon --show
Using the unallocated 30 GB
Check two things in the lsblk output first: which partition is the root filesystem, and whether it is the last partition on the disk (on t3 and other Nitro instances the disk is /dev/nvme0n1 and its partitions are /dev/nvme0n1p1, p2 and so on; on older instance types it is /dev/xvda). Take a snapshot of the volume before you change partitions.
If the root partition is the last partition, grow it into the free space, then grow the filesystem. growpart is in the cloud-utils-growpart package:
sudo dnf install -y cloud-utils-growpart
# Replace 3 with the root partition's number from lsblk
sudo growpart /dev/nvme0n1 3
Then grow the filesystem with the tool for the type df -hT / shows:
# XFS
sudo xfs_growfs /
# ext4 (use the root partition's device name)
sudo resize2fs /dev/nvme0n1p3
If another partition (for example swap) comes after the root partition, growpart cannot extend the root partition into the free space. Use the free space as a new partition instead, for example for application data:
# Create a partition in the free space at the end of the disk
sudo dnf install -y parted
sudo parted /dev/nvme0n1 print free
sudo parted /dev/nvme0n1 mkpart primary xfs <start-of-free-space> 100%
sudo partprobe /dev/nvme0n1
lsblk
Before you format, confirm the device name. /dev/nvme0n1p4 below is only an example: in the lsblk output, find the partition you just created (the new one, of the size of the free space, with no mount point) and use its name in place of /dev/nvme0n1p4 in every command below. Formatting the wrong device destroys the data on it, including the operating system.
# Format and mount the new partition (replace /dev/nvme0n1p4 with the name lsblk shows)
sudo mkfs.xfs /dev/nvme0n1p4
sudo mkdir -p /data
sudo mount /dev/nvme0n1p4 /data
Add the new filesystem to /etc/fstab by UUID (sudo blkid /dev/nvme0n1p4, with your device name) with the nofail option so it mounts at every boot.
The same steps apply after you enlarge the EBS volume in the EC2 console: the extra space appears as unallocated space at the end of the disk.
SELinux and firewalld
On this image SELinux is disabled and firewalld is not running. Check:
getenforce
sudo systemctl status firewalld
To enable SELinux, set it in /etc/selinux/config, ask for a full relabel and reboot. Start in permissive mode, which logs denials without blocking, and move to enforcing once your applications run cleanly:
sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config
sudo touch /.autorelabel
sudo reboot
The relabel makes that boot take longer. After it, review denials with sudo ausearch -m avc -ts recent, then set SELINUX=enforcing in the same file and reboot again.
To enable firewalld, install it if it is missing, start it and confirm SSH is allowed before you log out:
sudo dnf install -y firewalld
sudo systemctl enable --now firewalld
sudo firewall-cmd --list-services
# If ssh is not listed:
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reload
Open other services the same way, for example sudo firewall-cmd --permanent --add-service=https.
AWS Tools
AWS CLI v2
aws --version
The image has AWS CLI 2.7.7. Give the instance an IAM role (instance profile) with the permissions your commands need instead of storing access keys on the instance. To update the CLI to the latest v2 release, use AWS's installer:
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o awscliv2.zip
unzip awscliv2.zip
sudo ./aws/install --update
aws --version
If which aws shows a path other than /usr/local/bin/aws, pass the matching --bin-dir and --install-dir to ./aws/install (see the AWS CLI installation documentation).
AWS Systems Manager Agent
The SSM Agent is installed and running at boot:
sudo systemctl status amazon-ssm-agent
To manage the instance with Session Manager, Run Command or Patch Manager, attach an IAM role with the AmazonSSMManagedInstanceCore policy. The instance also needs a route to the Systems Manager endpoints (internet access, a NAT gateway or VPC endpoints).
Amazon CloudWatch agent
The CloudWatch agent is installed but not configured. Attach an IAM role with the CloudWatchAgentServerPolicy policy, then run the configuration wizard:
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-config-wizard
The wizard saves its answers to /opt/aws/amazon-cloudwatch-agent/bin/config.json. Load that file and start the agent:
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file:/opt/aws/amazon-cloudwatch-agent/bin/config.json
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a status
Installing Software
Install packages from the AlmaLinux and EPEL repositories with dnf:
sudo dnf install -y git python3
dnf module list
AppStream modules give other versions of language runtimes and databases; list the streams for one with, for example, dnf module list nodejs.
Troubleshooting
Permission denied (publickey)
Connect as ec2-user (not root or almalinux) with the private key of the key pair you chose at launch, and check the key file's permissions (chmod 400 your-key.pem). Password logins are off.
SSH times out
Check that the security group allows TCP 22 from your current IP address, that the instance has a public IP (or you are connecting over a VPN or bastion), and that the subnet's route table has a route to an internet gateway. If you enabled firewalld, check that ssh is in sudo firewall-cmd --list-services.
dnf waits for a lock, or is slow just after boot
The boot security update is still running. Wait for it to finish (pgrep -af initial_boot_update returns nothing) and try again; its log is /stage/scripts/initial_boot_update.log.
The kernel did not change after a boot
This is expected: the boot update excludes the kernel. Run sudo dnf update kernel and reboot.
Root filesystem is full but the volume is 80 GB
Only 50 GB of the volume is partitioned. See "Using the unallocated 30 GB" above. Find what is using the space with sudo du -xh / --max-depth=1 | sort -h, and clear the package cache with sudo dnf clean all.
Session Manager does not show the instance
Check that the instance has an IAM role with AmazonSSMManagedInstanceCore, that it can reach the Systems Manager endpoints, and the agent's state with sudo systemctl status amazon-ssm-agent.
CloudWatch shows no metrics or logs
The agent is not configured on this image. Run the wizard and fetch-config as in "Amazon CloudWatch agent" above, and check the IAM role has CloudWatchAgentServerPolicy. The agent's log is /opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log.
Security Recommendations
- Allow port 22 from trusted addresses only, and open other ports only where needed
- Enable SELinux and firewalld if your policy needs them (see "SELinux and firewalld" above)
- Update the kernel and the remaining packages with
sudo dnf updateand a reboot; the boot update applies security errata only and never the kernel - Use IAM roles for AWS access rather than access keys stored on the instance
- Consider requiring IMDSv2 on the instance (EC2 console, Actions > Instance settings > Modify instance metadata options)
- Take regular EBS snapshots of volumes holding data you need
Support
cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours:
- Email: support@cloudimg.co.uk
- Website: www.cloudimg.co.uk