Skip to main content
Data Storage Modules 0.35.0Last updated in version 0.31.4

Backup Vault Module

View SourceRelease Notes

This Terraform Module launches a Backup Vault that you can use to store, organize and, optionally, preserve your AWS Backup recovery points against deletion.

What is a Backup Vault?​

A backup vault is a container for securing and organizing your Backup artifacts, such as EC2 AMIs, RDS Database recovery points, EBS volumes, et cetera. You can specify an AWS KMS key ID that will be used to encrypt resources in this vault that support encryption. Learn more in the official AWS Backup encryption guide.

Note that, once you have enabled AWS Backup support in a given region for your account, there will always be a default vault named "Default" (note the casing). You cannot delete the default backup vault.

You can opt to either associate Backup plans and selections with your default vault, or any custom vaults you create.

What is a Backup Vault Lock?​

Locks are an optional means of adding an additional layer of protection for your recovery points stored in a Backup Vault. If you opt to lock a vault, you will secure its recovery points against delete operations and any updates that would otherwise alter their retention period. This means you can use locks to enforce retention periods, prevent early or accidental deletions by privileged users, and generally meet any compliance and data protection requirements you may have.

See the official AWS Backup Vault Lock guide for more information.

How do you lock a vault?​

To add a Vault lock when configuring a new vault with this module, set the locked attribute to true like so:

module "backup_vault" {

  vaults = {
    locked-vault = {
      locked              = true
      changeable_for_days = 5
      min_retention_days  = 30
      max_retention_days  = 120
    }
  }
}

How do you enable vault notifications?​

Backup vaults can publish notifications to an SNS topic. This is useful when you want to monitor for any problems with your backup workflows. To enable notifications for a vault when configuring a new vault with this module, set the enable_notifications attribute to true like so:

module "backup_vault" {

  ...

  vaults = {
    "vault-with-notifications-enabled" = {
        enable_notifications = true
        # If you wish to specify which AWS Backup events to listen to, you can pass them like so
        # If you do not pass events_to_listen_for, then all AWS Backup events will be listened for!
        events_to_listen_for = ["BACKUP_JOB_STARTED", "BACKUP_JOB_COMPLETED"]
    }
  }
}

WARNING - It is important to understand that misuse of locks could lead to high AWS spend​

For example, the following common conditions could all be true when you are developing against or testing AWS Backup. If:

  1. You create a lock for a vault
  2. the vault has a plan selecting many resources, for example, via widely used tags such as Snapshot: true
  3. Your account has many resources with matching tags
  4. Your lock takes effect, because you did not delete it during the 3 day cool-down period

then you will end up with many potentially large recovery points that you cannot delete and must pay for the storage of. Use extreme caution when testing, developing or studying!

Sample Usage​

main.tf

# ------------------------------------------------------------------------------------------------------
# DEPLOY GRUNTWORK'S BACKUP-VAULT MODULE
# ------------------------------------------------------------------------------------------------------

module "backup_vault" {

  source = "git::git@github.com:gruntwork-io/terraform-aws-data-storage.git//modules/backup-vault?ref=v0.35.0"

  # ----------------------------------------------------------------------------------------------------
  # REQUIRED VARIABLES
  # ----------------------------------------------------------------------------------------------------

  vaults = <any>

  # ----------------------------------------------------------------------------------------------------
  # OPTIONAL VARIABLES
  # ----------------------------------------------------------------------------------------------------

  # The cooling-off-period during which you can still delete the lock placed on
  # your vault. The AWS default is 3 days. After this period expires, YOUR LOCK
  # CANNOT BE DELETED
  default_changeable_for_days = 7

  # The ceiling of retention days that can be configured via a backup plan for
  # the given vault
  default_max_retention_days = 365

  # The minimum number of retention days that can be configured via a backup
  # plan for the given vault
  default_min_retention_days = 7

}


Reference​

Required​

vaultsanyrequired
Any types represent complex values of variable type. For details, please consult `variables.tf` in the source repo.

Optional​

The cooling-off-period during which you can still delete the lock placed on your vault. The AWS default is 3 days. After this period expires, YOUR LOCK CANNOT BE DELETED

7

The ceiling of retention days that can be configured via a backup plan for the given vault

365

The minimum number of retention days that can be configured via a backup plan for the given vault

7