Amazon Aurora clusters should have backtracking enabled
Confirms that Aurora MySQL clusters have backtracking enabled, so the cluster can be rewound to an earlier point in minutes to undo a destructive change without restoring from a backup.
- service
- RDS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
In the console
RDS → Databases → Create clone or Create database → Backtrack
With the AWS CLI
aws rds restore-db-cluster-to-point-in-time --db-cluster-identifier <new-db-cluster-identifier> --source-db-cluster-identifier <source-db-cluster-identifier> --restore-type copy-on-write --use-latest-restorable-time --backtrack-window <seconds> --region <region>With Terraform
resource "aws_rds_cluster" "this" {
engine = "aurora-mysql"
backtrack_window = var.backtrack_window_seconds
}
See which of your accounts this check is failing on.
Book a demo