GCP Private Service Connect

GCP Private Service Connect (PSC) lets Slateo connect to GCP-hosted databases without exposing your services to the public internet. Use this when your organization requires private network paths for production data access.

---

Overview

Use this guide if your database is hosted in Google Cloud and you want private connectivity between Slateo and your environment.

Typical use cases:

• Private connectivity for production PostgreSQL or MySQL deployments on GCP
• Internal service endpoints behind Google Cloud load balancers
• Security policies that prohibit public ingress

---

Configure

1) Prepare your service endpoint in GCP

Create or identify the producer service you want Slateo to reach (for example, a database endpoint exposed through an internal load balancer).

Confirm:

• The target is reachable from your internal VPC
• TLS is enabled end-to-end
• The service account/user Slateo will use has read-only permissions

2) Create Private Service Connect endpoint resources

Set up PSC resources in your GCP project according to your network architecture and security requirements.

At minimum, capture:

• Project ID and region
• PSC endpoint/service attachment details
• Allowed principals/projects
• DNS hostnames that Slateo should use

3) Share connection details with Slateo

Provide your Slateo account manager with:

• Endpoint and DNS details
• Region and networking constraints
• Required allowlists/authorization identifiers
• Database hostname, port, and database name

Slateo will complete provider-side setup and confirm when the connection is ready for testing.

4) Configure the database in Slateo

In Slateo:

1. Go to Settings -> Databases
2. Create or edit your database connection
3. Use the private hostname provided for the PSC path
4. Click Test connection and save

---

Usage

After setup completes:

• Use the connection like any other Slateo database
• Continue using read-only credentials
• Monitor query activity through your existing database audit logs

For workspace setup details, see the Admin Setup Guide.

---

FAQ

Is PSC required for GCP databases?

No. You can also use direct connections or SSH tunnel patterns, but PSC is recommended for stricter network isolation in production.

Can I use PSC and IP allowlisting together?

Yes. Many teams combine private networking with restrictive allowlists and read-only credentials for layered security.

Do I still need SSL/TLS when using PSC?

Yes. Private networking does not replace transport encryption. Keep TLS enabled for all database connections.

---

Related documentation

• AWS PrivateLink
• Connect your database
• Admin Setup Guide