How to encrypt and use a .env file for a service hosted on S3.
Apps are configured by putting files in a secure configuration bucket on S3. The ENTRYPOINTscript for our apps pulls all files in from the app’s path in the bucket before starting up. This allows an app to be securely configured with a .env file and, for example, server.crt and server.key files for TLS connections.
An AWS CLI login (this is different from the AWS account you can log into via the web)
kms:Encrypt permissions
The AWS Command Line Interface package installed and configured
Though .env files are stored encrypted in S3 and only transferred securely, we still encrypt environment variables like passwords so that they are not seen in plain when editing the .envfiles.
Each service is configured to have its own private key in the Amazon KMS keystore. Only the task role may decrypt with that key.
Adding the _KMS_ENCRYPTED suffix to an environment variable’s name in the .env file will cause the task to decrypt the variable at runtime, storing it in process.env after stripping the suffix.
To create an encrypted environment variable value:
Visit the “Customer managed keys” section of the KMS part of the AWS web console.
Look for the Key ID for your service. Save it in the $CONFIG_KEY_ID environment variable.
Log in to AWS CLI with an account that has kms:Encrypt permissions for the key.
Run the following command with a leading space so that it doesn’t appear in your command history: aws kms encrypt --output text --key-id $CONFIG_KEY_ID --plaintext STR-TO-BE-ENCRYPTED
Copy the encrypted value (the output up to the whitespace) as the value in .env: PASSWORD_KMS_ENCRYPTED=…
Note that using --plaintext on the command line will cause aws kms to encrypt the ASCII as-is. When using the fileb:// form to reference a file on disk, aws kms will first Base64 encode the value, which will cause a failure on the app side, which does not expect Base64-encoded values.
Decrypting a variable which was encrypted using the method above is possible using the following commands in a terminal session:
If you have multiple profiles on your computer, you may use this option in the aws kms decrypt command:
--profile=myprofile