Cloud SQL for MySQL instances will change to per vCPU and GB of RAM pricing, similar to PostgreSQL and SQL Server instances.
Google now offers flexible instance configurations for Google Cloud SQL for MySQL. Starting March 1, 2021, your invoice descriptions will change and if you have highmem MySQL instances, you will see a slight price decrease.
The following changes will appear on your invoice as noted in the table below:
| Old | New |
| vCPU with predefined machine types 1 vCPU + 3.75GB |
vCPU and RAM line items |
What do you need to know?
Cloud SQL for MySQL instances will change to per vCPU and GB of RAM pricing, similar to PostgreSQL and SQL Server instances.
What this means to you:
- Dedicated vCPU core MySQL instances will no longer be restricted to predefined machine types. For example:
db-n1-standard-2 - More vCPU and RAM options will be available.
If you continue to use predefined machine types or have scripts that rely on existing API calls and CLI commands:
- You will continue to receive support for all existing machine types.
- You don’t have to update your scripts unless you want to configure instances with vCPU and RAM levels that differ from predefined machine types.
What do I need to do?
No action is required to change your scripts. However, we recommend that you begin using the new API and CLI if you use Cloud SQL for MySQL when creating and editing instances as well as updating your Terraform variables with the right machine types. Please open a support ticket if you need us to do this for you.