Hi,

I'm running a MySQL database on Railway (used as our QA environment). I'd like to understand the encryption-at-rest situation before I decide whether to configure anything myself.

Could you help me with the following:

1. Is the storage volume for Railway MySQL databases encrypted at rest by default? If so, what encryption is used (e.g. AES-256) and who manages the keys?

2. If it is not encrypted by default, is there a way to enable encryption at rest on a Railway-hosted MySQL instance?

3. Does Railway support MySQL's Transparent Data Encryption (TDE) — i.e. do I have the access needed to configure a keyring component, edit my.cnf, and place the keyring manifest files? Or is the MySQL service too locked down for that?

4. If I need lower-level control, is running my own custom MySQL Docker image the recommended path, and are there any docs for that?

I just need at-rest protection for the data on disk (compliance/peace-of-mind), not anything application-level. If the storage is already encrypted at the infrastructure level, that fully covers my need and I don't have to do anything further.

Thanks

Dinesh