Here are the steps to setup Cloud SQL Proxy on your local machines:
First of all you have to download it. I would recommend putting it at root (
1$~ cd ~/ 2$~ curl -o cloud_sql_proxy https://dl.google.com/cloudsql/cloud_sql_proxy.darwin.amd64 3$~ chmod +x cloud_sql_proxy
A service account is a special type of Google account that belongs to your project. Instead of using your individual user’s credential, you can use service account to authenticate your application.
To set it up, follow these commands. You can replace
"my-proxy-user" to your likings
1$~ gcloud iam service-accounts create proxy-user --display-name "my-proxy-user"
Once you have created it, list it down to get the email of the service account.
1$~ gcloud iam service-accounts list
Next, allow your service account to connect to the Cloud SQL proxy on your behalf. You can do this by giving
Cloud SQL Client role to the service account.
Run the following commands. Replace
[SERVICE_ACCOUNT_EMAIL] with your own Google Project ID and the service account email that you got from the command before.
1$~ gcloud projects add-iam-policy-binding [PROJECT_ID] --member \ 2serviceAccount:[SERVICE_ACCOUNT_EMAIL] --role roles/cloudsql.client
Next, generate a
key.json for authentication to the service account. (I would recommend you to ignore this file in git)
1$~ gcloud iam service-accounts keys create key.json --iam-account [SERVICE_ACCOUNT_EMAIL]
Finally to start the Cloud SQL Proxy, run the following commands. Replace the
[INSTANCE_CONNECTION_NAME] with your own and the
[PORT] based on the database you want to connect to.
1$~ ./cloud_sql_proxy -instances=[INSTANCE_CONNECTION_NAME]=tcp:[PORT] -credential_file=key.json
If everything is working fine, you will get an output similar like this
12020/05/10 22:23:07 Listening on 127.0.0.1:5432 for [INSTANCE_CONNECTION_NAME] 22020/05/10 22:23:07 Ready for new connections
That’s pretty much it. You should be connected to your Cloud SQL from your local machine now.
If you happened to get following error:
1listen tcp 127.0.0.1:5432: bind: address already in use
It’s likely you already have a local database instance running on your local machine that’s using the port
5432 (In this case it’s Postgresql). If this is the case, stop the running instance first.