MEDIUM

Ensure RDS instances have Multi-AZ enabled

Production RDS instances should have Multi-AZ deployment for high availability and automatic failover.

Security Impact

Single-AZ deployments have single point of failure and require manual intervention for recovery.

How to Remediate

Modify RDS instance to enable Multi-AZ deployment. This creates a synchronous standby replica in a different AZ.

Affected Resources

AWS::RDS::DBInstance

Compliance Frameworks

SOC 2NIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Relational Database Service (RDS) resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for SOC 2, NIST 800-53 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-rds-6
Service
Relational Database Service (RDS)
Category
High Availability
Severity
MEDIUM

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Relational Database Service (RDS) Checks

View all checks
aws-rds-1critical

Ensure RDS instances are not publicly accessible

aws-rds-2high

Ensure RDS instances have encryption at rest enabled

aws-rds-3medium

Ensure RDS instances use KMS customer managed keys

aws-rds-4high

Ensure RDS instances have automated backups enabled

aws-rds-5medium

Ensure RDS backup retention is at least 7 days