Rocky Linux 10 Minimal

Option A: Azure Portal

• Go to the Azure Marketplace and search for "Rocky Linux 10 Minimal SecureAnyCloud".
• Select the image and choose Create.
• Configure the basics:
• Subscription: Select your Azure subscription
• Resource Group: Create new or select existing
• Virtual Machine Name: Enter a name for your VM
• Region: Select your preferred Azure region
• Size: Standard_B2s recommended
• Under Administrator Account, select SSH public key and enter your key.
• Under Inbound Port Rules, allow SSH (port 22).
• Choose Review + Create, then Create.

Option B: Azure CLI

az vm image terms accept --urn sac1647283583153:rocky-10-minimal:default:latest
az vm create \
  --resource-group myResourceGroup \
  --name my-rocky-10-minimal-vm \
  --image sac1647283583153:rocky-10-minimal:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

Run these on your own workstation, not on the VM. Find the public IP, then connect:

az vm show --resource-group myResourceGroup --name my-rocky-10-minimal-vm --show-details --query publicIps -o tsv ssh azureuser@<vm-ip>

There is no password to enter. If SSH asks for one, your client is not offering the key you supplied when you created the VM.

Check the Rocky Linux release and package count:

cat /etc/rocky-release grep -E '^(NAME|VERSION|ID|PLATFORM_ID)=' /etc/os-release uname -rm rpm -qa | wc -l

Expected output:

Rocky Linux release 10.2 (Red Quartz) NAME="Rocky Linux" VERSION="10.2 (Red Quartz)" ID="rocky" PLATFORM_ID="platform:el10" 6.12.0-211.44.1.el10_2.x86_64 x86_64 430

This listing moves forward with the Rocky Linux 10 stream. It ships whichever 10.x point release is current when the image is built. It is not pinned to a single minor release like the SecureAnyCloud Rocky Linux 10.2 image.

The image is fully updated at build time. dnf check-update returns exit code 100 when updates are pending and 0 when none are:

sudo dnf check-update echo "check-update exit code: $?"

Confirm no reboot is outstanding. needs-restarting -r returns 0 when nothing requires a restart:

sudo dnf needs-restarting -r echo "needs-restarting exit code: $?"

List the enabled repositories to confirm your update path is intact:

dnf repolist --enabled

Expected output:

repo id repo name appstream Rocky Linux 10 - AppStream baseos Rocky Linux 10 - BaseOS extras Rocky Linux 10 - Extras

CodeReady Builder (crb) is not enabled on this image. It carries developer and build-time packages that most server workloads do not need. Enable it yourself if you need it:

echo "crb state: $(dnf repolist --all 2>/dev/null | grep -c '^crb ')"

To turn it on, run sudo dnf config-manager --set-enabled crb.

Package signatures are verified on every install: no repository on this image sets gpgcheck=0.

This image ships patched and keeps patching itself. dnf-automatic is installed and configured to apply updates, and its timer is enabled so it starts on every boot:

systemctl is-enabled dnf-automatic.timer
systemctl is-active dnf-automatic.timer grep -E '^(upgrade_type|download_updates|apply_updates)' /etc/dnf/automatic.conf

Expected output:

enabled active upgrade_type = default download_updates = yes apply_updates = yes

upgrade_type is deliberately set to default rather than security. The security-only mode resolves against errata metadata. Where that metadata is not published, a security-only policy silently resolves to nothing and applies no updates at all. Setting default applies every available update, so it cannot quietly do nothing.

To control the schedule yourself, disable the timer and patch on your own cadence:

echo "to take manual control: sudo systemctl disable --now dnf-automatic.timer"

To patch by hand at any time, run sudo dnf upgrade -y, then reboot with sudo systemctl reboot if a new kernel was installed.

Confirm that SELinux is enforcing with its policy loaded, root is locked, SSH is key-only, and there is no swap:

getenforce grep -E '^[[:space:]]*SELINUX=' /etc/selinux/config rpm -q selinux-policy-targeted
sudo passwd -S root
sudo sshd -T | grep -E '^(permitrootlogin|passwordauthentication|kbdinteractiveauthentication)' swapon --show

Expected output:

Enforcing SELINUX=enforcing selinux-policy-targeted-42.1.18-4.el10_2.2.noarch root L 2009-12-22 -1 -1 -1 -1 permitrootlogin without-password passwordauthentication no kbdinteractiveauthentication no

The swapon --show command returns nothing. That is expected (see Step 7).

without-password is how OpenSSH reports the prohibit-password setting. Both names mean the same thing: root may not authenticate with a password.

The checks cover the runtime SELinux mode, the persisted /etc/selinux/config value and the selinux-policy-targeted package itself. Checking the package matters. A minimal trim that removed the policy package by accident could still produce plausible getenforce output until the system falls back to Permissive with no policy loaded. That failure is materially worse than a config file that is simply set to permissive.

Confirm that the Azure Linux Agent, cloud-init and time synchronisation are healthy, and check your resources:

systemctl is-active waagent
systemctl is-enabled waagent cloud-init --version
systemctl is-active chronyd df -h / free -h

Note that free -h reports 0B of swap. That is deliberate. Azure manages swap on the ephemeral resource disk through waagent rather than on the OS disk, and a swap file baked into a Marketplace image fails certification. If your workload needs swap, configure it through waagent.

The Azure Network Security Group (NSG) controls inbound and outbound traffic. It is usually the only place you need to open a port.

This image is a Minimal build, so firewalld is not installed. That is deliberate. With no host firewall in the way, your NSG rules take effect exactly as written, and there is no second layer to keep in sync. Confirm what is listening before you open anything:

ss -tlnu

On a fresh machine, SSH on port 22 is the only externally bound listener. Chrony appears on 127.0.0.1:323, which is loopback only and not reachable from the network.

rpcbind is disabled on this image (where present on the base at all). The stock Rocky Linux cloud image can enable it because nfs-utils depends on it, which would otherwise leave TCP and UDP port 111 open on every interface. NFSv4, the default in Rocky Linux 10, does not use rpcbind at all. This image therefore keeps rpcbind disabled and the port closed, while nfs-utils stays installed and fully working for NFSv4 mounts:

echo "rpcbind.socket: $(systemctl is-enabled rpcbind.socket 2>/dev/null || echo disabled)" rpm -q nfs-utils

If you need NFSv3, which does require the portmapper, turn rpcbind back on with one command:

echo "to re-enable NFSv3 support: sudo systemctl enable --now rpcbind.socket"

rpcbind is disabled rather than masked, so that command works without further steps.

If your policy also requires a host firewall, install and enable it yourself:

sudo dnf install -y firewalld
sudo systemctl enable --now firewalld
sudo firewall-cmd --permanent --add-port=443/tcp sudo firewall-cmd --reload

Once firewalld is running, open each port in both the Azure NSG and firewalld. Traffic does not reach your service until both allow it.

This is the same Rocky Linux 10 base as the standard SecureAnyCloud images, with the packages that a headless Azure guest never uses removed. Confirm the trim for yourself:

rpm -qa cockpit-ws cockpit-bridge tuned sos plymouth linux-firmware echo "(no output above = every trimmed package is genuinely absent)"

Removed Why it is safe to remove on Azure

linux-firmware Firmware blobs for physical NICs, GPUs, wireless and storage controllers. An Azure guest's storage and network are the in-kernel Hyper-V synthetic drivers, which load no firmware at all. This is the single largest reduction.

cockpit-ws, cockpit-bridge The web admin console. This is a headless server image with no web UI.

tuned The tuning-profile daemon. Azure images use the platform defaults.

sos The Red Hat support-report collector. Install it yourself if you need it for a support case.

plymouth The graphical boot splash. There is no console to splash to on a cloud VM.

GeoIP data files A bundled dataset unused on a base OS image.

Nothing the platform needs is touched. systemd, NetworkManager, openssh-server, cloud-init, WALinuxAgent, dnf, sudo, chrony and dnf-automatic all ship exactly as on the standard image.

SELinux packages are never trim candidates on this image. selinux-policy, selinux-policy-targeted and the rpm-plugin-selinux/libselinux/cockpit-ws-selinux family are excluded from the trim outright, because removing the wrong Cockpit sub-package can otherwise cascade-remove the SELinux policy itself. Every removal above is verified on the image before it is captured. SELinux enforcing with its policy loaded is checked as a separate, mandatory gate.

AppStream carries the application packages. Search it, then install what you need:

dnf search nginx

Rocky Linux 10 has moved away from DNF4 module streams, and modularity is deprecated on this platform. As a result, dnf module list exits non-zero and reports "No matching Modules to list" for most packages, including nginx. That is expected and is not an error in your setup. AppStream now carries a single current version of each package rather than several parallel streams to choose between:

dnf module list nginx || echo "(modularity is deprecated on Rocky Linux 10 — this is expected)"

Expected output:

WARNING: modularity is deprecated, and functionality will be removed in a future release of DNF5. Error: No matching Modules to list (modularity is deprecated on Rocky Linux 10 — this is expected)

Install a package and enable it in the usual way. For example, run sudo dnf install -y nginx, then sudo systemctl enable --now nginx.

To add another administrator, create the account with sudo adduser <name>. Add it to the wheel group with sudo usermod -aG wheel <name>, then copy your public key into /home/<name>/.ssh/authorized_keys with mode 600 and the .ssh directory mode 700, owned by that user. The image ships with no human accounts, so azureuser is the only login until you add one:

getent group wheel

Option A: AWS Marketplace console

• Open the SecureAnyCloud Rocky Linux listing on AWS Marketplace and choose View purchase options, then Subscribe. One subscription covers every version in the listing.
• Once the subscription is active, choose Launch your software.
• Choose One-click launch from AWS Marketplace (or Launch from EC2 Console for full control), then in Version choose Rocky Linux 10 Minimal - YYYY-MM-DD (the date is when the version was added) and your Region.
• Instance type: m5.large is recommended; any current x86_64 type works. The software charge is $0.04 per vCPU per hour.
• Key pair: choose your EC2 key pair. It is the only way in. RSA and ED25519 keys both work.
• Security group: allow inbound TCP 22 from your own IP address or network only.
• Storage: the root volume is 11 GiB gp3 by default. Choose a larger size if you need one; cloud-init grows the root partition and filesystem to fill it on first boot.
• Metadata: leave the defaults. The image already requires IMDSv2. Then choose Launch.

Option B: AWS CLI

Run this on your own workstation. Replace the AMI ID with the one shown for your Region on the Marketplace launch page, and the key pair, security group and subnet with your own. The root device of this AMI is /dev/sda1:

aws ec2 run-instances \
  --image-id ami-0123456789abcdef0 \
  --instance-type m5.large \
  --key-name my-key-pair \
  --security-group-ids sg-0123456789abcdef0 \
  --subnet-id subnet-0123456789abcdef0 \
  --block-device-mappings 'DeviceName=/dev/sda1,Ebs={VolumeSize=20,VolumeType=gp3}' \
  --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=rocky-linux-10-minimal}]'

You do not need --metadata-options: the AMI already makes IMDSv2 required.

From your workstation, connect as rocky with the key pair you chose:

ssh -i ~/.ssh/my-key-pair.pem rocky@<public-ip>

There is no password to enter. If SSH asks for one, or says Too many authentication failures, see Troubleshooting below.

You can also connect without opening port 22 at all through AWS Systems Manager Session Manager, if the instance has an instance profile that allows Systems Manager. The agent is installed and running on this image.

cat /etc/rocky-release grep -E '^(NAME|VERSION|ID|VERSION_ID|PLATFORM_ID|PRETTY_NAME)=' /etc/os-release uname -srm

Expected output:

Rocky Linux release 10.2 (Red Quartz) NAME="Rocky Linux" VERSION="10.2 (Red Quartz)" ID="rocky" VERSION_ID="10.2" PLATFORM_ID="platform:el10" PRETTY_NAME="Rocky Linux 10.2 (Red Quartz)" Linux 6.12.0-211.66.1.el10_2.x86_64 x86_64

This version follows Rocky Linux 10: it receives every Rocky Linux 10 minor release (10.2 at build time) through normal dnf updates. Your kernel version may be newer if updates have installed since this image was built.

The image lists exactly what was removed, and anything that a removal would have taken with it is kept and listed instead:

cat /usr/share/doc/sac/minimal-manifest.txt rpm -qa | wc -l

Expected output:

Minimal version: packages 468 -> 443 Removed: cockpit-ws cockpit-system Kept (a removal would have taken a protected package, or it failed): 458

The trim takes the package count from 468 to 443. The two named packages are the Cockpit web console; the other 23 are packages that were installed only as part of that stack and left with it, among them sos, the kdump crash-dump tools (kdump-utils, makedumpfile), setroubleshoot, policycoreutils-python-utils and the libraries only they used. Nothing had to be kept back. After the trim, the CIS remediation adds the tools it needs (OpenSCAP, AIDE, systemd-journal-remote and their libraries) and the build removes the superseded kernels, so a new instance has 458 packages. The count on your instance moves by a few as kernels and updates install.

Anything removed is one sudo dnf install away from the standard Rocky Linux repositories, for example sudo dnf -y install sos if a support case asks for an sos report, or sudo dnf -y install kdump-utils if you want kernel crash dumps.

The evaluation the build ran after its reboot ships on the image:

ls -lh /usr/share/doc/sac/ python3 -c "import json; s=json.load(open('/usr/share/doc/sac/cis-l1-summary.json')); print('profile: ', s['profileLabel'], '(SCAP Security Guide', s['ssgVersion'] + ')'); print('scored rules: ', s['scored'], ' pass:', s['pass'], ' fail:', s['fail'], ' rate:', str(s['ratePct']) + '%'); print('waived: ', s['waived'], ' not applicable:', s['notapplicable']); print('evaluated at: ', s['evaluatedAt'])"

Expected output:

total 32M -rw-r--r--. 1 root root 29M Oct 20 00:17 cis-l1-arf.xml -rw-r--r--. 1 root root 2.4M Oct 20 00:17 cis-l1-report.html -rw-r--r--. 1 root root 1.3K Oct 20 00:17 cis-l1-summary.json -rw-r--r--. 1 root root 1.8K Oct 20 00:17 cis-l1-tailoring.xml -rw-r--r--. 1 root root 2.9K Oct 20 00:17 cis-l1-waivers.txt -rw-r--r--. 1 root root 145 Oct 20 00:11 minimal-manifest.txt -rw-r--r--. 1 root root 1.6K Oct 20 00:11 scap-security-guide-LICENSE.txt profile: CIS Level 1 Server (SCAP Security Guide 0.1.82) scored rules: 286 pass: 284 fail: 2 rate: 99.3% waived: 7 not applicable: 31 evaluated at: 2026-10-20T00:17:09Z

• cis-l1-report.html is the full OpenSCAP report, rule by rule. Copy it to your workstation and open it in a browser.
• cis-l1-arf.xml is the same evaluation in the machine-readable ARF format, for compliance tooling.
• cis-l1-tailoring.xml is the exact tailoring used, so you can re-run the same evaluation (Step 6).
• The pass rate is pass / (pass + fail + error + unknown). Rules that are not applicable to this machine, not selected, or waived are not counted.

To copy the report to your workstation, run this on the workstation:

scp -i ~/.ssh/my-key-pair.pem rocky@<public-ip>:/usr/share/doc/sac/cis-l1-report.html .

The seven waived rules

grep -v '^#' /usr/share/doc/sac/cis-l1-waivers.txt | cut -f1,2

Expected output:

partition_for_tmp [single-volume-partitions] grub2_password [serial-console-and-boot] ensure_root_password_configured [serial-console-and-boot] accounts_maximum_age_login_defs [key-only-account-aging] account_disable_post_pw_expiration [key-only-account-aging] sshd_limit_user_access [ssh-access-list] service_systemd-journal-upload_enabled [log-remote-destination]

The full reason for each is the third column of the same file. In short:

• Separate /tmp partition: this version boots from one EBS root volume. (The LVM versions of this listing provide separate volumes for /tmp, /var, /var/log, /var/log/audit, /var/tmp and /home.)
• Boot loader and root passwords: a GRUB or root password would have to be baked into the image, giving every instance the same secret. Root stays locked with no password. Set your own if you need serial console access (see Step 11).
• Password ageing defaults: the accounts cloud-init creates are key-only. An ageing limit would expire them and lock the SSH key out. Accounts that do have a password are still aged.
• SSH AllowUsers/AllowGroups: a list fixed at build time would refuse accounts you create later. Your security group restricts who can reach port 22.
• Remote journal upload: the benchmark enables systemd-journal-upload, which sends the journal to a remote log server. An image cannot know your log server, and with no destination the upload service fails at every boot. systemd-journal-remote is installed and the upload service is left disabled: set URL= in /etc/systemd/journal-upload.conf and run sudo systemctl enable --now systemd-journal-upload to send the journal to your own collector.

The two rules that do not pass

python3 -c "import json; [print(r) for r in json.load(open('/usr/share/doc/sac/cis-l1-summary.json'))['failingRules']]"

Expected output:

ensure_journald_and_rsyslog_not_active_together ensure_redhat_gpgkey_installed

• journald and rsyslog together. The benchmark wants one logging system, not both. Rocky Linux runs journald and rsyslog together by default: journald keeps the structured system journal (persistent, in /var/log/journal), and rsyslog writes the traditional text logs (/var/log/messages, /var/log/secure, /var/log/cron) that many log shippers and audit procedures read. The image keeps both so neither kind of tooling loses its logs. If you standardise on one, for example the journal only, run sudo systemctl disable --now rsyslog on your instance and re-run Step 6.
• The Red Hat release key. In SCAP Security Guide 0.1.82, this rule's check for Rocky Linux 10 looks only for Red Hat's own package signing keys. Rocky Linux packages are signed with the Rocky Linux release key, which is installed, and dnf verifies every package against it. Installing Red Hat's key would not protect anything on a Rocky Linux system, so the image does not, and the rule stays as a reported fail. You can see the installed keys with:

rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE} %{SUMMARY}\n'

Expected output:

6fedfc85-682ae1a9 Release Engineering (Rocky Linux 10) <releng@rockylinux.org> public key 2ebba43f-6a7b0932 Release Engineering (Rocky Linux 10) <releng@rockylinux.org> public key 22b7fa33-682ae15f Release Engineering (Rocky Linux 10 Testing) <releng@rockylinux.org> public key

You can repeat the evaluation at any time with the same content and tailoring. It takes about a minute:

sudo oscap xccdf eval \
  --tailoring-file /usr/share/doc/sac/cis-l1-tailoring.xml \
  --profile xccdf_co.sac_profile_cis-l1_ec2_single \
  --results /tmp/cis-check-results.xml --report /tmp/cis-check-report.html \
  /usr/share/xml/scap/ssg/content/ssg-rl10-ds.xml > /tmp/cis-check.log 2>&1 echo "oscap exit code: $? (2 = at least one rule did not pass)"
sudo python3 -c "import re,collections; c=collections.Counter(re.findall(r'<result>(\w+)</result>', open('/tmp/cis-check-results.xml').read())); s=sum(c[k] for k in ('pass','fail','error','unknown')); print(dict(sorted(c.items()))); print('pass rate: %.1f%%' % (100.0*c['pass']/s))"

Expected output:

oscap exit code: 2 (2 = at least one rule did not pass) {'fail': 2, 'notapplicable': 31, 'notselected': 756, 'pass': 284} pass rate: 99.3%

Your own report is at /tmp/cis-check-report.html. The content file is ssg-rl10-ds.xml, the Rocky Linux 10 data stream; the RHEL 10 data stream that the same package carries reports every rule as not applicable on Rocky Linux. As you install software and change settings, re-run this to see how your changes affect the result.

curl -s -o /dev/null -w 'IMDSv1 request without a token: HTTP %{http_code}\n' http://169.254.169.254/latest/meta-data/instance-id
TOKEN=$(curl -s -X PUT -H 'X-aws-ec2-metadata-token-ttl-seconds: 60' http://169.254.169.254/latest/api/token)
curl -s -H "X-aws-ec2-metadata-token: $TOKEN" -w '\n' http://169.254.169.254/latest/meta-data/placement/region

Expected output (your Region may differ):

IMDSv1 request without a token: HTTP 401 us-east-1

A request without a session token is refused with HTTP 401, and the same request with a token works. Scripts and SDKs on the instance must use IMDSv2; every current AWS SDK and the AWS CLI do this automatically.

sudo firewall-cmd --state sudo firewall-cmd --list-all sudo ss -tlnp

Expected output:

running public (default, active) target: default ingress-priority: 0 egress-priority: 0 icmp-block-inversion: no interfaces: ens5 sources: services: dhcpv6-client ssh ports: protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=973,fd=7)) LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=973,fd=8))

• Only sshd listens, on port 22. Nothing else on the image opens a TCP port.
• The public zone allows ssh and dhcpv6-client (replies to the instance's IPv6 DHCP client, which is how an instance in an IPv6-enabled subnet gets its address). The Rocky Linux default cockpit service is removed from the zone; Cockpit is not installed.
• The loopback interface sits in firewalld's trusted zone, with rules that drop traffic claiming a loopback source from anywhere else (a CIS requirement).
• The network interface name (ens5 here) depends on the instance type.

Opening a port for your own service takes two steps: allow it in the instance's security group, and allow it in firewalld. For example, for a web server on 443, run on the instance:

sudo firewall-cmd --permanent --add-service=https sudo firewall-cmd --reload

If a port is open in the security group but not in firewalld (or the other way round), the traffic will not arrive.

systemctl is-active chronyd amazon-ssm-agent chronyc -n sources

Expected output (the pool servers and timings vary):

active active MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- 134.215.155.177 2 6 77 16 +1086us[+1087us] +/- 27ms ^- 173.71.69.149 1 6 157 14 -467us[ -467us] +/- 5190us ^- 144.202.41.38 2 6 77 16 +590us[ +594us] +/- 30ms ^- 217.180.231.4 1 6 77 17 -1209us[-1205us] +/- 16ms ^* 169.254.169.123 3 4 377 0 +5027ns[+5439ns] +/- 640us

The ^* marks the source chrony is using: 169.254.169.123, the Amazon Time Sync Service. It is reachable from every instance without internet access, so time stays correct in a private subnet too. The public Rocky Linux pool servers are fallbacks.

The AWS Systems Manager agent is installed from Amazon's own package at its current release (3.3.5390.0 on this build). It is not in the Rocky Linux repositories, so dnf does not update it; Systems Manager can keep it current for you (the AWS-UpdateSSMAgent document, or the Auto update SSM Agent setting in Fleet Manager).

The image is fully patched at build time. Check what is pending now:

sudo dnf -q check-update --refresh echo "dnf check-update exit code: $? (0 = nothing to update, 100 = updates available)" grep -E '^(upgrade_type|apply_updates)' /etc/dnf/automatic.conf systemctl is-enabled dnf-automatic.timer uname -r

Expected output on an instance launched soon after the image was built (later launches list the updates released since, with exit code 100):

dnf check-update exit code: 0 (0 = nothing to update, 100 = updates available) upgrade_type = security apply_updates = yes enabled 6.12.0-211.66.1.el10_2.x86_64

dnf-automatic runs daily (06:00, with a random delay of up to an hour) and installs security updates automatically. To update everything now, run:

sudo dnf -y upgrade

Reboot if a new kernel was installed:

sudo systemctl reboot

getenforce
sudo passwd -S root
sudo sshd -T | grep -E '^(permitrootlogin|passwordauthentication|pubkeyauthentication|maxauthtries|clientaliveinterval|banner) ' cat /etc/issue.net

Expected output:

Enforcing root L 2025-11-16 0 99999 7 -1 maxauthtries 4 clientaliveinterval 300 permitrootlogin no pubkeyauthentication yes passwordauthentication no banner /etc/issue.net Authorized users only. All activity may be monitored and reported.

• Enforcing means SELinux is on and enforcing the targeted policy. Keep it on; if your own software is denied, check sudo ausearch -m avc -ts recent rather than disabling SELinux.
• L in the second field means the root account is locked.
• maxauthtries 4 and clientaliveinterval 300 come from the CIS profile: SSH allows four authentication attempts per connection and checks idle sessions every five minutes.
• The banner text is shown before login.

EC2 Serial Console and recovery. No account on this image has a password, so the serial console cannot log in until you set one. If you want serial console access, set a password for your own user on your running instance (the password is yours and is not on the image):

sudo passwd rocky

df -hT /
sudo grep -E 'cc_growpart.*(resized|NOCHANGE)' /var/log/cloud-init.log | tail -1 swapon --noheadings --show | wc -l sudo grep -h aide /etc/crontab

Expected output with the default 11 GiB root volume (on a larger volume, Size is larger and the cloud-init line says resized):

Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p4 xfs 9.4G 1.7G 7.8G 18% / 2026-10-20 00:43:42,954 - cc_growpart.py[DEBUG]: '/' NOCHANGE: no change necessary (/dev/nvme0n1, 4) 0 05 4 * * * root /usr/sbin/aide --check

• Disk layout. The root filesystem is XFS on partition 4 of the root volume; /boot (XFS) and /boot/efi are separate small partitions.
• Disk growth. cloud-init grows the root partition and filesystem to the volume size on first boot. To grow later, increase the EBS volume size in the console or with aws ec2 modify-volume, then run sudo growpart /dev/nvme0n1 4 && sudo xfs_growfs / (or reboot).
• Swap. The image has no swap. Add a swap file yourself if your workload needs one.
• AIDE. The file integrity database is built from the image's own files, and the CIS profile schedules aide --check daily at 04:05 from /etc/crontab.

The instance uses the standard Rocky Linux 10 repositories (BaseOS, AppStream and Extras):

sudo dnf -q list --available nginx

Expected output (the version changes over time):

Available Packages nginx.x86_64 2:1.26.3-6.el10_2.7 appstream

Install and start software in the usual way, for example sudo dnf -y install nginx then sudo systemctl enable --now nginx, and open its port in the security group and firewalld (Step 8). The AWS CLI is not on the image; install the current version from AWS (the AWS CLI install guide) if you need it.

To add another administrator, create the account, add it to the wheel group and give it an SSH key:

sudo useradd -m -G wheel alice
sudo install -d -m 700 -o alice -g alice /home/alice/.ssh echo "ssh-ed25519 AAAA... alice@laptop" | sudo tee /home/alice/.ssh/authorized_keys
sudo chown alice:alice /home/alice/.ssh/authorized_keys && sudo chmod 600 /home/alice/.ssh/authorized_keys
sudo restorecon -R /home/alice/.ssh

Because SSH is key-only, a new account needs its key in authorized_keys (and restorecon gives the file the SELinux label sshd expects). The new account has no password, so sudo cannot authenticate it until you give it one with sudo passwd alice. SSH stays key-only; the password is used by sudo. (Password-free sudo is granted only to rocky, created by cloud-init, and to ssm-user, which the Systems Manager agent creates the first time you open a Session Manager session.)