RDS skips its final snapshot
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
skip_final_snapshot = true means deleting the instance takes no final backup, so the data is unrecoverable once the resource is gone.
Why it matters
skip_final_snapshot = true tells RDS to take no final backup when the instance is deleted, so once it is gone the data is unrecoverable. That is fine for throwaway test databases but dangerous for anything holding real data, where an accidental destroy then means permanent loss.
How to fix it
Set skip_final_snapshot = false for production and provide a final_snapshot_identifier. Keep automated backups enabled with a sensible backup_retention_period as well. Reserve skip_final_snapshot = true for databases you can freely recreate, and label them clearly.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo