Other Articles
- Cloud SQL – Configure Private IP
- Cloud SQL – Monitor CPU Utilization
- Cloud SQL – Enable Deletion Protection
- Cloud SQL – Enable Disk Encryption
- Cloud SQL – Enable Automated Backups
- Cloud SQL – Enable Log Export
- Cloud SQL – Enforce Password Validation
- Cloud SQL – Protect From Internet Access
- Cloud SQL – Enforce Secure Transport
- Compute Engine – Block Project-Wide SSH Keys
- Compute Engine – Disable IP Forwarding
- Compute Engine – Disable Public IP Addresses
- Compute Engine – Disable Serial Port Access
- Compute Engine – Enable Confidential Computing
- Compute Engine – Enable OS Login
- Compute Engine – Enable Shielded VM
- Compute Engine – Restrict Default Service Account
- General – Deny Public Access to KMS Keys
- General – Enforce Duties Separation
- General – Enforce KMS Key Rotation
- General – Restrict Admin Roles on Service Accounts
- Cloud Run – Configure Timeout Settings
- Cloud Storage – Enable Bucket Encryption
- Cloud Storage – Enable Bucket Logging
- Cloud Storage – Enable Bucket Versioning
- Cloud Storage – Enforce Uniform Bucket-Level Access
- Cloud Storage – Restrict Public Access
- IAM Users – Enforce GCP-Managed Keys
- IAM Users – Rotate External User-Managed Service Account Keys
- GKE – Enable Private Nodes
- GKE – Restrict Control Plane Access
- GKE – Enable Workload Identity
- GKE – Disable Legacy ABAC
- GKE – Enable Network Policy
- GKE – Enable Shielded Nodes
- GKE – Enable Node Auto-Upgrade and Auto-Repair
- GKE Cluster – Enable Cluster Logging
- General – Enable Cloud Audit Logs
- General – Configure a Log Sink
- General – Configure Log Bucket Retention
- Cloud SQL – Configure Maintenance Window
- Cloud Storage – Configure Bucket Retention or Lifecycle
- General – Enable Security Command Center
- Compute Engine – Enable Instance Deletion Protection
- VPC Firewall – Restrict Public SSH and RDP Access
- VPC Firewall – Restrict Public Database Access
- VPC Network – Avoid the Default Network
- VPC Network – Enable Subnet Flow Logs
Cloud SQL – Enable High Availability
Secure Configuration Checks > GCP
This check ensures that Cloud SQL instances are regional, which makes them highly available. A standby instance in a second zone takes over if the main zone fails. Read replicas are not checked.
Check Details
- Resource: Cloud SQL Instance
- Check: Enable Cloud SQL high availability
- Risk: If the zone of a single-zone instance fails, the database goes offline. Applications that depend on it have an outage until the zone recovers.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Cloud SQL.
- Click on the affected Cloud SQL instance.
-
Click Edit to modify the instance configuration.
- Expand Customize your instance and scroll to the Availability section.
-
Select Multiple zones (Highly available).
- Click Save to apply the changes.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
List the single-zone instances. Read replicas are left out:
gcloud sql instances list \ --filter="settings.availabilityType=ZONAL AND instanceType=CLOUD_SQL_INSTANCE" \ --format="table(name,region,settings.availabilityType)"
-
Update the Cloud SQL instance to be highly available:
gcloud sql instances patch <INSTANCE_NAME> --availability-type=REGIONAL
Replace
<INSTANCE_NAME>with your Cloud SQL instance name. Automated backups must be turned on first. Point-in-time recovery, or binary logging for MySQL, must also be on. The change can cause a short interruption, so apply it in a maintenance window. -
Verify the availability type:
gcloud sql instances describe <INSTANCE_NAME> \ --format="value(settings.availabilityType)"
The output must be
REGIONAL.
Default Value
Unless you choose high availability when you create the instance, it runs in a single zone. High availability costs more, because a standby instance runs in a second zone.
Updated on 09 November, 2026