Use Google Cloud Virtual Private Cloud for secure communication between services
Use Cases and Deployment Scope
Most of the microservices I use are deployed in Cloud Run. I configured a serverless connector for these services to communicate with each other privately. The serverless connector can be configured with min and max number of instances so that it can automatically scale based on workload. Being serverless the cost of using the connector works out low for my use case.
Pros
- Serverless connector helps Cloud Run services to communicate privately.
- Serverless connector supports auto scaling.
- Being serverless, the cost is based on usage for serverless connector.
Cons
- Cannot reduce minimum number of instances than the previously set value. Workaround is to delete the connector and create a new one with a lower minimum number of instances.
- Cannot set minimum number of instances below 2 for a serverless connector.
- The instance and bandwidth options for a serverless connector seem to be too few.
Return on Investment
- Monthly cost for VPC is less compared our other cloud services costs.
- Once set up the VPC can be used for numerous other services without any further changes. There is less operational overhead.
- Seems a more secure way to configure a VPC.
Usability
Alternatives Considered
Amazon Virtual Private Cloud (VPC)
Other Software Used
Amazon Virtual Private Cloud (VPC)




