Split every operational secret per host
Split the four per‑host operational secrets after establishing that
two hosts sharing one dead‑man's switch alert less than two
switches, not more, and that a shared backup passphrase can expose
both hosts' backups, even in separate repositories, if someone
obtains it and can read both repositories' encrypted data and key
files.
September 2026

Situation. The platform was built for one host and was about to have
two. Several operational secrets had been written as single values
on that assumption: one backup repository, one passphrase, one alert
switch. Extending them to a second host by sharing them is the path
of least resistance and it is wrong in two separate ways, both of
which fail quietly.

Task. Each secret had to become a map keyed by host, and the reason
had to be written down, because the shared version looks correct and
costs nothing until the day it matters.

Action. Two arguments settled it, and both are recorded next to the
configuration. A dead‑man's switch shared by two hosts alerts less
than two switches, not more: either host still pinging keeps the
check green while the other one is dead, so adding a host to a
shared switch actively reduces the coverage of the one that was
already there. And a backup repository string names a location, not
an independent credential boundary. Separate restic repositories can
have distinct master keys even when they use the same passphrase.
But someone who obtains that passphrase and can read both
repositories' encrypted data and key files can unlock both, so
sharing it couples their exposure rather than isolating the hosts.
Each value became a map keyed by inventory hostname, resolved per
host by a shared task file that both the converge and the preflight
run. The existing host was then named in all four maps with its
repository and both switches left empty, which is the truthful state
and keeps the two open initiatives honest about owing the operator
half of the work rather than the code.

Result. Secrets are per host by construction, and the two failure
modes that would have followed from sharing them are written down
where the next person edits the file. The empty entries are the part
worth keeping: they say the wiring exists and the value does not,
which is a different and more useful statement than a missing key.

Categories:
1Solution Architecture	/categories/solution-architecture/	engineer.company	70
1Infrastructure	/categories/infrastructure/	engineer.company	70
1Automation & CI/CD	/categories/automation/	engineer.company	70
1Reliability & Backups	/categories/reliability/	engineer.company	70
1Linux & Servers	/categories/linux/	engineer.company	70
1Security	/categories/security/	engineer.company	70

Services:
1Infrastructure as Code	/services/infrastructure-as-code/	engineer.company	70
1Site Reliability & Monitoring	/services/site-reliability/	engineer.company	70
1Backup & Disaster Recovery	/services/backup-recovery/	engineer.company	70
1Security & Access Management	/services/security-access/	engineer.company	70
1AI Agent Security	/services/ai-security/	engineer.company	70

hThis page on the web	URL:https://engineer.company/portfolio/split-every-operational-secret-per-host/	engineer.company	70
