Cloud SQL for MySQL release notes

You can now create custom organization policies for the BackupRun resource in Cloud SQL instances. In addition, more fields in the Instances resource are available to create custom organization policies. For more information, see Add custom organization policies.

You can now have Cloud SQL create a Private Service Connect endpoint automatically instead of creating the endpoint manually after the instance is created. You use this endpoint to access a Cloud SQL instance through a VPC network. For more information, see Connect to an instance using Private Service Connect. This feature is available in Preview.

You can now view the size of a backup for a Cloud SQL instance.

When you run the backupRuns.GET API or the gcloud sql backups describe command, the maxChargeableBytes parameter now appears in the response. This parameter contains the maximum number of bytes that you can be charged for a backup.

You can now create a read replica for an instance that has private services access configured for it and connector enforcement enabled for it. For more information, see Connect using Cloud SQL Language Connectors.

Cloud SQL for MySQL now supports minor version 8.0.39. To upgrade your existing MySQL 8.0 instance to the new version, see Upgrade the database minor version.

You can now configure server certificate authority (CA) mode when you create a Cloud SQL instance. With server CA mode, you have two options:

• Per-instance CA: this is the default configuration. With this option, an internal CA dedicated to each Cloud SQL instance signs the server certificate for that instance.
• Shared CA: with this option, the Cloud SQL instance uses a CA hierarchy consisting of a root CA and subordinate server CAs managed by Cloud SQL and hosted on Google Cloud Certificate Authority Service (CA Service). The subordinate server CAs in a region sign the server certificates and are shared across instances in the region. This option can be used only with MySQL 8.0.30 and later.

For more information about each option, see Certificate authority (CA) hierarchies. This feature is in Preview.

Cloud SQL for MySQL 8.4 is now generally available. For more information about the differences between MySQL 8.4 and MySQL 8.0, review What Is New in MySQL 8.4 since MySQL 8.0.

By default, if you specify MySQL 8.4 as the version when you create a Cloud SQL instance (either primary or replica) using the gcloud CLI or the REST API, then the Cloud SQL edition is Enterprise Plus.

If you specify a version other than MySQL 8.4 or don't specify a version, then the default Cloud SQL edition of the instance is Enterprise.

For more information about the implementation of MySQL 8.4 in Cloud SQL, see the following topics:

• MySQL 8.4 authentication plugin default
• MySQL features unsupported for Cloud SQL
• MySQL 8.4 user privileges (cloudsqlsuperuser)

To create a MySQL 8.4 instance in Cloud SQL, see Create instances. Before you upgrade to MySQL 8.4, you must first upgrade to MySQL 8.0.37 or later. To perform a major version upgrade, see Upgrade the database major version in-place. To perform a minor version upgrade of Cloud SQL for MySQL 8.0, see Upgrade the database minor version.

Cloud SQL now supports near-zero downtime planned maintenance on standalone Cloud SQL Enterprise Plus edition primary instances. In addition, you can also simulate near-zero downtime for planned maintenance events on standalone Cloud SQL Enterprise Plus edition primary instances.

For more information, see About maintenance on Cloud SQL instances.

You can now upgrade your instances to Cloud SQL Enterprise Plus edition with near-zero downtime. To upgrade your instance, see Upgrade an instance to Cloud SQL Enterprise Plus edition using in-place upgrade.

You can now upgrade the minor version of a Cloud SQL for MySQL Enterprise Plus edition instance with near-zero downtime. To upgrade the minor version of your Cloud SQL for MySQL 8.0 instance, see Upgrade the minor version.

You can now provide access to Cloud SQL Studio by granting a new IAM role, Cloud SQL Studio User (roles/cloudsql.studioUser), instead of using the Cloud SQL Admin IAM role.

For more information about using Cloud SQL Studio, see Manage your data using Cloud SQL Studio.

When you clone your zonal instance, you can now specify a preferred zone for the instance. You can also specify preferred primary and secondary zones for your regional instance. If the zones for your instance go down in the future, then Cloud SQL can assign the preferred zones to the instance, and you don't experience downtime. For more information, see Clone instances.

Gemini in Databases assistance in Cloud SQL for MySQL is now available in Preview for query insights, system insights, index advisor, and active queries. You can use Gemini assistance to help you observe and troubleshoot your Cloud SQL resources. For more information, see Observe and troubleshoot with Gemini assistance.

You can now use the gcloud CLI or the Cloud SQL Admin API to switch the storage location of transaction logs used for point-in-time recovery (PITR) on your instance from disk to Cloud Storage. For more information, see Use point-in-time recovery and Switch transaction log storage to Cloud Storage.

Migrating your external MySQL 5.7 and 8.0 databases into Cloud SQL for MySQL by using Percona XtraBackup physical files is now generally available (GA).

For more information, see Migrate to Cloud SQL from an XtraBackup physical file.

IAM group authentication is now generally available (GA) for Cloud SQL for MySQL. You can add IAM groups to Cloud SQL instances and manage database access at the group level. To use IAM group authentication, you must have [MySQL version].R20230909.02_00 or later installed on your instance.

You can now create custom organization policies for Cloud SQL instances. For more information, see Add custom organization policies.

Cloud SQL Studio is now generally available. For more information, see Manage your data using Cloud SQL Studio.

You can now search for and manage your Cloud SQL resources by using Dataplex Catalog. For more information about the integration of Cloud SQL and Dataplex Catalog, see Manage your Cloud SQL resources using Dataplex Catalog.

Cloud SQL Enterprise Plus edition now supports the southamerica-west1 (Santiago) region.

You can now use the gcloud sql instances describe command or the SQL Admin API to retrieve a list of database versions that are available to your MySQL instance for upgrade. For more information, see Plan a major version upgrade and Upgrade the database minor version.

Cloud SQL for MySQL now supports minor version 8.0.37. To upgrade your existing instance to the new version, see Upgrade the database minor version.

You can now choose to receive a maintenance notification 5 weeks before the maintenance update of your Cloud SQL instance is scheduled to occur. This option is named Week 5.

In addition, some labels in the Google Cloud Console have been renamed to align with this new option:

• Order of update is renamed to Maintenance timing
• Earlier is renamed to Week 1
• Later is renamed to Week 2

For more information, see Maintenance settings and Find and set maintenance windows.

The following Gemini in Databases features are now available in Public Preview:

• Database Center: an AI-assisted dashboard that gives you one centralized view across your entire database fleet.
• Cloud SQL Studio: lets authorized users interact directly with the SQL database and run SQL queries from the Google Cloud console to access and manipulate data.
• Monitor active queries: monitor and troubleshoot the queries that are active in your database.
• Index advisor: a fully managed index advisor that tracks the queries your database handles regularly.
• 4-week query metric retention in the Query Insights dashboard.
• 17 new database insight recommendations.

To learn how to enable and activate Gemini in Databases, see Set up Gemini in Databases.

Cloud SQL for MySQL now supports the storage of vector embeddings in MySQL 8.0.36 and later databases. To use this feature, update your instance to MySQL 8.0.36.R20240401.03_00 or later.

After you store vector embeddings in your database, you can then perform K-nearest neighbor (KNN) searches on the dataset along with the rest of your data. Cloud SQL for MySQL also supports the creation of vector search indexes for several different index types using approximate nearest neighbor (ANN) search.

For more information, see Working with vector embeddings using Cloud SQL for MySQL. This feature is in Preview.

Cloud SQL Enterprise Plus edition primary instances with high availability (HA) now require less than one second of downtime for planned maintenance.

For Cloud SQL Enterprise Plus edition, you can now use advanced disaster recovery (DR) to simplify recovery and fallback processes after you perform a cross-regional failover. With advanced DR, you can:

• Designate a cross-region disaster recovery (DR) replica
• Perform replica failover
• Restore your original deployment by using zero data loss switchover

You can also use switchover to simulate disaster recovery without data loss.

For more information, see Advanced disaster recovery (DR) and Use advanced disaster recovery (DR). This feature is in Preview.

You can now migrate your external MySQL 5.7 and 8.0 databases into Cloud SQL for MySQL by using Percona XtraBackup physical files. This feature is in Preview.

For more information, see Migrate to Cloud SQL from an XtraBackup physical file.

You can now scale up the compute size (vCPU, memory) of a Cloud SQL Enterprise Plus edition primary instance with near-zero downtime.

You can now simulate a planned maintenance update with near-zero downtime on your Cloud SQL Enterprise Plus primary instance without updating your database. For more information, see About maintenance on Cloud SQL instances.

Private Service Connect now includes support for cross-region read replicas. You can also choose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances. Both features are in GA.

Cloud SQL Enterprise Plus edition now supports the me-central2 (Dammam) region.

You can now upgrade network architecture for your HA-enabled instances in a region, even if you have multiple instances in your network and region. For more information, see Upgrade an instance to the new network architecture.

Cloud SQL now automatically updates your read replicas when you perform self-service maintenance on the primary instance. For more information, see Self-service maintenance.

Cloud SQL now supports near-zero downtime planned maintenance on HA-enabled Cloud SQL Enterprise Plus instances with all combinations of public IP connectivity.

Cloud SQL for MySQL now supports minor version 8.0.36. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Private Service Connect now includes support for cross-region read replicas. You can also choose an availability type (REGIONAL or ZONAL) for Private Service Connect-enabled instances. Both features are in Preview.

For more information, see Connect to an instance using Private Service Connect.

Support for africa-south1 (Johannesburg) region.

You can now use the MySQL Shell dumpInstance and loadDump utilities to export and import data for multiple files in parallel. For more information, see Export and import files in parallel.

Cloud SQL Enterprise Plus edition now supports the following regions:

• asia-northeast2 (Osaka)
• asia-south2 (Delhi)
• europe-north1 (Finland)
• europe-southwest1 (Madrid)
• us-east5 (Columbus)
• us-south1 (Dallas)

Cloud SQL for MySQL now supports setting microsecond time periods for the following flag on MySQL 5.7 and MySQL 8.0:

• innodb_flush_log_at_timeout

For more information about this flag, see supported flags.

You can now specify the SSL mode of your Cloud SQL for MySQL instances. To use SSL mode, you must use maintenance version [MySQL version].R20230909.02_00 or later. For more information, see Enforce SSL/TLS encryption.

Cloud SQL for MySQL now supports the following flags for MySQL 8.0:

• innodb_buffer_pool_dump_now
• innodb_buffer_pool_load_abort
• innodb_buffer_pool_load_now

For more information about these flags, see supported flags.

Cloud SQL Enterprise Plus edition now supports the following regions:

• europe-west8 (Milan)
• europe-west12 (Turin)
• us-west4 (Las Vegas)

You can now use Database Migration Service to migrate data to an existing Cloud SQL instance that was created using Terraform or other Infrastructure-As-Code (IaC) Tools.

You can now use the cloudsql_ignore_innodb_encryption flag to ignore InnoDB table encryption when you migrate instances to Cloud SQL. The flag is supported in MySQL 8.0 for Cloud SQL. For more information, see Supported flags.

You can now upgrade your Cloud SQL instances to use the new network architecture to get additional capabilities not available in the old network architecture. For more information, see Upgrade an instance to the new network architecture.

You can now configure Cloud SQL for MySQL instances for IAM group authentication. IAM group authentication requires MySQL 8.0 and R20230909.02_00 or later. This feature is in Preview.

The rollout of the following MySQL versions is currently underway:

MySQL 5.7.43 is upgraded to MySQL 5.7.44. For more information, see MySQL 5.7 Release Notes.

If you use a maintenance window, then the updates to the minor versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks. The new maintenance version is [MySQL version].R20231105.01_00. The details of the security fixes applied as part of this release are published in the MySQL maintenance changelog.

To learn how to check your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

Cloud SQL now supports migrating data to an instance that already exists. You can create the instance by using Terraform or other Infrastructure-As-Code (IaC) Tools. After creating the instance, use the demote API to migrate data to it. This API demotes an existing standalone instance to be a Cloud SQL read replica for an external database server.

Cloud SQL for MySQL now supports minor version 8.0.35. To upgrade your existing instance to the new version, see Upgrade the database minor version.

You can now upgrade Enterprise edition instances to Enterprise Plus edition in place with minimal disruption. Similarly, you can also switch from Enterprise Plus edition to Enterprise edition in place. For more information, see Upgrade an instance by using in-place upgrade.

Cloud SQL Enterprise Plus edition now supports asia-southeast2 (Jakarta).

Cloud SQL supports InnoDB page compression for MySQL 5.7 and MySQL 8.0 and later.

Cloud SQL supports the preview version of the enable-high-availability recommender. This service proactively generates recommendations that help you bring your important instances within SLA by providing data redundancy. This might be helpful during a zonal outage or when an instance runs out of memory. For more information, see Improve instance reliability by enabling high availability.

All Cloud SQL for MySQL Enterprise Plus edition instances now support up to 35 days of retained transaction logs for point-in-time recovery.

The rollout of the following minor version is currently underway:

MySQL 5.7.42 is upgraded to MySQL 5.7.43. For more information, see MySQL 5.7 Release Notes.

If you use a maintenance window, then the updates to the minor versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks. The new maintenance version is [MySQL version].R20230909.02_00. The details of the security fixes applied as part of this release will be published in the MySQL maintenance changelog.

To learn how to check your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.

Support for me-central2 (Dammam) region.

Support for europe-west10 (Berlin) region.

Private Service Connect is now GA for Cloud SQL for MySQL. This solution allows you to connect to a Cloud SQL instance from multiple VPC networks that belong to different groups, teams, projects, or organizations.

Cloud SQL Enterprise Plus edition now supports four new regions:

• europe-central2 (Warsaw)
• europe-west9 (Paris)
• southamerica-east1 (San Paulo)
• us-west1 (Oregon)

Cloud SQL for MySQL now supports minor version 8.0.34. To upgrade your existing instance to the new version, see Upgrade the database minor version.

You can now re-encrypt an existing Cloud SQL CMEK-enabled primary instance or replica with a new primary key version.

You can now retain up to 35 days of retention logs for your Cloud SQL for MySQL Enterprise Plus edition instances when using point-in-time recovery.

Cloud SQL for MySQL now supports storage of point-in-time recovery logs in Cloud storage.

Cloud SQL Enterprise Plus edition now supports the asia-northeast3 (Seoul) region.

You can now upgrade a Cloud SQL for MySQL instance to Cloud SQL Enterprise Plus edition by using IP allowlists and VPC Peering.

Cloud SQL now supports multiple categories of API rate quotas. Rate quotas for each category are imposed per minute, per project, per region, and per user. For more information about rate quotas for each category, see Quotas and limits.

The Cloud SQL Node.js Language Connector is now available for public preview.

You can now migrate large MySQL databases from external sources to Cloud SQL for MySQL faster using Database Migration Service.

Cloud SQL now supports default maintenance windows for your instances. With this release, an instance without a user-specified maintenance window is maintained outside of the typical business hours for the time zone that the instance is deployed in.

Cloud SQL now offers two editions of Cloud SQL to support your various business and application needs: Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition. Each edition provides different performance and availability characteristics to meet the needs of your applications.

Cloud SQL Editions are only available for Cloud SQL for MySQL and Cloud SQL for PostgreSQL.

For more information about Cloud SQL editions, see Introduction to Cloud SQL editions.

Cloud SQL now supports cancelling the import and export of data into Cloud SQL for MySQL instances.

MySQL 5.7.40 has been upgraded to 5.7.42. For more information, see MySQL 5.7 release notes.

Cloud SQL for MySQL now supports up to 500,000 tables for instances that meet the minimum hardware requirements of 32+ cores and 200G+ memory. For more information, see table limit.

Cloud SQL now supports non-RFC 1918 IP address ranges, including privately used public IP addresses. This enables you to create instances and replicas in a non-RFC 1918 IP address range. Additionally, you can connect to an instance from an application that is running in a non-RFC 1918 IP address range.

For our preferred partners and allowlisted customers, Private Service Connect is now available. This solution allows you to connect to a Cloud SQL instance from multiple VPC networks that belong to different groups, teams, projects, or organizations. To use Private Service Connect, contact your Technical Account Manager.

The Cloud SQL System insights dashboard helps you detect and analyze system performance problems.

Cloud SQL for MySQL now supports minor version 8.0.33. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Cloud SQL for MySQL has launched two database flags that impact the Cloud SQL SLA: innodb_flush_log_at_trx_commit and sync_binlog. For more information about these flags, see supported flags.

The Cloud SQL Proxy Operator is now generally available. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

Cloud SQL for MySQL now supports 40+ new database flags. See supported flags for more information.

Cascading Replicas is now generally available when migrating from external servers. You can now configure migrated replicas to have read replicas under them before promoting them to primary replica. To learn more, see External Server Cascading Replicas.

Support for me-central1 (Doha) region.

The changes in the September 15, 2022 Release Notes entry for read replica maintenance are now available. Cloud SQL read replicas follow the maintenance settings for the primary instance, including the maintenance window, rescheduling, and the deny maintenance period. During the maintenance event, Cloud SQL maintains the replicas before maintaining the primary instance. For more information, see How does maintenance affect read replicas?

Cloud SQL for MySQL now supports minor version 8.0.32. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Support for europe-west12 (Turin) region.

Cloud SQL for MySQL now supports 106 new database flags. See supported flags for more information.

Cloud SQL now supports the ability to get details for a Cloud SQL user for a database instance using the API or gcloud. To learn more about the new method, see Cloud SQL Admin API REST Resource.

The Cloud SQL Proxy Operator is now available in public preview. The Cloud SQL Proxy Operator is an open-source Kubernetes operator that automates connecting workloads in a GKE cluster to Cloud SQL databases. To learn more about the Cloud SQL Proxy Operator, see About the Cloud SQL Proxy Operator.

The Cloud SQL Auth proxy is a utility for ensuring secure connections to your Cloud SQL instances. The v2 release offers improvements in performance, stability, and telemetry. Among the new features, there's support for:

• Metrics and tracing with Cloud Monitoring and Cloud Trace
• Support for Prometheus
• Service account impersonation
• Separate Dialer functionality released as the Cloud SQL Go Connector
• Configuration with environment variables
• Fully POSIX-compliant flags

We recommend all customers upgrade to v2 and have released a migration guide. For more information, see Cloud SQL Auth proxy.

Cloud SQL supports the preview version of the Underprovisioned instance recommender. This service helps you avoid bottlenecks from high CPU and memory usage and minimize the likelihood of out-of-memory events. It gives you recommendations to resize your instances to a machine tier that better suits your workload.

Cloud SQL now supports viewing an audit log for an automated backup of an instance to verify whether the backup is completed successfully. You can also configure a log-based alert so that a user can be notified of the backup's status.

Cloud SQL for MySQL now supports using the lower_case_table_names flag for MySQL 8.0. For more information, see Configure database flags.

Cloud SQL for MySQL now supports minor version 8.0.31. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Cloud SQL for MySQL now supports using the lower_case_table_names flag for MySQL 8.0. For more information, see Configure database flags.

Automatic IAM database authentication for Cloud SQL for MySQL is now available. To get started using automatic IAM database authentication, see Cloud SQL IAM database authentication.

MySQL 5.7.38 has been upgraded to 5.7.39. For more information, see MySQL 5.7 release notes.

You can now allow other Google Cloud services, such as BigQuery, to access data in Cloud SQL for MySQL and make queries against this data over a private connection. For more information, see Create instances.

Cloud SQL supports the preview version of the following recommenders that help you optimize your instance's performance:

• High number of open tables recommender: Optimize the performance of your instance by increasing the size of table open cache for the Cloud SQL instances that have the number of open tables equal to the table open cache and keep opening too many tables concurrently
• High number of tables recommender: Optimize the performance of your instance by reducing the number of tables for the Cloud SQL instances whose table count is too high and close to the SLA limit.

Terraform is supported when you use self-service maintenance.

Query insights is now generally available. Query insights helps you detect, diagnose, and prevent query performance problems for Cloud SQL databases. It provides self-service, intuitive monitoring, and diagnostic information that goes beyond detection to help you to identify the root cause of performance problems. To learn more, see Use Query insights to improve query performance.

Cloud SQL allows the re-use of an instance name immediately after the instance is deleted. For more information, see the Cloud SQL for MySQL FAQ.

Cloud SQL read replicas now follow the maintenance settings for the primary instance, including the maintenance window, rescheduling, and the deny maintenance period. During the maintenance event, Cloud SQL maintains the replicas before maintaining the primary instance. For more information, see How does maintenance affect read replicas?

Support for me-west1 (Tel Aviv).

MySQL 5.7.37 has been upgraded to 5.7.38. For more information, see MySQL 5.7 release notes.

The In-place Major Version Upgrade feature is now generally available for Cloud SQL for MySQL.

Cascading Replicas is now generally available for Cloud SQL. Customers can now configure PostgreSQL and MySQL for Cloud SQL read replicas to have read replicas under them.

Cloud SQL for MySQL now supports minor version 8.0.30. To upgrade your existing instance to the new version, see Upgrade the database minor version.

By enabling instance deletion protection, you can prevent the accidental removal of Cloud SQL instances. This functionality is generally available.

For more information, see Prevent deletion of an instance.

For enhanced security with built-in authentication, Cloud SQL now lets you set password policies at the instance and user levels.

You can enable high availability for read replicas. See Disaster recovery for additional information about the use of high-availability replicas in a disaster recovery configuration.

You can create external server replicas with HA enabled.

Cloud SQL for MySQL now supports setting timezone names as values for the time_zone parameter. Refer to the Cloud SQL documentation for a list of supported timezone names.

A second June maintenance changelog is now available. For more information, use the links at Maintenance changelog.

Cloud SQL for MySQL supports in-place major version upgrades in Preview. You can upgrade your instance's major version to a more recent version. For more information, see Upgrade the database major version in-place.

Cloud SQL now supports faster machine type changes, with connectivity dropping to less than 60 seconds. For more information, see Impact of changing instance settings.

MySQL 5.7.36 has been upgraded to 5.7.37.

The June maintenance changelog is now available. For more information, use the links at Maintenance changelog.

An addendum to the May maintenance changelog shows additional security patches. For more information, use the links at Maintenance changelog.

Support for us-south1 (Dallas).

Cloud SQL for MySQL now supports minor version 8.0.29. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Support for us-east5 (Columbus).

New maintenance versions are now available through self-service maintenance. See the maintenance changelog to learn more about these new maintenance versions.

Support for europe-west9 (Paris).

New maintenance versions are now available through self-service maintenance. See the maintenance changelog to learn more about these new maintenance versions.

MySQL 8.0 is now the default major database version for Cloud SQL for MySQL.

The following Cloud SQL recommenders that help you optimize your database costs are now generally available:

• Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.

• Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

You can now accept a maintenance update on your instance outside of the normal flow of scheduled maintenance.

While Cloud SQL schedules maintenance updates once every few months to ensure you have the latest maintenance version, you might want to use self-service maintenance if:

• You need an update sooner than your next scheduled maintenance event.
• You want to catch up to the latest maintenance version after skipping your most recent scheduled maintenance event.
• You want to gain more control over when maintenance is applied

Cloud SQL now supports maintenance changelogs. Maintenance changelogs provide information about updates available in new maintenance versions, such as database minor version upgrades and patches for security vulnerabilities. For links to current maintenance changelogs for each major database version, see Cloud SQL maintenance changelogs.

Support for europe-west8 region (Milan).

Customer-managed encryption key (CMEK) organization policy constraints are now available in Preview.

• constraints/gcp.restrictNonCmekServices allows you to control which resources require the use of CMEK.
• constraints/gcp.restrictCmekCryptoKeyProjects allows you to control the projects from which a Cloud KMS key can be used to validate requests.

You can use both constraints together to enforce the use of CMEK from allowed projects.

To learn more, see Customer-managed encryption keys (CMEK) organization policies. To add CMEK organization policies now, see Add Cloud SQL organization policies.

Cloud SQL for MySQL now supports minor versions 8.0.27 and 8.0.28. To upgrade your existing instance to the new version, see Upgrade the database minor version.

Cloud SQL for MySQL 8.0.26 is now the default minor version. To upgrade your existing instance to the new version, see Set the MySQL minor version.

If your primary instance uses a private IP address, you can now select an allocated IP range for clones and replicas created from the instance.

Cloud SQL now supports the use of tags on instances. Tags are key-value pairs you can apply to your resources, such as a project or a Cloud SQL instance, which are used for fine-grained access control. To learn more, see Access control with Google Cloud tags. To use tags now, see Attach and manage tags on Cloud SQL instances.

The Key Access Justifications (KAJ) feature is now generally available in Cloud SQL. You can use KAJ as part of Cloud External Key Manager (EKM). KAJ enables you to view the reason for each Cloud EKM request. Additionally, based on the justification provided, you can automatically approve or deny a request. For related information, see the Overview.

You can now see the database minor version when viewing information about an instance. See Database versions and version policies for a list of the latest supported versions.

You can now set or upgrade your minor version for Cloud SQL for MySQL 8.0.

Cloud SQL now supports MySQL 8.0.26. To upgrade your existing instance to the new version, see how to upgrade your minor version.

MySQL 5.7.35 has been upgraded to 5.7.36.

Cloud SQL for MySQL now supports point-in-time recovery using a timestamp. See Point-in-time recovery.

Cloud SQL for MySQL now supports database auditing. Database auditing lets you track specific user actions in the database, such as table updates, read queries, user privilege grants, and others. To learn more, see MySQL database auditing.

Cloud SQL now limits the rate for backup and restore operations on the data disk. For more information, see Backup rate limitations and Restore rate limitations.

Support for southamerica-west1 (Santiago) region.

Access Approval is now GA for Cloud SQL. Access Approval enables you to require explicit approval before Google Support may access your database for support purposes.To learn about access approval, see Overview of Access Approval. To set up access approval now, see the Access Approval Quickstart.

Cloud SQL now supports the ability for you to specify IP CIDR ranges from your VPC network for your Cloud SQL instances allowing you to manage your IP address space better. For more information, see Allocated IP address ranges. To start using this feature now, see Configuring private IP for a new instance.

Cloud SQL supports the preview version of two recommenders that help you optimize your database costs:

• Idle database instance recommender: Identifies idle database instances in your project and provides recommendations about the savings that you can make by shutting them down.

• Overprovisioned database instance recommender: Identifies overprovisioned database instances in your project and provides recommendations about the savings that you can make by rightsizing these instances.

When a database instance is nearly out of storage capacity, it's automatically stopped to prevent the loss of information. For more information, see Stopping an instance.

Cloud SQL for MySQL now supports custom formatting controls for CSVs. For more information on how to select custom characters for field delimiters, quotes, escapes, and other characters in admin exports and imports, see our documentation.

The Cloud SQL out-of-disk recommender is now generally available. This feature proactively generates recommendations that help you reduce the risk of downtime that might be caused by your instances running out of disk space.

Cloud SQL for MySQL now allows you to specify mysqldump options during migration from external servers. For more information, see Configuring Cloud SQL to replicate from an external server and Using a managed import to set up replication from external databases.

Cloud SQL for MySQL now supports using a custom import to set up replication from large external databases. To use this replication option, see Configuring Cloud SQL to replicate from an external server and Using a custom import to set up replication from large external databases.

Cloud SQL now supports IAM Conditions.

You can use IAM Conditions to define and enforce conditional, attribute-based access control for Google Cloud resources, including Cloud SQL instances. See Overview of IAM Conditions for more information.

MySQL 5.7.33 has been upgraded to 5.7.34.

The Cloud SQL Admin API v1 is now generally available. It is and will continue to be compatible with the v1beta4 version. There is no requirement to migrate from v1beta4 to the v1 Admin API.

Support for northamerica-northeast2-a,b,c (Toronto) region.

IAM database authentication for Cloud SQL for MySQL is now generally available. To get started using IAM database authentication, see Cloud SQL IAM database authentication.

Cloud SQL for MySQL now offers stored procedures that you can execute on your instances. You can use stored procedures to add or drop secondary indexes on read replicas. See Cloud SQL stored procedures.

Cloud SQL for MySQL now supports the innodb_flush_log_at_trx_commit flag.

Support for asia-south2 (Delhi) region.

Cloud SQL storage limits are now increased to support up to 64 TB. See Cloud SQL storage limits for more information.

The following MySQL minor versions have been upgraded:

• MySQL 5.6.50 is upgraded to 5.6.51
• MySQL 5.7.32 is upgraded to 5.7.33

Support for australia-southeast2 (Melbourne) region.

Cloud SQL now offers faster maintenance, with connectivity dropping for less than 60 seconds on average.

Cloud SQL for MySQL now supports the MySQL flags expire_logs_days (for MySQL 5.6 and 5.7) and binlog_expire_logs_seconds (for MySQL 8.0). Note that if you enable point-in-time recovery, the expiration period of your binary logs will be determined by the lesser of your transaction log retention period and the value of these flags.

Cloud SQL supports the preview version of the out-of-disk recommender. This feature proactively generates recommendations that help you reduce the risk of downtime that might be caused by your instances running out of disk space. These recommendations can be applied when a Cloud SQL instance is trending towards the storage limit.

Support for europe-central2 (Warsaw ).

Cloud SQL for MySQL now supports the innodb_buffer_pool_size flag. To learn more about how to set this flag, see buffer pool size.

The following MySQL minor versions have been upgraded:

• MySQL 5.6.47 is upgraded to 5.6.50
• MySQL 5.7.25 is upgraded to 5.7.32

Cloud SQL for MySQL now supports flexible instance configurations. Compared to our predefined machine types, flexible instance configurations offer you the extra freedom to configure your instance with the specific number of vCPUs and GB of RAM that fits your workload. To set up a new instance with a flexible instance configuration, see our documentation here.

The Cloud SQL Admin API v1beta4 is now generally available. The URL for the Admin API will continue to refer to v1beta4 for backward compatibility. To start using the Cloud SQL Admin API now, see Using the Cloud SQL Admin API.

Cloud SQL now exposes the metric database/memory/total_usage. This metric provides visibility into the database working set (including buffer cache). You can find this metric in the Metrics explorer within the Monitoring dashboard.

For more information about database/memory/total_usage, see Cloud SQL Metrics.

In Cloud SQL for MySQL, parallel replication is generally available for improving replication performance.

Cloud SQL for MySQL now supports retention settings for automated backups. You can configure retention of your automated backups for shorter or longer periods (1 to 365 days). The default setting remains 7 days.

Cloud SQL for MySQL now supports retention settings for point-in-time recovery. You have the option of retaining logs, used for point-in-time recovery, for shorter periods (1 to 7 days). The default setting is 7 days.

In Cloud SQL for MySQL, 80 supported flags that previously were in beta are now generally available.

Cloud SQL for MySQL supports binary logging on read replicas for MySQL versions 5.7 and 8.0.

Cloud SQL now offers "deny maintenance periods". With deny maintenance periods, you can prevent automatic maintenance from occurring during a specific time period. For example, the end-of-year holiday season is a time of peak load that requires heightened focus on infrastructure stability for many retail businesses. By setting a deny maintenance period from mid-October to mid-January, these businesses can prevent planned upgrades from Cloud SQL during their busiest time of year.

MySQL 5.6.42 is upgraded to 5.6.47.

Cloud SQL has upgraded Replicating from an external server to version 1.1. You can now:

• Replicate from sources where GTID is not enabled.
• Allow Cloud SQL to copy data directly from an external server to a Cloud SQL replica.
• Use new APIs that give you greater control to verify replication requirements, retry after making external server configuration changes, and remove the 30-minute limit for successful connectivity to an external server.

Cloud SQL now offers serverless export. With serverless export, Cloud SQL performs the export from a temporary instance. Offloading the export operation allows databases on the primary instance to continue to serve queries and perform other operations at the usual performance rate.

Cloud SQL for MySQL 8.0 is now generally available. If you have not used MySQL 8.0, familiarize yourself with the What is new in MySQL 8.0 and Changes in MySQL 8.0.

For information about the implementation of MySQL 8.0 on Cloud SQL, see the following topics:

• MySQL 8.0 authentication
• Differences between Cloud SQL and standard MySQL functionality
• Unsupported Cloud SQL feature in MySQL 8.0 for Cloud SQL

To get started using MySQL 8.0 on Cloud SQL, see Creating instances.

Committed use discounts (CUDs) are now available to purchase for Cloud SQL. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With committed use discounts for Cloud SQL, you can earn a deep discount off your cost of use in exchange for committing to continuously use database instances in a particular region for a 1- or 3-year term. See the documentation for more details.

Support for asia-southeast2 region (Jakarta).

MySQL 5.6 minor version is upgraded to 5.6.42. MySQL 5.7 minor version is upgraded to 5.7.25.

Support for us-west4 region (Las Vegas).

Cloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see the Pricing page.

Cloud SQL now supports read replicas in a different region than that of the primary instance, providing additional protection against regional outages and improving read performance by making replicas available closer to your application. To get started, see Cross-region replicas.

Cloud SQL instances using private IP are now accessible across regions, at the regular cross-region network egress cost.

MySQL 5.6.42 is now generally available in Cloud SQL. To start using MySQL 5.6.42, see Creating Instances.

Support for us-west3 region (Salt Lake City).

Support for asia-northeast3 region (Seoul).

Cloud SQL now supports VPC Service Controls, which let you add a service perimeter around the Cloud SQL Admin API and host project for Cloud SQL instances to reduce the risk of data exfiltration. To learn more about using VPC Service Controls with Cloud SQL, see Configuring VPC Service Controls.

You can now use Cloud VPN with Cloud SQL. To get started, see Using a VPN with Cloud SQL.

Connection organization policies for Cloud SQL give you the ability to set policies that control access to and from Cloud SQL instances. To learn more about this feature, see Connection organization policies. To use this feature, see Setting organization policies for Cloud SQL.

Cloud SQL now offers notifications for upcoming maintenance. See the Overview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, see Finding and setting maintenance windows.

Cloud SQL now supports Access Transparency. As part of Google's long-term commitment to security and transparency, you can use Access Transparency, which provides you with logs of actions that Google staff have taken when accessing your data. To learn more about Access Transparency, see the Overview of Access Transparency.

Cloud SQL now supports customer-managed encryption keys (CMEK). With CMEK, you can encrypt Cloud SQL instances using a key you manage. To learn more about CMEK, see the Overview of customer managed encryption keys (CMEK). To start using CMEK, see Using customer-managed encryption keys (CMEK).

Cloud SQL Second Generation MySQL instances have a new high availability (HA) configuration. The new HA configuration, based on Google's Regional Disks, eliminates replication lag and, combined with automatic failover, provides isolation from many types of infrastructure, hardware, and software failures. Regional disks also ensure that all previously committed database transactions are persisted and available after failover, right up to the time of the failure.

The new high availability configuration is the default. You can continue to use the API to create instances with the legacy high availability configuration (using failover replicas) until the upgrade of existing instances occurs in early 2020. To learn how high availability now works for Second Generation MySQL instances, see the Overview of the high availability configuration. To enable high availability on existing instances, or to create new instances with high availability, see Enabling and disabling high availability on an instance.

This release increases the maximum data storage for instances of MySQL (MySQL Second Generation) and PostgreSQL. The maximum data storage is increased from 10,230 GB to 30,720 GB. For Cloud SQL storage limits, see Limits. You can limit your automatic storage increases; see Automatic storage increase limit.

Cloud SQL now allows you to specify a location for backups, and to restrict data to a single region. To learn about custom backup locations, see Custom backup locations. To learn how to set a custom location for a backup, see Setting and viewing a custom location for backups.

Support for asia-northeast2 region (Osaka, Japan).

Support added for 122 MySQL flags and 96 PostgreSQL flags. See Supported PostgreSQL Flags and Supported MySQL Flags.

Support for europe-west6 region (Zürich, Switzerland).

Cloud SQL Second Generation is replacing First Generation. Support for First Generation instances for MySQL is ending March 25th, 2020.

GA support for Private IP connectivity.

Support for asia-east2 region (Hong Kong).

Upgrade to Second Generation generally available for eligible First Generation MySQL instances.

Beta support for private IP (private services access) connectivity.

Support for replication from an external MySQL server to a Cloud SQL Second Generation replica.

Support for us-west2 region (Los Angeles).

Support for connecting from Cloud Functions ^Beta.

Support for europe-north1 region (Finland).

Support for rotating SSL certificates.

Support for asia-southeast1 region (Singapore).

Support for europe-west4 region (Netherlands).

Support for northamerica-northeast1 region (Montréal).

Beta support for the high availability configuration and replication for PostgreSQL instances.

Support for asia-south1 region (Mumbai).

Support for 64-core machine types for MySQL instances and 64 cores for PostgreSQL instances.

Support for southamerica-east1 region (São Paulo).

Support for europe-west3 region (Frankfurt).

Support for labels.

Support for australia-southeast1 region (Sydney).

Support for europe-west2 region (London).

GA support for Second Generation and PostgreSQL instances in version 157.0.0 of the gcloud command-line tool. The beta version is no longer required for these instances.

Support for us-west1 region (Oregon).

Support for us-east4 region (Northern Virginia).

Support for 32-core machine types for MySQL instances.

Support for making MySQL general and slow query log files available through the Stackdriver Log Viewer.

Support for Identity and Access Management (IAM) predefined roles.

Support for administration of users and databases for Second Generation instances in the Google Cloud Console and the Cloud SQL API.

Support for Northeastern Asia Pacific region (asia-northeast1).

Cloud SQL Second Generation General Availability.

• Up to 16 cores and 104 GB RAM.
• SSD or HDD storage option with optional automatic storage increase capability.
• Optional high availability configuration (recommended for all production instances).
• Configurable maintenance window and maintenance timing.
• MySQL compatibility:
  • MySQL 5.6 (5.6.31) and 5.7 (5.7.11)
  • InnoDB storage engine
  • GTID support