Skip to content

Encrypt and decrypt SOPS files with AWS KMS


Using a SOPS file to store secrets in the git repository.

Encrypting the SOPS file with a KMS key.


We are assuming the binbash Leverage Landing Zone is deployed, an account called apps-devstg was created and a region us-east-1 is being used. In any case you can adapt these examples to other scenarios.



To know more about SOPS read here.

How to

We will be using binbash Leverage shell command to achieve this.

The source file

First, in the layer where you need the SOPS file, create a sample yaml, e.g. a file secrets.yaml:

  subtopic: value

Access the shell

First, be sure your credentials are up to date. You can run a leverage tf plan and they will be updated.

Run the shell command:

leverage shell --mount /{path-to-your-tools-directory}/sops/ /extrabin

Encrypt the file

Note for encrypting you need to specify an AWS Profile. In the binbash Leverage context profiles are like this: {short-project-name}-{account}-{role}. For example, for my apps-devstg account, using the role devops, in my project bb, the profile is: bb-apps-devstg-devops.

From the new shell encrypt your file:

AWS_PROFILE=bb-apps-devstg-devops /extrabin/sops --encrypt --kms {your-kms-arn-here} secrets.yaml > secrets.enc.yaml


Since binbash Leverage Landing Zone is being used, the default key for the account+region has an alias: ${var.project}_${var.environment}_${var.kms_key_name}_key, in this case is vp_apps-devstg_default_key, so arn:aws:kms:<region>:<account>:alias/vp_apps-devstg_default_key should be used.


To use this file with Terraform, edit the secrets.enc.yaml and at the bottom, edit the line with aws_profile and set there the AWS Profile you've used to encrypt the file.

Decrypt the file

From the shell decrypt your file:

AWS_PROFILE=bb-apps-devstg-devops /extrabin/sops --decrypt secrets.enc.yaml

How to use it with Leverage

Now that the secret is stored in a secure file, it can be used.

The example here is prety simple, just getting the value and sending it to an output. But it can be used in any other resource.

First your user (the one used to run binbash Leverage ) needs access to the used KMS key.

Then, open the file:

data "sops_file" "secrets" {
  source_file = "secrets.enc.yaml"

...and use it:

output "thevalue" {
    value =["topic.subtopic"]