All checks
Medium
RDS DB instances should be configured with multiple Availability Zones
Confirms that RDS DB instances use a Multi-AZ deployment, which keeps a synchronous standby in a second Availability Zone and fails over to it automatically. RDS Custom for SQL Server and RDS Custom for Oracle instances are evaluated too, and convert the same way once their Multi-AZ prerequisites are in place.
- service
- RDS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Replaces the resource: SQL Server Express has no Multi-AZ and no in-place edition change: restore a snapshot as Standard, Enterprise or Web, repoint clients, then delete this instance.
In the console
RDS → Databases → the DB instance → Modify → Availability & durability
- Multi-AZ deployment
- Yes (SQL Server: Standard, Enterprise, or 2022 Web Edition at 16.00.4215.2 or later)
- Schedule modifications
- Apply immediately at a quiet time, as the conversion adds I/O load, or wait for the next maintenance window
With the AWS CLI
aws rds modify-db-instance --db-instance-identifier <db-instance-id> --multi-az --region <region>With Terraform
resource "aws_db_instance" "this" {
instance_class = var.instance_class
multi_az = true
}See which of your accounts this check is failing on.
Book a live scan