All checks
Medium
RDS DB clusters should be configured for multiple Availability Zones
Confirms that RDS DB clusters have instances in more than one Availability Zone, so a failover has a running instance elsewhere to move to. The cluster reports where its instances sit, so the fix is a new reader rather than a setting. DocumentDB and Neptune clusters are evaluated too (aws_docdb_cluster_instance, aws_neptune_cluster_instance, or the docdb or neptune CLI).
- service
- RDS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
In the console
RDS → Databases → the DB cluster → Actions → Add reader
With the AWS CLI
aws rds create-db-instance --db-instance-identifier <new-reader-id> --db-cluster-identifier <db-cluster-id> --db-instance-class <db-instance-class> --engine <engine> --availability-zone <availability-zone> --region <region>With Terraform
resource "aws_rds_cluster_instance" "reader" {
cluster_identifier = aws_rds_cluster.this.id
engine = var.engine
instance_class = var.instance_class
availability_zone = var.reader_availability_zone
}See which of your accounts this check is failing on.
Book a demo