Skip to content
Encryption at rest for Postgres volumes, and TLS for the Postgres TCP Proxy
olucasalles
OP

a month ago

Hi Railway team,

We are preparing to run a production Postgres database on Railway (the Postgres service with an attached volume, in US East). For our data-protection documentation under LGPD (Brazil), we need written confirmation of a few points:

  1. Is the volume that backs a Postgres service encrypted at rest? If so, at which layer (block storage, disk or filesystem), with which algorithm, and who manages the keys?
  2. Are volume backups (daily, weekly and monthly) also encrypted at rest?
  3. Exhibit C of the DPA says "Databases are encrypted at rest". Does that cover customer volumes and customer-deployed databases, such as the Postgres template, or only Railway's internal databases?
  4. Is there a document we can cite for this, such as the SOC 2 Type II report available through the Trust Center?
  5. Is traffic between services over the private network encrypted in transit?
  6. The Postgres TCP Proxy presents a self-signed server certificate. Is there an official Railway CA we can use to verify it with sslmode=verify-full, or is pinning the server certificate (verify-ca) the recommended approach?

Thank you!

Solved

1 Reply

Railway
BOT

a month ago

Yes, the volume behind a Postgres service is encrypted at rest, and so are its volume backups (daily, weekly and monthly). The control to cite is the Encryption-at-rest control on our Trust Center, under Data Security: "All data at rest within Railway's systems is encrypted using AES 256, providing robust protection against unauthorized access and ensuring data confidentiality." Encryption and key management are handled by us on infrastructure we operate. Neither is exposed to or configurable from your workload, and we don't offer customer-managed keys.

That control isn't limited to one product or plan. It covers customer volumes, customer-deployed databases such as the Postgres template, and their backups, not just our internal systems. You can treat this reply as our written confirmation.

For documents you can cite, the Trust Center control descriptions and the SOC 3 report are public, with no sign-in needed. The SOC 2 Type II report, the Encryption Policy and the Backup Policy are available there after signing in with your account email.

Traffic between services on the private network is encrypted in transit. It runs over a WireGuard mesh.

The TCP Proxy is a raw TCP passthrough, so we don't terminate TLS on it or issue a certificate for it. The certificate you see is presented by the Postgres server running in your service, and we have no Railway CA to verify it against.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...