Home / AWS Backup errors

KMS key not accessible / cannot decrypt

Critical FAILED AWS Backup
What AWS reports
is not enabled or you do not have permissions to access itgiven key id not accessiblecannot decrypt the sourcekms key is not accessiblekey id not accessible

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

The backup role cannot use the KMS key that encrypts the source (common with encrypted RDS/EBS). On-demand backups may succeed while scheduled ones fail, because some copy calls do not touch KMS.

How to fix it

  1. Add the backup IAM role as a key user on the source KMS key.
  2. Ensure the role has at least kms:Decrypt, kms:GenerateDataKey and kms:CreateGrant on that key.
  3. For cross-account or cross-Region copies, also grant kms:DescribeKey on the destination key.

What AWS documents

AWS states the IAM role must have at least Decrypt, CreateGrant and GenerateDataKey permissions on the KMS key.

Source: AWS Backup Developer Guide — Troubleshooting (KMS)

Stop finding this one failure at a time

BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.

Start free trial