Ensures that RDS instances are created to be cross-AZ for high availability.
Creating RDS instances in a single AZ creates a single point of failure for all systems relying on that database. All RDS instances should be created in multiple AZs to ensure proper failover.
Follow the appropriate remediation steps below to resolve the issue.
Log into the AWS Management Console.
Select the “Services” option and search for RDS.
Scroll down the left navigation panel and choose “Databases”.
Select the “Database” that needs to be verified and click on the selected “Databse” from the “DB identifier” column to access the database.
Click on the “Configuration” under the selected database configuration page.
Scroll down the “Configuration” tab and check the “Availability” section.Check the “Multi AZ” and if it’s “No " then selected database cannot scale across multiple availability zones .
Repeat steps number 2 - 6 to check other RDS instances.
Select the “Database” on which automated backup needs to be enabled. Click the “Modify” button at the top to make the necessary changes.
Scroll down the “Modify DB Instance” page and check for “Multi-AZ deployment” under “Instance specifications”.
On the “Multi-AZ deployment” section under “Instance specifications” click on the “Yes” button.
Scroll down the “Modify DB Instance” page and click on “Continue” button.
On the “Scheduling of modifications” choose “Apply immediately” so that it will made the above changes applied as soon as possible and click on the “Modify DB Instance” button.
Repeat steps number 8 - 12 to enable scaling across multiple availability zones.