Connect App Engine to Cloud SQL via Private IP - Google Cloud Serverless VPC Access 

I have a mide a mistake and corrected it, I will see how many of you can spot it :). If you want to take a challange, please implement this with cloud function.👍

Such a better explanation than the video produced by Google. Subscribed!

Very good and helpful Cloud Advocate !! The only thing is that the red letters on black background was not very clear. Congrats!

Good explanation :)

thank you!!

Hi GK, thanks for sharing this video. Connecting to Cloud SQL from appengine via private IP is the best approach. Let's assume Cloud SQL is already configured with only private IP. Can you please suggest what could be the best approach to connect from cloud shell in this case. And it will be great if you share any sample java project with same scenario. Thanks in advance.

hello sir, is there any way to initiate dataproc workflow-template (spark job workflow) using cloud function or workflows (beta)(cloud workflow)

how can i do it with elastic search in could function ? any help

Thanks

I had a question, I did the exact same thing but "Connector is in a bad state, manual deletion recommended See logs" is always shown, I have used the default, I don't have any overlapping services

How about from Cloud Functions?

BTW I think the error was that you added a 1 at the end of the project name right ?

Hi there, very helpful video. But I'm stuck at a point. After enabling API, when I create connector with exactly same details as explained by you - connector is getting created with an error - 'Connector is in bad state, manual deletion recommended. Region I'm using is asia-south1. Tried multiple times since yesterday, no luck! What can be the possible issue?

Hello GK, can you help with Connecting App Engine Flex Env. to Cloud SQL via Private IP

I think if-else... condition is swapped in main-pip.py.

Don't you lose the advantages of having a private IP address (security) if you set a public IP also ?

Hi GK, I have a doubt, please clear this if possible: I have a cloud run attached with serverless vpc connector and i am using db_host as a connection name instead of cloudsql private IP because my cloudsql instance is enforced with SSL certificates so to bypass this i am using /cloudsql/${connection_name} as a db_host variable to my application, so but my cloudsql instance is having both private and public ip addresses because some reasons, so does cloud run uses private ip to connect to cloudsql or public ip??? Thanks in advance

while creating vpc connector, I am getting error: "Operation failed: Insufficient CPU quota in region." What I do?

wearing AWS t-shirt and Teaching about GCP..

this method is outdated and you have to set ENV_VARIABLES before building cloud run.