Private Service Connect endpoints

Related topics

• Private Service Connect endpoints is part of Private Service Connect From the official documentation: “- **Private Service Connect endpoints**: provide a direct connection by mapping an internal IP address in your VPC network to the target multi-region endpoint.”
• gcloud CLI configures Private Service Connect endpoints From the official documentation: “You must use the gcloud CLI or the API to create an endpoint in a service project, and this configuration requires [additional permissions](/vpc/docs/access-regional-google-apis-endpoints#roles-shared-vpc).”
• Private Service Connect endpoints is part of Memorystore From the official documentation: “The cluster's Private Service Connect endpoints aren't affected by maintenance.”
• Private Service Connect endpoints depends on service attachment From the official documentation: “Private Service Connect endpoints that have a regional endpoint or multi-regional endpoint target point to a service attachment that has been created by Google to direct traffic to the service.”
• Private Service Connect endpoints works with Shared VPC From the official documentation: “[Service Project Admins](/vpc/docs/shared-vpc#svc_proj_admins) can create Private Service Connect endpoints in Shared VPC service projects that use IP addresses from [Shared VPC networks](/vpc/docs/shared-vpc#shared_vpc_networks).”
• Shared VPC is an alternative to VPC Network Peering From the official documentation: “We recommend using Shared VPC over using VPC Network Peering because Shared VPC is easier to configure and scale.”
• Cloud Interconnect works with VPC network From the official documentation: “Connects to on-premises networks by using Cloud VPN tunnels and VLAN attachments for Cloud Interconnect.”
• Private Service Connect is an alternative to VPC Network Peering From the official documentation: “Use VPC Network Peering if you need to insert NVAs or if your application doesn't support Private Service Connect”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Cloud Interconnect works with Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
• Memorystore works with Virtual Private Cloud From the official documentation: “This page explains how to set up connectivity for multiple Virtual Private Cloud (VPC) networks and a new Memorystore for Valkey instance.”
• Private Service Connect works with service attachment From the official documentation: “Service attachment is an entity used with Google Cloud [Private Service Connect](/vpc/docs/private-service-connect) to allow service producers (in this case, Apigee) to expose services to consumers (in this case, one or more Cloud projects that you own).”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• Shared VPC is an alternative to Virtual Private Cloud From the official documentation: “From the **Network** drop-down, select a VPC or a Shared VPC network.”
• Shared VPC works with VPC Network Peering From the official documentation: “You can use Shared VPC with clusters based on VPC Network Peering.”
• Cloud Interconnect works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
• Cloud Interconnect works with service attachment From the official documentation: “The service attachment is connected to the on-premises network using Cloud Interconnect.”
• Cloud Interconnect works with Shared VPC From the official documentation: “You can extend one or more of your existing security zones to Google Cloud by provisioning Shared VPC on Google Cloud and connecting it to the existing zone by using Cloud VPN or Cloud Interconnect.”
• Cloud Interconnect is an alternative to VPC Network Peering From the official documentation: “3. Connect your VPC networks with [VPC Network Peering](/vpc/docs/vpc-peering), [Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/overview) or [Cloud VPN](/network-connectivity/docs/vpn/concepts/overview).”
• Cloud Interconnect works with VPC Service Controls From the official documentation: “VPC Service Controls works with either Cloud Interconnect or Cloud VPN to provide additional security for your clusters.”
• Cloud Load Balancing works with Private Service Connect From the official documentation: “By using Private Service Connect with Cloud Load Balancing, as shown in the following diagram, you can achieve two distinct communication paths.”
• Cloud Load Balancing works with service attachment From the official documentation: “The service attachment connects to the workload through Cloud Load Balancing.”
• Cloud Load Balancing works with Shared VPC From the official documentation: “Shared VPC can be used in conjunction with [Cloud Load Balancing](/load-balancing/docs/load-balancing-overview).”
• Memorystore works with Private Service Connect From the official documentation: “Before you can [Delete your Memorystore instance](/memorystore/docs/valkey/multiple-vpcs-user-registered-psc-connection#delete_your_memorystore_for_valkey_instance), you must delete all Private Service Connect connections associated with the instance.”
• Private Service Connect configures service attachment From the official documentation: “You can create a service attachment in Google Cloud, by using the Private Service Connect feature.”
• Private Service Connect works with Shared VPC From the official documentation: “Private Service Connect resources can be deployed in standalone VPC networks or Shared VPC networks.”
• Private Service Connect is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
• Private Service Connect works with Virtual Private Cloud From the official documentation: “[Private Service Connect](https://cloud.google.com/private-service-connect) | Create a private and secure connection from your VPCs to Google, third parties, or your own services.”
• Private Service Connect works with VPC network From the official documentation: “Private Service Connect](/vpc/docs/private-service-connect) lets you create private and secure connections between your VPC networks and a Google Cloud service, such as AlloyDB for PostgreSQL.”
• Private Service Connect is an alternative to VPC network From the official documentation: “In Managed Airflow (Gen 2), you can create environments that [use Private Service Connect](/composer/docs/composer-2/configure-private-service-connect) instead of VPC networks.”
• service attachment is part of Memorystore From the official documentation: “After creating a Memorystore instance, make a note of the two service attachment URIs for your Memorystore instance.”
• service attachment is part of Private Service Connect From the official documentation: “Private Service Connect endpoints, backends, and service attachments can be deployed in host projects or service projects.”
• service attachment works with VPC network From the official documentation: “The service attachment is a resource that establishes a secure and private connection between your VPC network and the producer VPC network.”
• Shared VPC is an alternative to VPC network From the official documentation: “The VLAN attachment or Cloud VPN tunnel must terminate in the same VPC network (or Shared VPC network) as the endpoint.”
• Virtual Private Cloud works with VPC Service Controls From the official documentation: “To implement network segmentation, place your CDE in a dedicated [Virtual Private Cloud (VPC)](/vpc) with [VPC Service Controls](/vpc-service-controls) enabled.”
• VPC network works with VPC Service Controls From the official documentation: “You can configure the VPC network to restrict Private Google Access with respect to a service perimeter.”
• VPC Network Peering is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
• VPC Service Controls secures Memorystore From the official documentation: “You can protect your Memorystore for Redis instances using VPC Service Controls.”