Launch Rocky Linux 9 with STIG-aligned partitions applied at install - a layout that cannot be retrofitted after launch, avoiding costly rebuilds when auditors flag disk-layout findings. StigReady Base adds EC2 hardening (v0.1.0), SBOM and CVE metadata per build, and Nitro boot verification.
Why StigReady Base for Rocky Linux 9:
STIG-required disk partition layouts must be in place at install time. Standard and many CIS-hardened AMIs lack that structure, leaving permanent findings on your PoA&M or forcing a full rebuild. StigReady Base delivers the layout and cloud baseline on official media so instances are ready for your scanning workflow.
Who this is for:
Platform and DevSecOps teams building regulated workloads on AWS - use this AMI as a golden image foundation before your own profiles or a scored StigReady Applied listing.
What you get (StigReady Base tier):
Separate mounts for /home, /tmp, /var, /var/log, /var/log/audit, /var/tmp (applied at install; not retrofittable after launch)
EC2 cloud baseline: IMDSv2 required, no pre-installed SSH authorized_keys, PermitRootLogin and password SSH disabled, host keys regenerated on first boot
Built from official OS install media; patched at build time
Boot-verified on real AWS EC2 Nitro before release
Per-version SBOM and CVE scan metadata (public catalog; see Support)
Not a fully remediated DISA STIG or CIS score - see StigReady Applied for OpenSCAP-scored remediation
How this differs:
Standard marketplace AMIs ship without STIG-aligned partitions. Post-launch STIG remediation cannot fix disk layout. StigReady Base addresses layout and EC2 hardening at the image; StigReady Applied adds scored ansible-lockdown remediation.
Getting started:
Subscribe and launch on a Nitro instance with your SSH key.
Connect as ec2-user; restrict security group TCP/22 to trusted IPs.
Not affiliated with or endorsed by DISA, DoD, NIST, CIS, Red Hat, or Canonical. All trademarks are the property of their respective owners.
Highlights
Closes install-time partition gaps: STIG-aligned mounts applied at image build, not retrofittable after launch - avoids rebuilds for layout-related findings
Per-build SBOM and CVE metadata in the public product catalog - less manual artifact gathering for assessors
EC2 hardening from first boot: IMDSv2 required, no baked-in SSH keys; boot-verified on AWS Nitro before release
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
You pay an hourly software fee tied to the EC2 instance size you run. Pricing spans 17 instance types across four families: t3 for general-purpose burstable workloads, m5 and m6i for balanced compute and memory, c5 for compute-focused work, and r5 for memory-heavy work. Within each family, larger sizes (large through 2xlarge or 4xlarge) carry a higher hourly rate. You choose the instance that fits your workload, and the fee scales with that choice. AWS bills your underlying EC2 usage separately from this software fee.
Top-of-mind questions for buyers
What do I get in this base image for the hourly software fee?
You get a Rocky Linux 9 image built from the official ISO, patched, and boot-tested on EC2 Nitro. It carries a STIG partition layout with separate hardened mounts and SSH hardening. You bring your own compliance profiles, Ansible, and tooling to apply on top.
Am I charged the software fee when my EC2 instance is stopped?
The hourly software fee meters running instance time. A fully stopped instance does not accrue the software charge. Stopped instances may still incur AWS storage fees for attached volumes, but those are billed by AWS separately from this software fee.
How does the software fee combine with my AWS EC2 charges?
Two charges apply at once. This listing's hourly software fee is tied to the instance size you run. AWS bills your underlying EC2 compute and storage usage separately. Both appear on your AWS invoice. The software fee is added on top of your normal EC2 costs.
stigready.com
Helpful?
Vendor refund policy
No refunds except as required by law.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
StigReady base Rocky Linux 9 v0.1.0
Additional details
Usage instructions
Subscribe in AWS Marketplace, then launch in EC2 with your SSH key pair. Connect via SSH as ec2-user. Open TCP port 22 only to trusted IP ranges in your security group (avoid 0.0.0.0/0 in production). This AMI requires IMDSv2-compatible instance metadata settings at launch. Documentation: https://stigready.com. Per-build SBOM and CVE scan metadata is listed in the public catalog at https://stigready.com/catalog.json (full factory evidence bundles are not web-public).
Listing copy revision: 2026-07-30a. Documentation and deployment guides: https://stigready.com. Email support@stigready.com for AMI build issues, STIG partition layout questions, and per-version SBOM/CVE metadata (public catalog: https://stigready.com/catalog.json). Scope covers the StigReady Base AMI image, not application-layer STIG tailoring or third-party scanner configuration. Subscription or refund questions: same email or AWS Marketplace buyer support.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
StigReady Base for AlmaLinux 10: STIG-aligned disk layout and EC2 cloud hardening on official media (v0.1.0), boot-verified on AWS Nitro. Published SBOM and CVE scan per build. Foundation before CIS/STIG remediation or StigReady Applied.
Launch RHEL 10 with STIG-aligned partitions applied at install - a layout that cannot be retrofitted after launch, avoiding costly rebuilds when auditors flag disk-layout findings. StigReady Base adds EC2 hardening (v0.1.1), SBOM and CVE metadata per build, and Nitro boot verification.
Launch RHEL 9 with STIG-aligned partitions applied at install - a layout that cannot be retrofitted after launch, avoiding costly rebuilds when auditors flag disk-layout findings. StigReady Base adds EC2 hardening (v0.1.0), SBOM and CVE metadata per build, and Nitro boot verification.
Launch RHEL 8 with STIG-aligned partitions applied at install - a layout that cannot be retrofitted after launch, avoiding costly rebuilds when auditors flag disk-layout findings. StigReady Base adds EC2 hardening (v0.1.0), SBOM and CVE metadata per build, and Nitro boot verification.
Launch RHEL 8 with STIG-aligned partitions applied at install - a layout that cannot be retrofitted after launch, avoiding costly rebuilds when auditors flag disk-layout findings. StigReady Base adds EC2 hardening (v0.1.1), SBOM and CVE metadata per build, and Nitro boot verification.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.