Is Serverless VPC Access connector a single point of failure?

1
votes

I am wanting to connect my Cloud Run app to Postgres Cloud SQL instance without assigning the instance a public IP. Seems like the only way to do this is with a Serverless VPC Access connector.

The docs indicate that the Serverless VPC Access connector is billed as 1 e2-micro instance per 100Mbps. Does this indicate that the connector is simply a single e2-micro VM? Is there any redundancy/automated-failover configured behind the scenes?

I can't find any SLA for the Serverless VPC Access and am worried that it could be a single point of failure for my app that brings down all DB connections.

1
google-cloud-platformgoogle-cloud-sqlserverlessgoogle-cloud-run

1 Answers

5
votes

The VPC Access Connector is a Compute Engine instance privately managed by Google Cloud. You are billed per 100Mbit of capacity. The instance size can scale up but not back down. Is this a single point of failure, yes but the service will auto recover. Fault tolerance, recovery time and SLA are not published (AFAIK).

Additional information:

  • The images for the VPC Access Connector instances are from the project serverless-vpc-access-image.
  • These instances use RFC1918 addresses that cannot overlap your VPCs.
  • These instances are basically NAT Gateways and require IP forwarding be allowed constraints/compute.vmCanIPForward.