ArangoDB v3.10 is under development and not released yet.
This documentation is not final and potentially incomplete.
ArangoDB Server Encryption Options
path-to-keyfile must contain the encryption key. This file must be
secured, so that only
arangod can access it.
You should also ensure that in case someone steals your hardware, they will not be
able to read the file. For example, by encrypting
creating an in-memory file-system under
/mytmpfs. The encryption keyfile must
contain 32 bytes of data.
This output is used if you want to use the program to generate your encryption key.
path-to-my-generator must output the encryption on standard output
and exit. The encryption keyfile must contain 32 bytes of data.