Last updated 2019-10-23
For supported logging endpoints, Fastly allows you to encrypt your log files before they are written to disk. The files are encrypted using OpenPGP (Pretty Good Privacy).
Be sure to take into account security, privacy, and compliance requirements when making configuration and endpoint decisions for the data you intend to include in streamed logs.
To use this feature, you'll need to use a PGP implementation (such as GPG) to generate a public and private PGP key pair. Typically, this involves running the following command in a terminal application on your personal computer:
$ gpg --gen-key
Follow the instructions shown in your terminal application. Enter your email address and set a passphrase when prompted. Remember the values you enter.
Keep your private key safe! If you lose it, your encrypted log files will be permanently unreadable.
After you generate the PGP key pair, you'll need to export your public key. Typically, this involves running the following command in a terminal application on your personal computer:
$ gpg --armor --export <your email>
The output will be in PEM (Privacy-Enhanced Mail) format and will look similar to the following:
1-----BEGIN PGP PUBLIC KEY BLOCK-----2mQGiBFciSsYRBAC9aHsraEzLmzfuQLx+BZmGTCOQFsPGpiPaEKrulRbrcBvtt3Bl3zajFP9iVzSm3+Zyqge/1AtHllSnPHTqG2EoBCsWtXL/JnZcPjx8c5r8G5IuBGrh84snP3KTJ64zCS7PUvrWy5RWcJ6Rs+6wiJ7zPOtU5wMEPuMbflh/soy50zrwCg74XN5[...REDACTED...]6-----END PGP PUBLIC KEY BLOCK-----
To enable PGP encryption for a logging endpoint that supports it, copy and paste your public PGP key into the PGP public key field in the Fastly web interface when creating or editing a supported logging endpoint.
To read an encrypted log file, you'll need to download and decrypt it. Typically, this involves running the following command in a terminal application on your personal computer:
$ gpg --decrypt <encrypted log file>
Enter your passphrase to decrypt the log file.