# Private Connectivity with GCP

GCP Private Service Connect connects your application VPC to ScyllaDB Cloud
over the Google Cloud backbone, with no VPC peering, no overlapping CIDRs,
and no internet routing.

**Before you begin:** When creating the cluster, select the
**Private Connection** network type. Private Connectivity is supported only
for private clusters.

Additionally, plan your PSC NAT subnet size before creating the cluster. The
subnet cannot be resized after PSC endpoints are attached. See
[Subnet Planning](https://cloud.docs.scylladb.com/stable/cluster-connections/private-connectivity/private-connectivity-gcp/configure-gcp-private-service-connect.md#subnet-planning) in the ScyllaDB Cloud configuration
guide for guidance.

Configuration is split across two guides:

| Guide                                                                                                                                                                                                        | Performed by         | Where                  |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------|
| [Configure GCP Private Service Connect in ScyllaDB Cloud](https://cloud.docs.scylladb.com/stable/cluster-connections/private-connectivity/private-connectivity-gcp/configure-gcp-private-service-connect.md) | ScyllaDB Cloud admin | ScyllaDB Cloud console |
| [Connect Your GCP VPC to ScyllaDB Cloud](https://cloud.docs.scylladb.com/stable/cluster-connections/private-connectivity/private-connectivity-gcp/create-gcp-vpc-endpoint.md)                                | Application team     | GCP console            |

Complete the ScyllaDB Cloud guide first — the GCP guide requires the
**Service Attachment ID** it produces.