Amazon DocumentDB clusters should have an adequate backup retention period
Checks that a DocumentDB cluster keeps automated backups for at least 7 days; new clusters default to 1. The retention period bounds how far back a point-in-time restore can reach, and so how long corruption, a bad deployment or a destructive change can go unnoticed and still be undone.
- service
- DocumentDB
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Affects another check: RDS.50 reads the same retention period on this cluster, so raising it to 7 days or more clears that finding too.
In the console
Amazon DocumentDB → Clusters → the cluster → Actions → Modify → Backup
- Backup retention period
- 7 to 35 days: as far back as you would realistically need to restore
With the AWS CLI
aws docdb modify-db-cluster --db-cluster-identifier <cluster-identifier> --backup-retention-period 7 --region <region>With Terraform
resource "aws_docdb_cluster" "this" {
cluster_identifier = var.cluster_identifier
backup_retention_period = 7
}
See which of your accounts this check is failing on.
Book a live scan