Cloud SQL No Maintenance Window Configured
Maintenance can restart the instance at any time, so an unavoidable restart is as likely to land in business hours as out of them.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Configure a maintenance window on Cloud SQL instance.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Cloud SQL on Google Cloud
- The fix, by hand
- Open Cloud Console → SQL → Instances → the resource → Edit.
- Under Maintenance, pick a day-of-week and hour that overlaps your lowest-traffic period.
- Save. Patches will only apply inside the chosen window.
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-1241- 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.