PostgreSQL 16 (Hardened) — documentation & support card

At a glance

Type	Hardened VM image
Upstream / license	PostgreSQL (PostgreSQL License) — see licenses
Version	PostgreSQL 16 (distro packages on Ubuntu 24.04 for GCE; EL9 image on AWS). 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
5432	PostgreSQL — listens on localhost	customer-must-open (config + firewall)

"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, then `sudo -u postgres psql`.

The postgres superuser has no password; access is via the local postgres OS account.

sudo -u postgres psql

Rotation: Create application roles with your own passwords: CREATE ROLE app LOGIN PASSWORD '...';

Data & dependencies

• Data locations: /var/lib/postgresql/16/main (Ubuntu) — snapshot the volume for full-instance backup — 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: Cluster is initialized by the distro packages; service enabled. Ready when pg_isready succeeds (seconds after boot).
• Update / patch: Replace with the newest image version (monthly rebuild cadence), or `apt upgrade postgresql-16` / `dnf update` in place. Major-version upgrades via pg_upgrade — snapshot first.
• Backup / restore: pg_dumpall via `sudo -u postgres pg_dumpall > backup.sql`, or stop the service and snapshot the volume.
• 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: /var/log/postgresql/postgresql-16-main.log; `journalctl -u postgresql -f`
• Health check: sudo -u postgres pg_isready → 'accepting connections'

Known limitations

Single-node image. HA (replication/failover) is an architecture you build deliberately — ask support for the reference pattern.

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