👀 Views: 41 💬 Answers: 1 📅 Created: 2025-06-11

gcp cloud-run cloud-sql pymysql vpc Python

I'm working with an scenario where my GCP Cloud Run service fails to connect to a private Cloud SQL instance, resulting in a 'Connection Timeout' behavior. I've set up the Cloud SQL instance with private IP and enabled the necessary API services. The Cloud Run service is deployed in the same VPC as the Cloud SQL instance, with the appropriate IAM roles assigned to the service account. In my `Dockerfile`, I'm using the following: ```dockerfile FROM gcr.io/google.com/cloudsdktool/cloud-sdk:latest COPY . /app WORKDIR /app RUN pip install -r requirements.txt CMD ["python", "app.py"] ``` I’m trying to connect to the Cloud SQL instance using the `pymysql` library in Python: ```python import pymysql def connect_to_db(): connection = pymysql.connect( host='YOUR_CLOUD_SQL_PRIVATE_IP', user='USERNAME', password='PASSWORD', db='DATABASE', cursorclass=pymysql.cursors.DictCursor, connect_timeout=5 ) return connection ``` When I run my Cloud Run service, I see the following behavior in the logs: `OperationalError: (pymysql.err.OperationalError) (2003, "need to connect to MySQL server on 'YOUR_CLOUD_SQL_PRIVATE_IP' (timed out)")`. I've checked that the Cloud SQL instance is up and running and that the networking settings are correctly configured. I also verified that my Cloud Run service has the `Cloud SQL Client` role attached to its service account. I attempted to troubleshoot this by configuring a VPC connector and ensuring it was linked to the Cloud Run service. However, I still encounter the same timeout scenario. Is there anything I might be missing in the configuration, or any common pitfalls that could lead to this connection timeout? Any insights would be greatly appreciated.