SSH connection settings
Host, port, and which key file to use still live in a personal SSH config and a wiki that says 'ask DevOps'. After a jump-host change, half the team still points at the old IP.
Hypervault stores server name, host, port, user, and auth method in an encrypted EU vault, with permissions for the engineers who are allowed on that box.
Why store SSH connection settings in a digital vault
The key path is a laptop-specific location
A new engineer cannot connect. Key file location on the vault item is the shared instruction, plus last rotated for the key.
Password vs key is not written down
People try both and lock the account. Authentication method as a field is the first thing to read.
Port 22 is assumed after a hardening change
Custom ports fail. Host/IP and port together are the actual endpoint.
Jump hosts are tribal
Notes and owner/team on the item show who maintains the path in.
Who uses this template
DevOps and SRE
Record host, port, user, and auth method per server instead of a private SSH config.
Application engineers with bastion access
Open the vault item rather than pinging the last person who SSH'd in.
MSPs on customer Linux estates
Keep per-client SSH settings in an EU vault with a named owner.
Fields in this template
Keep every record complete and easy to find. Existing fields stay as they are; extras are added only when a vault item would otherwise be incomplete.
- Server name
- Host/IP address
- Port
- Username
- Authentication method
- Key file location
- Notes
- Owner/team
- Last rotated
How it works in Hypervault
Create from the template
Add an item from the SSH connection settings template in your workspace.
Fill and attach
Complete the fields and attach supporting files where needed.
Share with the right roles
Give access only to the people who maintain or use this record.
Related templates
Access point information
Template for storing and managing access point information including network details, credentials, and configuration settings.
Computer accounts
Template for managing computer accounts, user credentials, and system access information.
Devices
Template for managing device information including serial numbers, warranties, and ownership details.
Store it in a vault, not a spreadsheet
Create a workspace, pick this template, and keep credentials and supporting files encrypted in the EU.