Overview
This is a repackaged open source software product wherein additional charges apply for a pre-hardened, AWS-optimized image with verifiable compliance evidence and maintenance. NVIDIA CUDA runs on a Rocky Linux 9.8 base hardened following DISA STIG guidelines, tuned for Amazon EC2 workloads, and shipped with a complete OpenSCAP evidence pack and Software Bill of Materials (SBOM).
Value-Added Features
NVIDIA CUDA Deployment:
-
Complete GPU Toolchain: The full CUDA Toolkit is installed with nvcc and the GPU math, communication, and profiling libraries on PATH, paired with the NVIDIA open kernel module driver built through DKMS, so CUDA C++ code compiles out of the box.
-
Container and Fabric Stack Included: Docker CE with the NVIDIA Container Toolkit, NCCL and gdrcopy for GPU communication, the AWS EFA stack with libfabric, Open MPI, and the NCCL OFI plugin, plus DCGM and Fabric Manager.
-
Framework-Neutral by Design: A Python data stack (JupyterLab, NumPy, pandas, SciPy, boto3) and AWS CLI v2 are included, while cuDNN and the deep learning frameworks are intentionally left out, so you pick the framework and version yourself.
Hardened Operating System Base:
-
DISA STIG Alignment: 339 security controls applied to the Rocky Linux 9.8 base via the SCAP Security Guide, including auditd logging, SSH hardening, kernel command line and module blocklist restrictions, and strict password policy enforcement.
-
Fully Patched at Release: Zero packages with a pending update at build time, verified. The complete CVE scan ships inside the image.
-
Documented Exceptions: Every STIG rule not applied is itemized with a technical justification, so the delivered posture is auditable.
Comprehensive Evidence Pack:
Every AMI carries an OpenSCAP evidence pack generated against DISA STIG guidance, under /opt/hardening-report/:
- Base_Report.html: Pre-hardening scan report, the initial baseline.
- Tailored_Profile_Report.html: Post-hardening report against the tailored profile shipped in this image.
- Raw_STIG_Report.html: Post-hardening report against the unmodified baseline DISA STIG profile.
- Exceptions.txt: Itemized unapplied STIG rules with technical justifications (AWS compatibility, site-specific policies, CSP service conflicts).
- Tuning_Parameters.txt: Every tuning parameter applied on top of the hardening, each shown against its base-image value.
- compliance_mapping.csv: Rule-by-rule mapping to NIST SP 800-53 controls and DISA STIG identifiers with pass/fail statuses.
- package_changes.txt: Package delta against the minimal stock installation.
- sbom.spdx.json: Software Bill of Materials in SPDX format, generated from the RPM database.
- cve_scan.txt / cve_scan_full.txt.gz: Vulnerability scan reports categorizing CVEs by upstream patch availability.
- key_files.sha256: SHA-256 checksums of the key configuration files changed by the hardening, so the delivered state can be verified.
- README.txt: Index of artifact contents, operational guidelines, and configuration defaults.
Reliability Validation:
- Validation Testing: Functional verification on clean AMI launches through multi-round integration testing, covering the complete GPU software lifecycle with SELinux enforcing.
AWS Network & Kernel Tuning:
-
Network Stack: TCP BBR congestion control with fair queueing, increased connection backlogs, buffer adjustments, and MTU probing enabled.
-
System Tuning: Red Hat tuned daemon active with a custom cloud profile, transparent hugepages set to madvise, and modified memory/EBS writeback parameters.
-
EC2 Integration: NVMe I/O timeouts, Amazon Time Sync (chrony), IRQ balance daemon, and size-capped persistent journald logging.
Operational Tools:
- Preinstalled Tools: AWS SSM Session Manager enabled, CloudWatch Agent installed (disabled by default).
Maintenance:
- Maintenance Specifications: Rebuilt and updated bi-weekly to monthly incorporating upstream NVIDIA CUDA and Rocky Linux 9.8 security updates, with artifact documentation refreshed per release.
About NVIDIA CUDA
A framework-neutral GPU compute base in which the driver, the CUDA Toolkit, the container runtime, and the multi-node fabric libraries are assembled and verified together, so accelerated workloads run immediately instead of requiring hours of reconciling kernel modules and toolkit versions. It suits AI and HPC stacks built on CUDA, PyTorch, TensorFlow, Docker, and Kubernetes.
About Rocky Linux 9
Built directly from RHEL 9 source code for binary compatibility with the Red Hat 9 ecosystem, with predictable update cadences and a maintenance lifecycle through 2032. Any application compiled, certified, or documented for RHEL 9 runs without modification, and the platform is structurally aligned with AlmaLinux, CentOS Stream, and legacy CentOS deployments.
Highlights
- NVIDIA CUDA on a DISA STIG Hardened Base: 339 security controls applied to the Rocky Linux 9.8 foundation via the SCAP Security Guide, incorporating SSH hardening, kernel command line and module blocklists, and strict password policies out of the box.
- Verifiable Evidence Pack and SBOM: A 12-file OpenSCAP evidence pack ships inside the image, with before/after scan reports, itemized exceptions and justifications, NIST SP 800-53 mapping, CVE scan, and a complete SPDX Software Bill of Materials.
- NVIDIA CUDA: Best-practice deployment. Driver, toolkit, container runtime, and fabric stack verified together - on an EC2-tuned base with TCP BBR and Red Hat tuned cloud profiles, rebuilt bi-weekly to monthly with upstream security patches.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
g5.xlarge Recommended | $0.19 |
t2.micro | $0.03 |
t3.micro | $0.03 |
t2.nano | $0.03 |
t3.nano | $0.00 |
t3a.nano | $0.03 |
t1.micro | $0.03 |
t3a.micro | $0.03 |
m1.small | $0.04 |
t2.small | $0.04 |
Vendor refund policy
No refunds. Cancel anytime.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
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
Latest Updates
Additional details
Usage instructions
Connection Methods
Once launched, SSH into the instance. The default username is 'rocky'. You can switch to the root user environment by running: sudo su -
This product requires SSH; there is no web console or web UI. There are no default credentials - access is via your own EC2 key pair as user 'rocky'.
Requires a GPU instance type (g4dn / g5 / g6 / p3 / p4 / p5 and similar). Non-GPU instance types will not work.
Install Information
-
OS: Rocky Linux 9 (x86_64)
-
NVIDIA Driver: 595.71.05 (open kernel module, DKMS)
-
CUDA Toolkit: 13.2 installed at /usr/local/cuda-13.2, with /usr/local/cuda pointing to it
-
GPU Communication: NCCL 2.29 (with headers) and gdrcopy 2.5
-
Containers: Docker CE 29 with containerd 2.2 (buildx, compose) and NVIDIA Container Toolkit 1.19
-
Fabric and MPI: EFA 3.1.0 with libfabric-aws 2.4.0, Open MPI 5.0.9, and the NCCL OFI plugin 1.20 - preinstalled and ready on EFA-capable instance types
-
GPU Management: DCGM 4.6 and NVIDIA Fabric Manager (both installed, started on demand)
-
Python: 3.12 with JupyterLab, IPython, NumPy, pandas, SciPy, matplotlib, boto3; plus AWS CLI v2
-
Environment: CUDA paths are set system-wide via /etc/profile.d/cuda.sh and /etc/ld.so.conf.d/cuda.conf
-
Not included by design: cuDNN, PyTorch, and TensorFlow. This is a base layer - you install the framework stack you need.
-
No internet access is required to run this product - everything above is preinstalled. Outbound access is only needed if you pull container images or pip install frameworks yourself.
Usage Instructions
-
Launch on a GPU instance type. Recommended: g5.xlarge (A10G, 24 GB GPU memory); the image was verified on g4dn.xlarge. Non-GPU instance types will not work.
-
Allow about 4 minutes on first boot before the GPU is ready (measured 234 seconds from launch to the first successful nvidia-smi on g4dn.xlarge). This first-boot wait is normal, not a fault.
-
SSH in as 'rocky' and run the first command to confirm the GPU and driver: nvidia-smi
-
Verify GPU access from a container: docker run --rm --gpus all <image> nvidia-smi Replace <image> with an actual image, for example ubuntu:24.04. The 'rocky' user is in the docker group, so sudo is not required.
-
Compile CUDA code. nvcc is already on PATH: nvcc --version, then build with: nvcc -o myapp myapp.cu Build systems expecting CUDA_HOME resolve through /usr/local/cuda.
-
Install your own framework stack, for example: python3 -m venv ~/venv && source ~/venv/bin/activate && pip install torch Match the build to CUDA 13.x when the project offers CUDA-specific wheels.
-
Start JupyterLab on demand when you want a notebook interface: jupyter lab --ip=0.0.0.0 It is installed but not started automatically. If you use it, open its port in your Security Group and restrict it to trusted IP addresses.
-
Manage services with systemctl start/stop/restart/status. Docker and nvidia-persistenced are enabled and start at boot. GPU monitoring and Fabric Manager are installed but disabled by default: sudo systemctl start nvidia-dcgm && dcgmi discovery -l, and enable nvidia-fabricmanager on NVSwitch-equipped multi-GPU instance types.
-
The CUDA, Docker, and NVIDIA Container Toolkit repositories are shipped disabled so a routine dnf update cannot break the driver and DKMS pairing. To upgrade those components, re-enable the relevant repository explicitly with dnf --enablerepo. EPEL remains enabled.
Firewall Configuration
-
SSH (Port 22): Required - restrict to trusted IPs. This product requires SSH; there is no web console or web UI.
-
No application ports are opened by default. If you later start JupyterLab yourself, open its port and restrict it to trusted IPs as well.
-
Security Recommendation: For production environments, strictly limit access to these ports to trusted IP addresses only via cloud Security Groups or the local firewall.
Support
Vendor support
Should you encounter any issues while using the system, please do not hesitate to contact us via email at: support@easyclouds.io ,Thank you!
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.