Cloud SQL: Concepts of Networking

Cloud SQL provides a managed service for MySQL, PostgreSQL, and SQL Server databases as well as backups, high availability, maintenance, and so much more! In this episode of Networking End to End, Lorin Price discusses networking concepts from implementation and security to connectivity on Cloud SQL. Watch along to learn about the options for deploying Cloud SQL and tips on how to determine who and what can access your Cloud SQL instance.

Chapters
0:00 - Intro
1:10 - Public IP Access patterns
2:17 - Private IP Access patterns
5:35 - Network security considerations
6:04 - Key takeaways

#NetworkingEndToEnd

[patroutjunkie]

Great job you are a natural in front on the camera. Hopefully we can get our IT department to which operations to Google some day. Keep up the great work.

[NFLEagles]

Really appreciate these short quick videos. It took me a long time to finally ingest the non transitive nature of Google Managed services. Our organization utilizes Shared VPC’s all going through a hub to on-prem. I fear that we are reserving available internal IP addressing for some of these PSC and Serverless VPC’s. Would like a video explaining the whether one should be using an unused range within a companies WAN when setting up these various psc, serverless VPC’s, etc. Obviously I know IaaS like compute in a service project will grab an IP from the host project VPC’s and be transitive therefore requiring a unique range.

[angelkern]

Good job Lorin! You speak my language. I'm teaching a Computer Networking course for Penn State this summer. We've had to redesign all of our networking courses because how we network in the cloud is fundamentally changing networking. For example, our on campus laboratories are no longer private IP address ranges behind a firewall...they are all public addresses authenticating to a cloud active directory server. Love this stuff and proud of you!

[vineshpandey]

Could you please share playlist link for network end to end topic.

[rakeshkarthikeyan]

Very useful. Should have mention about the access pattern from serverless to cloud sql

[pran]

so basically if I create a sql instance in the same vpc and set the instance as a private one, i'd have to use a sql proxy that connects the other gcp resources through the vm proxy to the database?