A managed database is a PostgreSQL, MySQL or Redis instance LayerOne provisions, secures and backs up for you. It runs on one of your private networks and has no public address, so only your servers on that network can reach it. Find them under Databases in the client area.
Create one
- Open Databases and choose New database.
- Pick the engine: PostgreSQL, MySQL or Redis.
- Name it, choose one of your ready private networks, and set a private address inside that network's range.
- Create it. The database is ready in a minute or two.
You do not set the size, the database name, the user or the password at this step. LayerOne picks a starting size per engine, generates the credentials, and issues a TLS certificate. You can resize it afterwards.
Connect to it
Open the database to see its connection details. A database answers only on its private network, so connect from a server on the same network.
- Connection URL and individual connection variables
(
DATABASE_URL,DATABASE_HOST,DATABASE_PORT, and so on;REDIS_*for Redis) are shown on the page, with a copy-as-.envoption. - Credentials are hidden until you choose Reveal credentials.
- SSL is required by default. Use
sslmode=require(PostgreSQL),--ssl-mode=REQUIRED(MySQL), or arediss://URL (Redis). Download the per-database CA certificate for full certificate verification.
Attaching a database to an application injects these values for you and keeps them current when the password rotates.
Backups
Databases back up on the same schedule mechanism as a server: daily, weekly or monthly at an hour you choose, plus on-demand copies, with a retention count you set. Copies draw from your organization's backup-storage pool. A restore rebuilds the database in place at its current size, reconnects its private network, and reconciles the password so attached applications keep working. See Backups and snapshots for how the pool is billed.
Resize, credentials, and updates
- Resize vCPU, memory and disk from the database page, then redeploy. The data is preserved, disk can only grow, and the hourly rate follows the new size.
- Rotate the password if it may have leaked. The user, the data and the TLS certificate stay the same and the database keeps running.
- Engine updates apply same-major upgrades, keeping a recovery snapshot in case one needs to be rolled back.
What it costs
A managed database is billed by the hour for the memory, vCPU and disk it is provisioned with, drawn from account credit, the same metered rates as the rest of the platform. There is no plan to choose and no egress charge, because the database stays on your private network. The database page shows its month-to-date cost, and the live rates are on the Managed Databases page. Billing starts when the database first comes up and stops when you destroy it.