Client-managed database
OneView does not include PostgreSQL. Create a dedicated, empty database and a dedicated user in an externally managed PostgreSQL service.
The setup form requires the database hostname, port, database name, username, password, and TLS mode. The hostname is not a connection URL. Enter a new database name only if that is the database the client created for OneView.
Database TLS
The setup page offers two encrypted connection modes:
- Verify hostname and certificate encrypts the connection and verifies the PostgreSQL server's identity. This is the recommended production mode. Supply the approved CA certificate when the database uses a private certificate authority; leave the field empty when the server uses a publicly trusted certificate.
- Require encryption without verification encrypts the connection but does not verify the PostgreSQL server's certificate or hostname. Use it only for evaluation or when the database is reached through a separately trusted private network and the provider cannot present a verifiable certificate.
The setup page does not offer an unencrypted connection. The client should move to verified TLS before production when its provider supports it.
Railway's standard PostgreSQL template generates a self-signed server certificate for localhost, while external
clients connect through a different TCP-proxy hostname. Its normal deployment therefore cannot pass hostname-verified
TLS. Use Require encryption without verification for a Railway evaluation database, or deploy PostgreSQL with a
certificate and CA that match its actual connection hostname.
Connection process
- Test the connection.
- Review the safe connection facts returned by the server, including whether TLS identity verification succeeded.
- Acknowledge that the database is externally managed.
- Save the configuration.
OneView prepares the database and advances setup. Database credentials are not displayed again after setup. Keep the approved value in the client's secret-management process for recovery and credential rotation.
Client responsibilities
Configure backups, monitoring, high availability, maintenance, and retention. Do not expose PostgreSQL publicly.