We have a customer deployment using PSC (Private Service Connect) to achieve secure private connectivity to a Atlas Mongo SaaS instance. Below are my questions
-
Is this the best possible option in terms of cost , security? We are seeing high costs associated with this setup as shown below. Also the pricing page for PSC is not clear, I do not see any LB deployed in GCP and no consumed data charge. Not sure what the 36,000 hours indicate (please see below screenshot)
-
Also looking at the PSC console in GCP dashboard , I see 50 published endpoints, is this normal?
From my understanding, PSC is more secure and expensive.
It likely means:
You have 50 PSC endpoints
Used for ~30 days (30 days x 24 hours x 50 endpoints = 36,000 hours)
So even if no LB is visible, GCP internally provisions forwarding rules and network plumbing for PSC, and those carry per-hour charges, even for idle connections.
? PSC Pricing Summary (as of 2025):
$0.01/hour per forwarding rule (endpoint) → ~$7.30/month per endpoint
$0.01/GB of data processed (egress from consumer VPC)
Not sure. I knew that earlier, Atlas Mongo supported VPC peering to the AWS environment. We can try that, or we can reduce the PSC endpoints.
https://www.mongodb.com/docs/atlas/security-vpc-peering/
Thanks,
GCP Consultant
Darwin Vinoth.
Linkedin
1 Like
