RDS Instance Not Using Multi-AZ
A failure in one availability zone takes the database down until it is restored from backup, with everything written since the last snapshot at risk.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Multi-AZ on RDS instance.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- RDS Instances on AWS
- The fix, by hand
- Open RDS → Databases → select this instance.
- Click Modify → scroll to Availability and durability.
- Set Multi-AZ deployment = 'Create a standby instance'.
- Choose 'Apply immediately' (or schedule for the next maintenance window; the standby is built before the brief I/O suspension).
- The instance enters 'modifying' state; conversion completes within ~10 minutes.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-005- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.