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 on the listing page, then Launch from Website (or EC2 console) choosing a current-generation x86-64 instance (4 vCPU+; pricing floor) and your SSH key pair.
Expected result Instance reaches 2/2 status checks. - Allow inbound 80/443 in the security group (SSH 22 restricted to your IP).
Expected result curl http://<public-ip>/ returns the NGINX welcome page.
Google Cloud
- Deploy from the Marketplace listing into your project (n2-standard-4 or larger), or use the listing's deployment package.
Expected result VM is RUNNING; the deployment's firewall rules show 80/443 allowed to the network tag. - Browse to http://<external-ip>/.
Expected result NGINX welcome page renders.
Validate
curl -fsS http://127.0.0.1/ (returns the default page)
First boot: Service is enabled at build; nginx serves immediately on first boot. No credential generation.
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