HAProxy (Hardened) — documentation & support card

At a glance

Type	Hardened VM image
Upstream / license	HAProxy (GPL-2.0-or-later (with LGPL components)) — see licenses
Version	HAProxy 2.8 (distro packages on Ubuntu 24.04). Current builds: release notes.
Architecture	x86-64
Sizing	Any current-generation instance with ≥ 4 vCPU (pay-as-you-go floor); 8 vCPU recommended for production.

Marketplaces

• Google Cloud Marketplace — SV package staged; submission = operator gate (base: Ubuntu 24.04 LTS)
• AWS Marketplace — view listing (base: Amazon Linux 2023)

Network ports

Port	Purpose	State
22	SSH (key-only)	default-open
80/443	Frontends you configure in haproxy.cfg	default-open (firewall) — no listener until you configure one
8404	Stats endpoint — bound to 127.0.0.1	optional (reach via SSH/IAP tunnel)

"customer-must-open" means a cloud firewall rule and, where noted, an in-image configuration change — both deliberate. Closed by default is the design.

Access & credentials

No shared or default credentials are included in this image. Access uses the SSH key you supply at launch; any application credential is generated uniquely on your instance at first boot and stored only there — we never know it.

Log in: SSH with your launch key.

This product has no application credential of its own.

Data & dependencies

• Data locations: /etc/haproxy/haproxy.cfg (configuration is the product) — all data stays on your instance and volumes.
• Does any data leave your tenant? No. Telemetry: none. Our images contain no phone-home, no usage beacons, no license servers. The only parties that know you deployed our software are you and your cloud provider's billing system.
• We have no access to your deployment. Your instance runs in your tenancy under your IAM; remote access for a support session exists only if you explicitly grant it, and you can revoke it at any time.
• External dependencies at deploy/runtime: None — the image is fully self-contained at deploy time; no internet access is required to boot and run.

Operate

• First boot: Service enabled with the stats frontend on 127.0.0.1:8404; add your frontends/backends to haproxy.cfg.
• Update / patch: Replace with the newest image version, or `apt upgrade haproxy` in place. Config is a single file — carry haproxy.cfg forward.
• Backup / restore: Back up /etc/haproxy/haproxy.cfg (that's the whole state).
• Uninstall: delete the VM/deployment and its volumes — nothing else persists, and software billing stops with the instance under your cloud's marketplace terms.
• Logs: journalctl -u haproxy -f (rsyslog target configurable)
• Health check: curl -fsS http://127.0.0.1:8404/stats (on the instance) — the stats page

Known limitations

Ships with no user frontends — deliberately. Your first config change IS the deployment step.

Support

Email support@dcassociatesgroup.com — first response within 1 business day (US Eastern), most tickets same-day. To escalate an open ticket, reply "ESCALATE"; it is reviewed by the founder within 1 business day. Security reports: vulnerability disclosure.

Privacy: policy · Terms: terms · Security practices: security & trust · Vulnerability reports: disclosure policy