This is a repackaged open source software product wherein additional charges apply for security hardening, optimization, and pre-integration of the MySQL 8.0 stack provided by Hanwei. MySQL 8.0 is initialized at build time and starts with the instance, on a base running SELinux enforcing with root login locked and key-only SSH access.
Charges for this image cover the security hardening, optimization, and pre-integration work Hanwei performs on top of the upstream MySQL 8.0 and CentOS Stream 9 projects. MySQL 8.0 is installed from the distribution's own module stream, the data directory is initialized and the service is enabled, so the server is listening when the instance finishes booting. The operating system underneath carries the same hardened and tuned baseline used across this catalogue.
What Hanwei Adds to Upstream MySQL 8.0
Server installed and initialized at build time: packages come from the CentOS Stream 9 AppStream module, /var/lib/mysql is initialized and mysqld is enabled, so the server accepts local connections as soon as the instance boots.
Transparent huge pages disabled at boot: a oneshot unit sets them to never before the database starts, following the vendor's guidance. This is not the distribution default, where the tuned virtual-guest profile leaves them enabled.
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-usable-database 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
Application backends whose schema and client libraries are validated against the 8.0 series.
Development and test environments recreated frequently from an identical database configuration.
Content management and e-commerce platforms that expect a MySQL-compatible server.
Workloads that need to stay on 8.0 for compatibility while running on a maintained distribution.
About MySQL 8.0 and CentOS Stream 9
MySQL 8.0 introduced common table expressions, window functions, a transactional data dictionary and the caching_sha2_password authentication plugin, and it remains the version most widely assumed by application frameworks and hosting tooling. Packages in this image come from the CentOS Stream 9 module stream, which Red Hat maintains for the lifetime of the 9 platform.
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 MySQL 8.0 installed from the CentOS Stream 9 AppStream module, data directory initialized and the service enabled, with transparent huge pages disabled as the vendor documentation requires for InnoDB workloads.
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 a hardened MySQL 8.0 image running on CentOS Stream 9. Pricing is not tiered by features. Instead, each option maps to a specific AWS EC2 instance type, and every deployment includes the same software. Your hourly rate depends on the instance you pick. Smaller instances like t1.micro, t2, and t3 sizes suit light workloads. General-purpose (m-series), compute-optimized (c-series), memory-optimized (r- and x-series), storage (d- and i-series), and accelerated (g-, p-, inf-, trn-series) families scale up cost with capacity. You choose the instance that fits your workload.
Top-of-mind questions for buyers
What does one billing unit cover for this MySQL image?
Each unit is one hour of running one EC2 instance with the hardened MySQL 8.0 image on CentOS Stream 9. The rate you see for your chosen instance type applies to every hour that instance runs. Larger instance families bill at higher hourly rates because they provide more compute, memory, or storage.
Am I charged the software rate when my instance is stopped?
The hourly software charge applies only while the instance runs. Stopped or powered-off instances do not accrue the software fee. Note that AWS may still bill for underlying storage tied to a stopped instance, but the MySQL software meters running hours only.
Is this pay-as-you-go, or do I commit to a term upfront?
Billing is usage-based. You pay per instance-hour with no upfront commitment. Charges start when the instance runs and stop when it stops. This suits variable or short-term workloads, since you are billed only for the hours you actually use.
www.proimage.cloud
Helpful?
Vendor refund policy
no refund
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
Update to 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 - ' to switch to root.
OS: CentOS Stream 9
MySQL Version: 8.0.46 MySQL Community Server
Installation Information:
The MySQL installation user in the system: mysql
MySQL configuration file: /etc/my.cnf
MySQL Port: 3306
Local login method: mysql -uroot -p
To view the initial MySQL root user password, you can check the file located at '/root/mysql-password'.
Use the command 'sudo cat /root/mysql-password' to view the initial password for the MySQL root user.
Service Management:
To start/stop/status mysql Service: sudo systemctl start/stop/status mysqld
Please allow SSH port 22, mysql Port 3306 to limited IPs for access.
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.
This is a repackaged open source software product wherein additional charges apply for security hardening, optimization, and pre-integration of the MySQL 9.7 LTS stack provided by Hanwei. MySQL 9.7 LTS is initialized at build time and starts with the instance, on a base running SELinux enforcing with root login locked and key-only SSH access.
This is a repackaged open source software product wherein additional charges apply for baseline security hardening, kernel performance tuning, weekly automated patch integrations, versatile storage support (Standard & LVM), and pre-integrated AWS cloud utilities.
This is a repackaged open source software product wherein additional charges apply for baseline security hardening, kernel performance tuning, weekly automated patch integrations, versatile storage support (Standard & LVM), and pre-integrated AWS cloud utilities.
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.