Encrypting Heroku Postgres with Your Encryption Key
Last updated 28 August 2020
Table of Contents
This article describes how to use AWS Key Management Service (KMS) to create a Customer Master Key (CMK) to encrypt Heroku Postgres in Private and Shield Spaces. This process involves three high-level steps:
- Create an Customer Master Key (CMK) in your AWS KMS
- Apply an IAM policy to that CMK to permit Heroku Data to use the key on your behalf
- Create a Postgres database with the encryption key
You perform the steps in this section from your Amazon KMS dashboard. Alternatively, can use the AWS CLI as shown below.
Your CMK must be located in the same region as your Heroku Postgres database. A list of supported regions is listed here.
Step 1: Create a Customer Master Key
Once logged into the AWS web console, navigate to Key Management Service and click Create Key.
Step 2: Select Symmetric Key
Select Symmetric Key and click Next.
We use S3 to store backups and it only supports symmetric CMKs.
Step 3: Add Details and Set Permissions
Add an alias (eg:
heroku-data) and press Next. There is no requirement to further configure key administrative permissions. Click Next.
When defining key usage permissions, scroll to the bottom to Add another AWS account. Enter the Heroku Data AWS Account ID (
021876802972) in the box and press Next.
Step 4: Review and Complete
Review the key policy and complete creation. Note the Amazon Resource Name (ARN) of your CMK.
Step 5: Enable automatic key rotation
You can enable automatic key rotation by opening the info page for your key. At the bottom of the page, select the Key Rotation tab, check the box, and press Save.
Alternative: Use the AWS CLI
You can use the AWS CLI to create your Customer Master Key (CMK) with the appropriate key policy.
$ export AWS_ACCOUNT_ID=`aws sts get-caller-identity --output text --query 'Account'` $ export HEROKU_DATA_ACCOUNT_ID=021876802972 $ curl -s -o key-policy.json https://gist.githubusercontent.com/jdowning/8d146cd238de828141e81b458dc546f0/raw/fc2a69603dc1364f1bc2fd2b5beb0af210150444/key-policy.json $ aws kms create-key --description 'heroku-data' --policy $(envsubst < key-policy.json)
The output of the
create-key command will include the key’s ARN which you will need during provisioning. This will be referred to has
CMK_ARN in later steps.
We recommend you enable automatic key rotation on your CMK:
$ aws enable-key-rotation --key-id CMK_ARN
Create a Heroku Postgres database with an encryption key
Now that you have a Customer Master Key with the appropriate permissions configured, you can use that key to encrypt your data managed by Heroku Data. You will need the full Amazon Resource Name (ARN) of your CMK. You can use the
--encryption-key provisioning flag when creating your database.
$ heroku addons:create heroku-postgresql:private-7 --encryption-key CMK_ARN --app your-app-name
Migrate a Heroku Postgres database to one using an encryption key
If you have an existing Heroku Postgres database, you can create a follower database using your encryption key to migrate your data.
$ heroku addons:create heroku-postgresql:private-7 \ --follow HEROKU_POSTGRES_LEADER_COLOR \ --encryption-key CMK_ARN \ --app your-app-name
Once your follower is created and caught up to the leader, you can promote it.
$ heroku maintenance:on $ heroku pg:promote HEROKU_POSTGRESQL_FOLLOWER_COLOR $ heroku maintenance:off
You can read more details about database promotion in our Upgrading Heroku Postgres article.
Disabling your encryption key
As part of the lifecycle of your encryption key, you may need to disable the key. When performing this action, all data encrypted with the key will be rendered inaccessible.
Disabling an encryption key will trigger a shutdown of all services and servers that use that key. Please use extreme caution when taking this action. We recommend you notify and coordinate with Heroku Support when performing this action.
You can disable your encryption key via the AWS web console or the AWS CLI.
$ aws kms disable-key --key-id CMK_ARN
Once we receive notification of the key disablement, there is a 10 minute waiting period before action is taken. This is to ensure accidental changes to the key status do not unnecessarily alter resources that depend on the key.
After the 10 minute waiting period, we will shutdown all services that use the encryption key. Next, we will stop all servers that run those services. Finally, we will send an email notification to application administrators notifying them of the disabled action.
Expect approximately 20 minutes to elapse between key disablement and service shutdown.
Enabling your encryption key
If you need to regain access to data that is encrypted with your encryption key, you may enable that key to restore. You can enable your encryption key via the AWS web console or the AWS CLI.
$ aws kms enable-key --key-id CMK_ARN
Once we receive notification of the key enablement, we will start previously stopped servers. Once they are running, we will start affected services. Finally, we will send an email notification to application administrators notifying them of the enabled action.
Expect approximately five minutes to elapse between key enablement and service restart.
There are limitations that apply to databases encrypted with a customer encryption key.
- Database must be in a Private or Shield Space.
- Followers and Forks must use the same encryption key as their leader.
- PGBackups will not work. This includes using the
heroku pg:copyCLI commands.
For your security, there is no automated way to migrate from using a customer-supplied key to a Heroku-managed key lifecycle. If you would like to stop using this feature on one more more data services, please contact Heroku support.