On-demand backups work but scheduled ones fail with a KMS error
is not enabled or you do not have permissionssource snapshot kms key does not existkms key does not existMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
The exact message is “The source snapshot KMS key does not exist, is not enabled or you do not have permissions to access it.” The confusing part is that on-demand backups still succeed: they use the CopyDBSnapshot API, which does not require KMS access. Scheduled backups take a different path and do. So the resource looks fine when you test it by hand and fails every night.
How to fix it
- Open AWS KMS → Customer managed keys and select the key encrypting the RDS instance.
- Edit the key policy and add the IAM role that AWS Backup uses (the default is AWSBackupDefaultServiceRole).
- Grant it at minimum kms:Decrypt, kms:DescribeKey, kms:CreateGrant and kms:GenerateDataKey.
- Wait for the next scheduled run, or trigger the plan, and confirm the job reaches COMPLETED.
What AWS documents
AWS gives the remedy directly: add your IAM role to your KMS key. It notes the on-demand job succeeds because CopyDBSnapshot does not require KMS access.
Source: AWS Backup Developer Guide — Troubleshoot creating resources
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