Databases
Salus can provision and run managed PostgreSQL databases for you. A database is an organization-level resource: you choose a size, Salus creates the instance, and you wire its connection details into the projects that need it — no separate database host to operate.
Each database is provisioned into a specific environment (region), so you can run, for example, a development instance and a production instance side by side.
What you get
- A managed PostgreSQL instance, with the engine version chosen at creation time.
- A private internal endpoint that your Salus deployments reach directly, plus an optional external endpoint for connecting over the public internet.
- TLS is required on every connection.
- A lifecycle status that reflects the instance’s current state and the last change made to it.
The database lifecycle
A database moves through a small set of states, shown on its overview:
- Provisioning — Salus is creating the instance. Settings can’t be changed yet.
- Active — the instance is running normally. This is the only state in which you can change resources or rotate the password.
- Updating — a change is rolling out (a resize, a version upgrade, or a password rotation). Settings are locked until it completes.
- Suspended / Unavailable — the instance isn’t currently serving connections; check its overview for the cause.
- Failed / Error — the last change didn’t complete successfully.
- Deleting — the instance is being torn down.
Whenever the database isn’t Active, changes are temporarily disabled — wait for the current process to complete and try again.
Your organization's databases, with each instance's engine, region and status
In this section
- Provision a database — tiers, naming, and the one-time admin password.
- Connect a database — link it to a project, or connect manually; endpoints and network access.
- Manage a database — resize, upgrade, rotate the password, and delete.