This is a repackaged open source software product wherein additional charges apply for security hardening, optimization, and pre-integration of the Rust toolchain provided by Hanwei. SELinux is enforcing, SSH is hardened and key-only, auditd is active, kernel and resource limits are tuned for EC2, and rustc, cargo and clippy are preinstalled.
Charges for this image cover the security hardening, optimization, and pre-integration work Hanwei performs on top of the upstream Rust and CentOS Stream 9 projects. The toolchain is installed during the image build and is on PATH at first boot, while the operating system underneath it is configured to a fixed hardened and tuned baseline and validated on EC2 before publication. A subscriber launches the instance and can compile immediately, with no toolchain installation, no hardening and no kernel tuning work to perform.
What Hanwei Adds to Upstream Rust
Toolchain installed at build time: rustc and cargo are installed system-wide and present on PATH, removing the download-and-install step that would otherwise run after every launch. The current version ships rustc 1.97.
Ecosystem tooling and build dependencies preinstalled: clippy and rustfmt are available alongside rustc and cargo, and gcc, pkgconf and the OpenSSL development headers are present so that crates requiring native linkage compile without further setup.
Tuning baseline applied identically across the catalogue: the file descriptor limit goes from 1024 to 65536 and the memory-map ceiling from 65530 to 262144; the device receive backlog goes from 1000 to 16384 and the TCP SYN backlog from 128 to 8192, so bursts queue instead of being dropped; socket buffer maxima reach 16 MB for larger autotuned windows; connections keep their congestion window across idle periods; and the journal is capped at 500 MB. The profile raises ceilings only and does not alter protocol semantics or application behaviour.
Applied hardening beyond the distribution default: SSH is limited to a vetted cipher, key exchange and MAC list, X11 forwarding is off, the login grace period is shortened and verbose authentication logging is on; auditd runs a base rule set for privileged command execution; the kernel drops ICMP redirects on IPv4 and IPv6, logs martian packets, filters reverse paths in loose mode, restricts dmesg, disables setuid core dumps and turns off sysrq.
AWS operational integration: the SSM Agent is installed and enabled for Session Manager and Patch Manager without an inbound SSH rule; chrony points at the Amazon Time Sync Service; and the root filesystem extends at boot when the volume exceeds the image default.
Patch level set at the build date: packages come from official upstream repositories at the newest level published when the image was built.
Repeatable build and EC2 validation: each version comes from the same build process and is launched and exercised on EC2 before release.
Access and Security Posture
SELinux runs in enforcing mode and auditd records activity against a base rule set.
Sign in as 'ec2-user' with the key pair selected at launch, then use 'sudo su -' for a root shell. Session Manager is available as an alternative that needs no inbound port.
Direct root login over SSH is disabled and password authentication is not accepted.
No authorized keys and no SSH private keys are embedded in the image.
Operational Impact on EC2
Launch-to-first-build time is reduced to a single boot cycle.
Every instance starts from an identical configuration, removing drift between development, staging and production hosts.
Network services need no per-host limit or backlog adjustment before handling load.
Clock accuracy comes from the Amazon Time Sync Service, which matters for log correlation and request signing.
Post-launch patching effort is lower because the package set is current at release.
Where This Image Fits
Build and CI hosts that compile Rust services and binaries.
Development instances for teams working on Rust codebases.
Cross-compilation, release-artifact and container build hosts.
Short-lived instances for benchmarking or dependency auditing.
About Rust and CentOS Stream 9
Rust is a systems programming language that provides memory safety without a garbage collector. Its ownership and borrowing rules are checked at compile time, which removes data races and use-after-free defects from safe code, and its binaries run with no runtime or virtual machine. Cargo, the bundled build tool and package manager, resolves dependencies from the crates.io registry and drives compilation, testing and release builds. It is commonly used for network services, command line tooling and the performance-sensitive parts of larger systems.
CentOS Stream 9 is a Linux distribution that tracks the development stream of Red Hat Enterprise Linux 9. Packages land in CentOS Stream before they appear in a RHEL minor release, so it stays close to the RHEL package set and toolchain while remaining freely redistributable. It uses dnf, systemd and SELinux, which makes it a predictable base for server workloads that need RHEL compatibility.
Highlights
WHAT IS PACKAGED - This image provides rustc, cargo, clippy and rustfmt installed during the image build and on PATH at first boot, together with gcc, pkgconf and the OpenSSL development headers that crates requiring native linkage need. The current version ships rustc 1.97.
HOW THE BASELINE IS HARDENED AND TUNED - SELinux enforcing, root login locked and SSH limited to key-based authentication with a vetted cipher, key exchange and MAC list. auditd runs a base rule set for privileged commands. The kernel drops ICMP redirects, logs martian packets and restricts dmesg. The file descriptor limit goes from 1024 to 65536 and the memory-map ceiling from 65530 to 262144; receive and SYN backlogs are enlarged and socket buffers reach 16 MB.
HOW IT FITS AWS OPERATIONS - The SSM Agent is installed and enabled, so instances can be managed through Session Manager and Patch Manager without an inbound SSH rule. chrony is pointed at the Amazon Time Sync Service, the root filesystem extends automatically when the volume exceeds the image default, and cloud-init handles user-data provisioning in launch templates and Auto Scaling groups.
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 EC2 instance type you run this software on. Each dimension matches a specific AWS instance size, so there are no software tiers or feature levels to choose between. The product itself stays the same; only the underlying compute changes. Smaller instances like t2.nano or t3.micro carry lower hourly rates, while larger memory, compute, storage, GPU, and bare-metal instances cost more per hour. You select the instance that fits your workload, and billing scales with how many hours you keep each instance running.
Top-of-mind questions for buyers
What does the hourly rate for each instance type actually pay for?
The rate covers the software license for running this hardened Rust build on CentOS Stream 9. You pay a separate AWS fee for the underlying compute. Each listed instance type sets one hourly software rate, matched to that instance's size and resource class.
Am I charged the hourly software fee when my instance is stopped?
The software fee meters running hours only. A stopped or terminated instance stops accruing the hourly software charge. Note that AWS may still bill underlying storage for a stopped instance, but that is separate from the software rate shown here.
Does the software itself change between a small t3.micro and a large bare-metal instance?
No. The packaged software is the same across every instance type. The product bundles its required libraries, databases, and runtimes so it runs the same way on any size. Only the hourly rate and the compute capacity differ between instance choices.
www.proimage.cloud
Helpful?
Vendor refund policy
no refunds
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
Updated to the latest
Additional details
Usage instructions
ssh as user 'ec2-user' to the running instance and use sudo to run commands requiring root access.
Use "sudo su - root" to switch to root.
OS: CentOS Stream 9.
Use the command 'rustc --version' to check the rust version.
Rust Version: rustc 1.97.0.
Please allow SSH port 22 to limited IPs for access.
Support
Vendor support
If you encounter problems in the process of using the system, please feel free to contact us by email prosupport@hanweie.com, 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.
rustc 1.97, cargo, clippy, and rustfmt installed system-wide and present on PATH at first boot, with gcc, pkgconf, and OpenSSL development headers for native linkage compilation
Operating System Hardening
SELinux enforcing mode, SSH key-only authentication with vetted cipher and key exchange algorithms, auditd active with base rule set for privileged command execution, kernel ICMP redirect dropping, and dmesg access restrictions
System Resource Tuning
File descriptor limit increased to 65536, memory-map ceiling raised to 262144, device receive backlog set to 16384, TCP SYN backlog set to 8192, and socket buffer maxima configured to 16 MB
AWS Integration
SSM Agent installed and enabled for Session Manager and Patch Manager access, chrony configured to Amazon Time Sync Service, and automatic root filesystem extension when volume exceeds image default
Build-Time Optimization
Toolchain and dependencies preinstalled during image build with identical configuration across all instances, eliminating post-launch installation and tuning steps
Operating System Distribution
CentOS Stream 9 based Linux distribution with enterprise-class functionality compatible with Red Hat Enterprise Linux
Remote Desktop Access
RDP based remote desktop environment for remote connectivity and management
Pre-installed Development Tools
Visual Studio Code integrated development environment included for software development
Command Shell Environment
Fish shell with command auto-suggestion and completion capabilities
Web Browser
Firefox browser included for web browsing and internet access
Security Hardening Standard
CIS Level 1 benchmark hardening validated via OpenSCAP with alignment to PCI DSS, FedRAMP, NIST, FISMA, and DoD Cloud Computing SRG compliance frameworks
System Monitoring and Infrastructure Visibility
Nagios Core configured for infrastructure monitoring including CPU, memory, disk, and network metrics
Security Information and Event Management
Wazuh Agent providing SIEM capabilities and intrusion detection functionality
Host-based Firewall Configuration
Pre-configured UFW firewall rules with robust password policies via libpam-pwquality and auditd system auditing
Malware Detection and Prevention
ClamAV integrated for malware scanning and threat detection
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.