Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Example Systemd file for starting cloud sql proxy at system start
  1. We assume you already read this: https://cloud.google.com/sql/docs/mysql/connect-external-app#proxy and created a service account for Cloud SQL Client
  2. Download cloud_sql_proxy to /usr/local/bin
  3. Make the following folders, all chown to root:root :
  4. /var/run/cloud-sql-proxy
  5. /var/local/cloud-sql-proxy
  6. Copy downloaded credential json file inside /var/local/cloud-sql-proxy, make sure only root can read as it is credential for connection.
  7. Copy above gist to /lib/systemd/system/cloud-sql-proxy.service
  8. Run systemctl daemon-reload
  9. Run systemctl start cloud-sql-proxy
  10. Profit$$$$
[Install]
WantedBy=multi-user.target
[Unit]
Description=Google Cloud Compute Engine SQL Proxy
Requires=networking.service
After=networking.service
[Service]
Type=simple
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cloud_sql_proxy -dir=/var/run/cloud-sql-proxy -instances=<instance_connection_name>=tcp:5432 -credential_file=/var/local/cloud_sql_proxy/<credential_json>.json
Restart=always
StandardOutput=journal
User=root
@larryzoumas
Copy link

larryzoumas commented Jun 6, 2018

This is cool thank you... but small typo in cloud-sql-proxy.service

-credential_file=/var/local/cloud_sql_proxy/<credential_json>.json

should be:

-credential_file=/var/local/cloud-sql-proxy/<credential_json>.json

@jgngo
Copy link

jgngo commented Jan 14, 2019

For cloud sql proxy to auto-start:

$ sudo systemctl enable cloud-sql-proxy.service

@jgngo
Copy link

jgngo commented Jan 29, 2019

For Centos 7, use the following:

[Install]
WantedBy=multi-user.target

[Unit]
Description=Google Cloud Compute Engine SQL Proxy
Requires=network.target
After=network.target

[Service]
Type=simple
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cloud_sql_proxy -dir=/var/run/cloud-sql-proxy -instances=<instance_connection_name>=tcp:3306 -credential_file=/var/local/cloud-sql-proxy/<credential_json>.json
Restart=always
StandardOutput=journal

@joeswann
Copy link

joeswann commented Jul 24, 2019

If you find that /var/run/cloud-sql-proxy gets deleted on reboot - add this under line 10

RuntimeDirectory=cloud-sql-proxy

@tbrown-payments
Copy link

tbrown-payments commented May 6, 2021

This works for RHEL8/Centos8

[Install]
WantedBy=multi-user.target

[Unit]
Description=Google Cloud Compute Engine SQL Proxy
Requires=network.target
After=network.target

[Service]
Type=simple
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cloud_sql_proxy -dir=/var/run/cloud-sql-proxy -instances=prod-modpress-prj:northamerica-northeast1:prod-modpress-inst=tcp:3306
Restart=always
StandardOutput=journal
User=root

@brokeyourbike
Copy link

brokeyourbike commented Jun 10, 2021

For ubuntu 20.04 this should work:

[Install]
WantedBy=multi-user.target

[Unit]
Description=Google Cloud Compute Engine SQL Proxy
Requires=network.target
After=network.target

[Service]
Type=simple
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cloud_sql_proxy -dir=/var/run/cloud-sql-proxy -instances=<instance_connection_name>=tcp:3306 -credential_file=/var/local/cloud-sql-proxy/<credential_json>.json
Restart=always
StandardOutput=journal
User=root

@rpkamp
Copy link

rpkamp commented Feb 3, 2022

I've found out that Google Cloud SQL proxy has watchdog support, even though I can't find this mentioned anywhere.

What this means is you can change Type=simple to Type=notify and add WatchdogSec=10 and then any time Google Cloud SQL proxy detects a connection error it will stop informing systemd that all is well and systemd will restart it.

This happens for example when Google Cloud SQL rotates SSL certificates. Which doesn't happen often, but it does happen every once in a while. Without using watchdog the service will just keep running but it can't connect anymore. With watchdog the service will be restarted and will reconnect using the new certificates.

Scratch that, it only notifies once started, it doesn't keep pinging to indicate it's still alive :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment