Prerequisites
- An account on the target cloud with permission to launch VM instances (no special IAM roles are required by this product unless stated below — IAM required: none).
- An SSH key pair registered in the target cloud (all access is key-only; password SSH is disabled).
- Instance size ≥ 4 vCPU (pricing floor; 8 vCPU recommended).
- No internet access or external dependency is required at deploy time — the image is self-contained.
AWS
- Subscribe and launch (4 vCPU+ recommended for production workloads; gp3 volume sized for your data).
Expected result Instance 2/2 checks; `sudo mysql -e 'SELECT VERSION()'` returns 8.4.x. - Remote access is OFF by default (3306 bound to 127.0.0.1). To enable: set bind-address in /etc/my.cnf to your VPC address, `systemctl restart mysqld`, create a non-root app user with a strong password, AND open 3306 in the security group to your app subnet only.
Expected result App connects from inside the VPC; 3306 remains unreachable from the internet.
Validate
sudo mysql -e 'SELECT 1' (first boot completes when /var/lib/mysql-firstboot.done exists)
First boot: A one-shot service (marker: /var/lib/mysql-firstboot.done) switches root to auth_socket and verifies the socket. Takes seconds; database is ready when the marker exists.
Secure it
- Restrict SSH (22) to your own IP range in the cloud firewall/security group.
- Open application ports only per the ports table — closed-by-default is deliberate.
- Volume encryption: use your cloud's native volume encryption (enabled by default on most accounts); the image adds no proprietary encryption layer.
Costs & quotas
Software is billed by the marketplace at the listed rate; infrastructure (VM, storage, egress) is billed
by your cloud at its standard rates. The recommended size fits default service quotas in most accounts —
if you scale out, review your cloud's quota console before launch.
Next: configuration · troubleshooting · security notes
DC Associates Group