This is a repackaged open source software product wherein additional charges apply for a hardened, AWS-optimized image with verification reports and maintenance. This AMI delivers PyTorch 2.12 with CUDA 13.0 in an isolated virtual environment, on an Ubuntu 24.04 LTS base tuned for EC2 by Easycloud-with a provenance evidence pack and SBOM.
This is a repackaged open source software product wherein additional charges apply for a hardened, AWS-optimized image with verifiable provenance evidence and maintenance. PyTorch 2.12 with CUDA 13.0 runs on an Ubuntu 24.04 LTS base tuned for Amazon EC2, with a documented set of security settings applied on top and a complete provenance evidence pack including a Software Bill of Materials (SBOM).
Value-Added Features
PyTorch 2.12 Deployment:
A Matched GPU Stack: Driver, CUDA runtime, cuDNN, NCCL and the framework build are pinned to a combination known to work together, so a first login goes straight to training or serving instead of debugging a version mismatch.
Isolated Virtual Environment: The whole stack lives in a self-contained Python 3.13 virtual environment at /opt/pytorch, leaving the system Python clean and untouched.
Notebook and Serving Ready: JupyterLab, TorchServe and tritonclient are preinstalled, and Docker with the NVIDIA Container Toolkit plus the EFA and NCCL OFI libraries cover containerized and multi-node work.
Comprehensive Evidence Pack:
Every AMI carries an 8-file provenance evidence pack under /opt/optimization-report/:
Tuning_Parameters.txt: Every tuning change, shown against its base-image value, with the reasoning and how to reverse it.
Security_Parameters.txt: All 31 security settings in the same format; the 10 already at the wanted value are marked unchanged rather than presented as improvements.
package_changes.txt: Packages upgraded, installed and removed versus the base image.
sbom.spdx.json: Software Bill of Materials in SPDX format, generated from the dpkg database.
cve_scan.txt / cve_scan_full.txt.gz: Vulnerability scan grouped by whether an upstream fix exists, with the kernel pinning explained.
key_files.sha256: SHA-256 checksums of all 7 files this image changed, so the delivered state can be verified in one command.
README.txt: Index of artifact contents and operational guidance.
Security & Attack Surface:
Kernel Network Hardening: 19 network-related kernel parameters are fixed in /etc/sysctl.d/99-security.conf: ICMP redirects are neither accepted nor sent, source-routed packets are rejected, and the rest are pinned at safe values so they cannot drift.
Unused Kernel Modules Disabled: 12 rarely used filesystem and network protocol modules are blocked from loading. No NVIDIA, EFA or container module is affected.
SSH Login Window Tightened: LoginGraceTime is reduced from 120 to 60 seconds. Root login policy, authentication retries and forwarding are left as the base image ships them.
No Outstanding Upstream Fixes: Every package outside the kernel pin was upgraded to the newest version its distribution offers, including updates Ubuntu was still phasing in. The scan reports zero findings with a fix available and not installed.
GPU Stack and Framework Left Intact:
Nothing Touches the Stack: The NVIDIA driver, the CUDA runtime and the PyTorch virtual environment are not modified. After the tuning is applied and the instance reboots, nvidia-smi reports the same driver, torch.cuda.is_available() returns true, a GPU tensor operation runs, and the kernel command line is byte for byte identical to the base image - all verified on a GPU instance.
Version Pinning Respected: The kernel is held at a fixed version because the driver is built against it. That pinning predates this release and is documented in the evidence pack rather than silently overridden.
AWS Network & Kernel Tuning:
Network Stack: TCP BBR congestion control with fair queueing, increased connection backlogs, raised socket buffer ceilings, and MTU probing enabled. Ceilings are only ever raised, never lowered.
System Tuning: tuned daemon active with an aws-optimized profile whose bootloader section is deliberately empty, so the network interface keeps its original name after a reboot.
Reliability: The systemd journal is capped at 200 MB so logs cannot fill the root filesystem.
Maintenance Specifications: Rebuilt and updated bi-weekly to monthly incorporating upstream Ubuntu 24.04 security updates, with artifact documentation refreshed per release.
About PyTorch
The most widely used open-source deep learning framework, here built for CUDA 13.0 and paired with torchvision, torchaudio and Triton, plus cuDNN and NCCL for accelerated and multi-GPU work. It underpins training and inference pipelines across research and production.
About Ubuntu 24.04 LTS
The most widely deployed Linux distribution in the cloud, built on the Debian foundation, with a five-year maintenance window for LTS releases and broad compatibility across AI and container tooling.
Highlights
PyTorch 2.12 on an AWS-Optimized Ubuntu 24.04 Base: 19 security-related kernel parameters, 12 blocked modules and a tightened SSH login window applied on top, with the driver, CUDA runtime, PyTorch environment and kernel command line left untouched.
Verifiable Evidence Pack and SBOM: An 8-file evidence pack ships inside the image, with an SPDX Software Bill of Materials, a CVE scan grouped by upstream fix availability, a package delta report, and SHA-256 checksums of every file the image changed.
PyTorch 2.12: Best-practice deployment. Driver, CUDA, cuDNN, NCCL and the framework build are pinned to a matched combination in a self-contained environment at /opt/pytorch, with JupyterLab and TorchServe preinstalled.
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 by the hour for the software running on your chosen Amazon EC2 instance type. Each dimension maps to one instance type, so pricing scales with the compute size and family you pick. Options span general-purpose (m, t), compute-optimized (c), memory-optimized (r, x, z), storage-optimized (i, d), accelerated GPU and inference (g, p, inf, dl, vt, f), and high-performance computing (hpc) families. Sizes range from nano and micro up to 48xlarge, plus bare-metal instances. Larger instances and specialized families carry higher hourly rates. You run only what you need and stop billing by stopping the instance.
Top-of-mind questions for buyers
What does one hourly unit cover, and what runs on the instance?
Each unit is one running Amazon EC2 instance of the type you select, billed per hour. The software is a security-hardened Ubuntu 24.04 image with PyTorch 2.12 preinstalled. Hardening follows recognized benchmarks to reduce the system's attack surface. You pay the software rate on top of standard AWS infrastructure charges.
Am I charged when I stop or pause the instance?
The software rate meters running time only. When you stop the instance, the hourly software charge stops. Stopped instances may still incur underlying AWS storage fees for attached volumes, but no software charge accrues while the instance is not running. Restarting the instance resumes the hourly charge.
How does my bill change if I move to a larger instance type?
Each instance type maps to its own hourly software rate. Moving to a larger size or a specialized family, such as GPU (g, p), inference (inf), or high-performance computing (hpc), changes the rate you pay per hour. You are billed at the rate for whichever type is running at the time.
www.easyclouds.io
Helpful?
Vendor refund policy
No refunds. Cancel anytime.
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
Latest Updates
Additional details
Usage instructions
Connection Methods
Once launched, SSH into the instance. The default username is 'ubuntu'. You can switch to the root user environment by running: sudo su -
This product must be launched on a GPU-backed instance type (G4dn, G5, G6, P4, P5, or P6 family). On a CPU-only instance type such as t3 the driver has no device to bind to and torch.cuda.is_available() will return false.
GPU Libraries: CUDA 13.0 runtime, cuDNN 9.20, and NCCL 2.29, all installed inside the virtual environment
Included Tooling: JupyterLab 4.6, TorchServe 0.12, tritonclient, SciPy, Pillow
Containers: Docker 29 with the NVIDIA Container Toolkit 1.19
Fabric: EFA with libfabric-aws 2.4.0 and the NCCL OFI plugin 1.18 for multi-node training
System Python 3.12 is kept clean and does not contain PyTorch
Note: there is no system-wide CUDA installation under /usr/local. The CUDA runtime is provided inside the /opt/pytorch environment, which is what PyTorch uses. If you need a system CUDA Toolkit with nvcc for compiling custom CUDA extensions, use our GPU Base CUDA AMI instead.
Usage Instructions
Launch on a GPU instance type. Recommended: g5.xlarge (A10G, 24 GB GPU memory) for single-GPU training, fine-tuning, and inference, or a larger g6, p4, p5, or p6 instance for multi-GPU work. Root volume is 30 GB with about 7.8 GB used by the environment; increase it at launch if you plan to store datasets or checkpoints.
SSH in as 'ubuntu' and activate the PyTorch environment (the login banner also shows this): source /opt/pytorch/bin/activate
Verify GPU access: python -c 'import torch; print(torch.version, torch.cuda.is_available(), torch.cuda.get_device_name(0))'
Expect the PyTorch version, True, and your GPU model. You can also check the driver level with: nvidia-smi
Start JupyterLab for interactive work. With the environment activated, run: jupyter lab --ip 0.0.0.0 --port 8888
Then open http://<YOUR_IP>:8888 and paste the access token printed in the terminal. Bind to a private address or use an SSH tunnel if the notebook should not be reachable from the internet.
Serve models with TorchServe. With the environment activated, run torchserve against your model archive; the inference API listens on port 8080 and the management API on port 8081.
Run GPU containers when you prefer your own image: sudo docker run --rm --gpus all <your-image>
For multi-node distributed training, the EFA stack and the NCCL OFI plugin are already installed; place your instances in the same cluster placement group and use EFA-capable instance types.
Manage services with systemctl start/stop/restart/status. JupyterLab and TorchServe are not enabled as services by default - you start them on demand from the activated environment as shown above.
Firewall Configuration
SSH (Port 22): Required for administration, activating the PyTorch environment, and running training or inference jobs.
TorchServe Inference API (Port 8080): Serves model predictions once you start TorchServe; closed until you do.
TorchServe Management API (Port 8081): Registers, scales, and unregisters models in a running TorchServe instance.
JupyterLab (Port 8888): Interactive notebook interface, available once you start JupyterLab manually.
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.
This product has charges associated with it for Hanwei's integration of TensorFlow 2.21, PyTorch 2.5.1, CUDA 12.6, cuDNN 9.x, NVIDIA driver 595, Python 3.12, Jupyter, and scientific libraries on Ubuntu 24.04 LTS, plus GPU configuration and testing for NVIDIA T4 on g4dn.
The solution goes beyond compliance by offering a Ubuntu server with comprehensive security hardening by default, covering everything from applications to the Linux kernel. With VED threat mitigation, you can rest assured that your digital assets are protected against advanced threats.
This product has charges associated with it for CIS Level 1 hardening, pre-configured compliance (PCI DSS, NIST), firewall policies, Nagios monitoring, Wazuh SIEM agent, and seller support.
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.