ClickHouse (Hardened) — documentation & support card

At a glance

Type	Hardened VM image
Upstream / license	ClickHouse (Apache-2.0) — see licenses
Version	ClickHouse current stable from packages.clickhouse.com. 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

• AWS Marketplace — submission in progress (image verified 2026-07-21) (base: Amazon Linux 2023)

Network ports

Port	Purpose	State
22	SSH (key-only)	default-open
8123	HTTP interface — localhost	customer-must-open (config + firewall)
9000	Native protocol — 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 `clickhouse-client`.

The default user is local-only with no password (upstream default), which is safe precisely because the listeners are loopback-bound.

clickhouse-client   # on the instance

Rotation: Before any network exposure, create users with passwords/quotas in users.d/ — see configuration.

Data & dependencies

• Data locations: /var/lib/clickhouse — 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 at build; ready in seconds.
• Update / patch: Replace with the newest image version, or `dnf update clickhouse-server clickhouse-client` between refreshes.
• Backup / restore: BACKUP TABLE ... TO Disk|S3 (native backup), or volume snapshots with the server stopped.
• 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/clickhouse-server/; `journalctl -u clickhouse-server -f`
• Health check: clickhouse-client -q 'SELECT 1'

Known limitations

Single node; replication/sharding (Keeper, clusters) is a deliberate multi-node design.

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