Lifecycle outside the valid range for the vault
What AWS reports
backup job failed because the lifecycle is outside the valid range for backup vaultlifecycle is outside the valid rangeMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
The vault has a vault lock setting MinRetentionDays or MaxRetentionDays, and the retention in your backup rule falls outside that range. AWS Backup refuses to create the recovery point rather than silently storing it with the wrong retention.
How to fix it
- Change the retention (DeleteAfterDays) in the backup plan so it sits inside the vault’s min/max retention range.
- Or update the vault lock configuration if the range itself is wrong.
- Remember cold storage needs retention ≥ 90 days beyond the transition-to-cold value.
What AWS documents
AWS reports this failure when retention is outside the vault’s minimum and maximum retention days.
Source: AWS Backup Developer Guide — Troubleshooting FAILED jobs
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