Deploying Encrypted Configurations Using Docker and Node.js

You may know that it’s good to not check your database credentials into Git. Good! Knowing is half the battle right? I’ve found that deploying secure configurations using Docker is actually a straightforward process. (You just search through the 5,000 Docker CLI flags until you find one that looks right?)

Before we get to Docker though, let’s start at the beginning.

Encrypting Data

When storing production for my Node.js server, I like to use a simple file like configuration.js. Some people prefer a json file. It’s really up to you.

export const config = {
username: "DarkHelmet",
password: "12345"

If I have multiple configurations for different environments, then I’ll use process.env to decide which one to export.

if (process.env === 'production')
export productionConfig;

Regardless of the file type, I will encrypt it in the same way. The basic idea is: generate a key pair, encrypt the files, and write the encrypted content out. Here’s a gist of something I’ve used that takes advantage of the node-rsa package. I like using an npm package instead of an alternative mechanism because it makes it easier to consume later on when decrypting.

Using the Encrypted Configuration

So how do we consume the configuration in production? Well, as I said, using an npm package makes this way easier. In my case I have a file that looks something like this:

import { decrypt } from './decrypt';
const fs = require('fs');
const env = process.env.NODE_ENV;
if (env === 'production' && !fs.existsSync('./production.js')) {
const config = require(`./${env}.js`);
module.exports = config;

If we’re running in production, I decrypt the configuration. It’s worth noting that this decryption only happens once — the time at which I import it into my server.js file for use. This is important, because otherwise we’d be running a decryption on every request and that sounds pretty inefficient.

Decrypting things looks pretty similar to the earlier gist using node-rsa.

Accessing the Private Key in Docker

How do we access the private key in the Docker container? Obviously if we pushed the key up with our app and deployed it in the container that would kind of defeat the purpose. The solution we’re looking for in Docker is called a volume — specifically a host volume.

So you’ve uploaded your key to a server somewhere, presumably with scp. Maybe if you’re really cool you’re using puppet or something else to set up your environment with the keys already. We use the volume option to essentially say “use this directory on the host machine as though it was a directory in my container”.

In the cli command this looks like:

docker run [some options] -v ~/keys:/in-container/keys

Where keys is the host directory and in-container is, well, in the container. If you’re using docker-compose you’re pretty cool already and it will look something like:

[some options]
- "~/keys:/in-container/keys"

Now the private key is accessible inside our Docker container. That means we can read the file in and decrypt our production settings. You can now push configurations to Git to your ❤️’s content.

Just don’t push your private key — but no one has ever pushed something to Git on accident right?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.