Skip to main content

Google Cloud SQL (MySQL)

Google Cloud SQL MySQL is a fully-managed database service that provides MySQL databases in the cloud, offering high availability, automatic backups, and seamless scaling capabilities for applications requiring reliable MySQL database infrastructure.

Google Cloud SQL (MySQL) icon

Power end-to-end data operations for your Google Cloud SQL (MySQL) database with Nexla. Our bi-directional Google Cloud SQL (MySQL) connector makes it easy to ingest, transform, and validate data from Google Cloud SQL (MySQL) and to deliver data to any Google Cloud SQL (MySQL) location – all with no coding required. Nexla organizes data from raw database queries or tables into ready-to-use data products you can manage and move at scale. With comprehensive monitoring, lineage tracking, and robust access controls, Nexla keeps your Google Cloud SQL (MySQL) workflows fast, secure, and fully governed.

Features

Type: Database

SourceDestination

  • Flexible ETL/ELT/CDC/Replication: Seamlessly read and write data using any integration style that fits your needs
  • Real-time data change capture for always up-to-date insights and continuous scalability
  • No-code database connectivity as source or destination, with automatic data product creation
  • Data as a Service: Instantly deliver secure, high-performance API access to your database data

Prerequisites​

Three Google Cloud SQL connectors are available in Nexla, allowing users to connect to any Cloud SQL instance. This page provides instructions for using the Google Cloud SQL MySQL connector for instances of Cloud SQL used with MySQL databases.

To connect to a different type of Google Cloud SQL instance, see Google Cloud SQL (PostgreSQL) or Google Cloud SQL (SQLServer).

Authenticate​

This section provides step-by-step instructions for creating a new Cloud SQL MySQL credential that will allow Nexla to authenticate to your Cloud SQL instance.

  • To create a new Cloud SQL MySQL credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Cloud SQL MySQL

CloudSQL_MySQL_Cred.png

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource Descriptions

    Resource descriptions should provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Details​

  1. Select the authentication method that will be used to connect to the Cloud SQL instance from the Authentication Type pulldown menu, and follow the corresponding instructions in the box below to configure associated credential settings.

  • Host – Hostname of the database server (formatted as an IP address or text in the format company.domain.com)

  • Port – Number of the port that will be used to connect to Cloud SQL

  • Username – Username for accessing the Cloud SQL instance

  • Password – Password associated with the Cloud SQL username

  • Database Name – Name of the Cloud SQL database that will be accessed with this credential

    • To locate the database name, navigate to the Cloud SQL instance in the Google Cloud console, and select the Databases tab. The database name will be listed in the Database Name column.

Advanced Settings​

Optional

For Cloud SQL MySQL credentials, advanced settings are available to configure how Nexla will access the Cloud SQL instance. These settings are optional and can be configured as needed.

  • To access advanced settings for the credential, expand the Advanced Settings section at the bottom of the overlay. Instructions for configuring the available connection settings are provided in the box below.

Advanced Credential Settings
Cloud SQL MySQL

If the Cloud SQL instance is not publicly accessible, Nexla can be configured to connect to the instance via the SSH protocol. When this option is selected, Nexla will connect to a bastion host via SSH, and the database connection will then be provided through the SSH host.

  • To enable SSH tunneling for Cloud SQL connections with this credential, check the box next to Requires SSH Tunnel for Access?, and enter the following information in the displayed fields:

    • SSH Tunnel Host – Hostname or IP address of the bastion host running the SSH tunnel server that has access to the database

    • SSH Tunnel Port – Tunnel bastion host port that will be accessed for connection

    • Username for Tunnel – SSH username created for Nexla in the bastion host (typically set as nexla)

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source​

To ingest data from a Google Cloud SQL location, follow the instructions in Section 2 of Common Setup for Databases & Data Warehouses.

Use as a destination​

To send data to a Google Cloud SQL location, follow the instructions in Section 3 of Common Setup for Databases & Data Warehouses.