Google Cloud SQL migration from the first to second generation

Question

1. Google Cloud SQL: after an upgrade SQL from the first generation to second MySQL workbench can’t connect my instance in Cloud. Why? Maybe you need to do instance 5.7 ?

2. Google application Engine: after upgrade SQL from the first generation to second MySQL opening a new WEB application and connect to my project in Cloud, it can’t see my instance. Why?

Answer 1

Any of these three configurations might eventually prevent the connection from GAE:

---

a) If you haven't assigned any public IP address to the instance;

the only option to connect would be: Configuring Serverless VPC Access.

---

b) Confirm and complete the upgrade reads:

If your applications are connecting using the First Generation instance connection name:

<project_id>:<instance_id>

update them to use the Second Generation instance connection name:

<project_id>:<region>:<instance_id>

---

c) Another possible culprit would be the service-account used - and it's assigned roles:

App Engine uses a service account to authorize your connections to Cloud SQL. This service account must have the correct IAM permissions to successfully connect. Unless otherwise configured, the default service account is in the format service-PROJECT_NUMBER@gae-api-prod.google.com.iam.gserviceaccount.com.

---

Authorization with authorized networks is usually not required when connecting from GAE.