VPC in Trusted Cloud versus Google Cloud

Virtual Private Cloud (VPC) provides networking functionality to Compute Engine virtual machine (VM) instances and Google Kubernetes Engine (GKE) clusters. VPC includes networking features such as networks, subnets, IP addresses, routing, and access to Google APIs and services.

This page describes the differences between the Trusted Cloud and Google Cloud versions of VPC.

For more detailed information about VPC, see the VPC overview and the rest of the VPC documentation.

Key differences

There are some differences between the Trusted Cloud version of VPC and the Google Cloud version. If you are already familiar with Google Cloud, we recommend that you review these differences carefully, particularly before designing an application to run on Trusted Cloud. We also recommend reviewing the general differences between Google Cloud and your universe in the Trusted Cloud by S3NS overview.

If you would like to use a particular VPC feature that isn't currently available in Trusted Cloud, contact Trusted Cloud support. To be notified when new features roll out in Trusted Cloud, subscribe to the release notes.

Network

VPC networks
Legacy networks Not available
IP addresses Global external IPv4 addresses aren't available.
Network Service Tiers

Only Premium Tier is available.

Routing Policy-based routes aren't available.
Private Service Connect
  • Automatic DNS configuration isn't available for endpoints with global Google API targets. As a workaround, manually create the DNS entries that you need.
  • Connection propagation for Private Service Connect endpoints isn't available.
  • Endpoints with regional Google APIs targets aren't available.
  • Backends aren't available.
  • Service connection policies and service connectivity automation aren't available.
Private Google Access

The IP addresses for Private Google Access are different:

  • private.googleapis.com:
    • IPv4: 177.222.88.0/30
    • IPv6: 2a13:7500:8302::/64
  • restricted.googleapis.com:
    • IPv4: 177.222.88.4/30
    • IPv6: 2a13:7500:8302:1::/64
Private services access Not available
Bring your own IP address
  • Only v2 prefixes are available in Trusted Cloud.
  • BYOIP IPv6 sub-prefixes in subnet creation mode aren't available in Trusted Cloud.
Network profiles Not available.
Network interfaces Dynamic Network Interfaces aren't available.

Regions and zones

Regions and zones Trusted Cloud has only a single region, though with multiple zones. Multi-region features and cross-region failover aren't supported.

Insights and observability

VPC Flow Logs
  • Flow logs for subnets are available. Flow logs for Cloud VPN and Cloud Interconnect aren't available.
  • The InternetRoutingDetails and GkeDetails records aren't available.

The following information might also affect how you use and design for VPC in Trusted Cloud by S3NS. These guides include general information about working in Trusted Cloud, including documentation, security and access control, billing, tooling, and service usage.

For details about other services and features in Trusted Cloud and their differences from their Google Cloud counterparts, see the product list.

Trusted Cloud guides