Internal communication between Cloud runs and cloud SQL

[mmilillo]

hello everyone!

I'm working with several microservices, these communicate via internal VPC and some of them also need access to Cloud SQL. 

I'm not sure if my setup is efficient, I have the following configuration:

Cloud Run microservices:
- allows internal traffic and traffic from Cloud Load Balancing.
- Route all traffic through the serverless VPC connector
- Cloud NAT so that Cloud run can be routed to external resources (identity providers, payments platforms, etc)

Cloud SQL
- it has an internal IP so that cloud run can access it internally.


the escenar is the same as https://www.googlecloudcommunity.com/gc/Serverless/Cloud-run-egress-traffic-to-internet/td-p/502062 so i have the same configuration. But my question is, the serverless VPC connector has a usage quota, is not the pricing of send all trafic to the Cloud SQL DB via VCP connector so high? is there other configuration recomendated for my use case?

Thanks in advance!

[anjelisa]

Hello @mmilillo,

Welcome to Google Cloud Community!

Serverless VPC Access is charged by the number of connector instances and depends on the machine type used. Refer to this documentation as to how the Serverless VPC Access is priced. 

You can view the estimated throughput and cost for each machine type through here: Throughput and Scaling.

Here is also a helpful documentation for connecting to a Cloud SQL instance from a service running in Cloud Run.

Hope this helps.