Blog · 2026-07-30 · Hands-on

RHEL 9 Base + rhel9_stig

Launch StigReady RHEL 9 Base from AWS Marketplace, then apply the public StigForge role rhel9_stig with a pinned release tag.

Before you start

1. Subscribe and launch Base

  1. Open the StigReady seller page on AWS Marketplace.
  2. Choose StigReady RHEL 9 - Minimal STIG-Ready Base for your arch (x86_64 or arm64).
  3. Subscribe, then launch into your VPC with a key pair you control. Prefer a security group that allows SSH from your control host only.
  4. SSH as ec2-user (or use SSM Session Manager — the agent is preinstalled).
ssh -i your-key.pem ec2-user@<instance-ip>

Confirm the STIG mounts exist (lsblk, findmnt) before remediating — Base already laid them down at install.

2. Install the role (pinned tag)

On your Ansible control host:

# requirements.yml
roles:
  - src: https://github.com/stigready/rhel9-stig
    scm: git
    version: v0.2.4-private-review
    name: rhel9_stig
ansible-galaxy role install -r requirements.yml -p ./roles

Galaxy import (stigready.rhel9_stig) is the long-term install path once the namespace is listed; until then, GitHub + tag is the supported pin.

3. Run the playbook

# inventory.ini
[stig]
rhel9-base ansible_host=<instance-ip> ansible_user=ec2-user
# site.yml
- hosts: stig
  become: true
  roles:
    - role: rhel9_stig
ansible-playbook -i inventory.ini site.yml

Expect a reboot-friendly run: FIPS / crypto policy and auth changes may require a reboot before services settle. Plan a maintenance window.

4. Check published evidence

Factory-verified scores and artifacts for this tag live under the role repo:

Your live host score can differ from docker verify (cloud exceptions, packages, timing). Use OpenSCAP against the raw SSG stig profile when you need an auditor-facing number for this instance.

Related

Questions? contact@stigready.com