Supported environments
API means the profile adapts origin API behavior. Infrastructure means the profile changes provisioned resources or documents a target-native alternative without promising an origin API endpoint. Check the operation and capability tables for the behavior your application depends on.
How the targets compare
Each row compares a capability of Cloud SQL for MySQL with its adaptation on each target. A dash means this profile does not state the capability for that target.Cloud Adapter
On AWS
RDS MySQL
Cloud SQL for MySQL becomes an RDS MySQL instance. The application keeps using the MySQL protocol, with regional high availability mapped to Multi-AZ and point-in-time recovery provided by RDS.
Connection setup and instance changes
The source management API and the database protocol serve different purposes. The adapter creates and configures the target instance and handles the connector certificate exchange; SQL then uses the target engine. Verify the complete connection sequence with the actual client library, including token acquisition and certificate renewal.Moving the database
Provisioning a target instance does not copy data, users, or backup history. Transfer the required database state, stop or coordinate writes for the final cutover, and test reconnection after target failover. Select the target engine version and settings together with the application’s extension and authentication requirements.Compatibility differences
Google’s connector libraries and Auth Proxy request a short-lived client certificate before connecting. The adapter handles that handshake on the target. Database users are created with SQL because RDS has no equivalent managed users API.On Azure
MySQL Flexible Server
Cloud SQL for MySQL becomes an Azure MySQL Flexible Server. The application keeps the MySQL protocol. Database flags become server parameters, and regional high availability becomes zone-redundant deployment.