Removing 0.0.0.0/0 as allowed IP from a Google SQL instance production
My PHP app is on a DigitalOcean droplet while my MySQL 8.0 database is on Google Cloud SQL.
I was testing for a while on localhost and hence gave 0.0.0.0/0, but now I don't want any server other than my droplet to connect to the Google Cloud SQL instance.
Can I now safely remove 0.0.0.0/0 ?
Solution
yes it should be safe, and is actually recommended to remove 0.0.0.0/0 from the allowlist.
Once this is removed you will still be able to connect from external IPs not in the whitelist using either the CloudSQL auth proxy or with SSL/TLS certificates
- How to export data from Google BigQuery to PostgreSQL
- How to connect Google Data Studio to Google Cloud SQL
- database connection URI string for GCP cloudsql postgres database?
- Best way to import Google Cloud SQL data into BigQuery
- Creating a CloudSQL IAM user different than logged in IAM user
- How to lower costs of having MySQL db in Google Cloud
- Google Cloud Functions and Cloud SQL - Intermittent Connection Errors & SQL Admin Quota
- Secret Manager with Spring Boot issue
- How to fix mysql access denied on google-cloud-platform compute instance
- In Google Cloud SQL Postgres how do I avoid log_min_messages as not superuser?
- How to simplify and remove overlap in GeoJSON polygons
- ERROR 2005 (HY000): Unknown MySQL server host '[35.232.51.216]' (0) in google cloud SQL client
- How to increase the connection limit for the Google Cloud SQL Postgres database?
- Removing 0.0.0.0/0 as allowed IP from a Google SQL instance production
- How to connect Sequelize to Google Cloud SQL database when I have deployed my Node.JS backend api?
- Does Cloud SQL have a query console or is CLI the only option?
- Connection between Private GKE and Cloud SQL
- Connecting Google App Engine to a Cloud SQL (Prisma) Postgres instance (through Bitbucket CI/CD)
- Why would Mysql return "error Column cannot be null"?
- PostgreSQL autovacuum causing significant performance degradation
- Unable to connect from BigQuery job to Cloud SQL Postgres
- Unable to pip install google.cloud.sql.connector when building docker image
- Trying to find the `recommended dns` data for GCP Cloud SQL instance
- Failing to upgrade postgres 11 instance to postgres 15 instance on Google cloud Sql
- Error "address already in use" when trying to connect to google cloud SQL using cloud-sql-connector
- Using SQLAlchemy to migrate databases (sqlite to Postgres CloudSQL)
- Local MySQLdb connection fails with AttributeError for paramstyle when running GAE development server
- Error with Django application on Cloud Run using Cloud SQL PostgreSQL DB - cannot connect to database
- Cloud Function cannot connect to Cloud SQL with "upstream request timeout"
- Create CloudSQL instance without public IP