Stay organized with collections
Save and categorize content based on your preferences.
Deploy a managed service instance by using service
connection policies
This page describes how a service instance administrator can deploy an instance
of a managed service and configure connectivity by using service connection
policies.
Before you begin
Make sure that the managed service that you want to deploy supports
service connection policies. Making services available for deployment by
using service connection maps is available in a limited Preview. For more
information about services that support service connection maps, see
Supported services.
You need a service connection policy
for the VPC network, region, and managed service that you want
to deploy.
Required roles
Service instance administrators don't need any IAM permissions
for the VPC network because these permissions are delegated
by the service connection policy. However, IAM permissions might
be required for specific managed services that are deployed by using service
connection policies. For information about IAM permissions that
are required by a specific managed service, check the service's documentation.
Deploy a managed service instance and configure connectivity
If a service connection policy exists for a service, a consumer service
administrator can configure connectivity for the managed service instance that
they are deploying directly through the administrative API or UI of the managed
service.
To deploy managed service connectivity, follow these steps. The steps might
vary depending on the managed service.
Use the administrative API or UI of the managed service to deploy a service
instance, specifying Private Service Connect as your connectivity
type. The service might provide the option to specify the VPC
network to deploy Private Service Connect endpoints in.
If all authorization checks
pass, then connectivity is deployed. The
Network Connectivity Service Account creates an internal IP
address and Private Service Connect
endpoint in the specified VPC network.
The lifecycle of your endpoint matches the lifecycle of your managed
service instance. The endpoint remains active and stable unless you
reconfigure connectivity or decommission the service instance
After the Network Connectivity Service Account creates your endpoint, the
endpoint's forwarding rule is visible in the project that you configured
in step 1. This forwarding rule indicates that the connection has been
accepted by the producer and includes the IP address that was assigned to
your endpoint.
The names of all forwarding rules that are created by using
service connection policies start with sca-auto-. The following is an
example of a forwarding rule that was created by using a service connection
policy.
Your service might provide information about how to connect to the
new endpoint—for example, by providing an IP address. Use the
provided IP address to communicate with your service through internal IP
addresses within Google Cloud.
For more information about how to configure a specific service, see that
service's documentation.
Decommission service connectivity
To decommission service connectivity or decommission a managed service instance
that's deployed by using service connection policies, use the administrative API
or UI of the managed service. Delete each service instance that's associated
with the managed service. When service instances are deleted, service
connectivity automation deletes the associated connections and endpoints.
Troubleshooting
This section contains information about troubleshooting connections that are
created through service connectivity automation.
Endpoint creation or deletion failure
If authorized endpoints are not created or deleted as you expect,
describe the service connection policy.
The pscConnections field contains details about any blocking
errors and how you can resolve them.
After any issues are resolved, the endpoint is created or deleted the next time
service connectivity automation automatically
retries the operation.
Alternatively, if you don't want to wait for the retry process, you can use the
administrative API or UI of the managed service you are deploying to request
deployment and connectivity for another service instance, using a valid
configuration.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Deploy a managed service instance by using service connection policies\n\nDeploy a managed service instance by using service\nconnection policies\n======================================================================\n\nThis page describes how a service instance administrator can deploy an instance\nof a managed service and configure connectivity by using service connection\npolicies.\n\nBefore you begin\n----------------\n\n- Make sure that the managed service that you want to deploy supports\n service connection policies. Making services available for deployment by\n using service connection maps is available in a limited Preview. For more\n information about services that support service connection maps, see\n [Supported services](/vpc/docs/about-service-connectivity-automation#supported-services).\n\n- You need a [service connection policy](/vpc/docs/about-service-connection-policies)\n for the VPC network, region, and managed service that you want\n to deploy.\n\n### Required roles\n\nService instance administrators don't need any IAM permissions\nfor the VPC network because these permissions are delegated\nby the service connection policy. However, IAM permissions might\nbe required for specific managed services that are deployed by using service\nconnection policies. For information about IAM permissions that\nare required by a specific managed service, check the service's documentation.\n\nDeploy a managed service instance and configure connectivity\n------------------------------------------------------------\n\nIf a service connection policy exists for a service, a consumer service\nadministrator can configure connectivity for the managed service instance that\nthey are deploying directly through the administrative API or UI of the managed\nservice.\n\nTo deploy managed service connectivity, follow these steps. The steps might\nvary depending on the managed service.\n\n1. Use the administrative API or UI of the managed service to deploy a service\n instance, specifying Private Service Connect as your connectivity\n type. The service might provide the option to specify the VPC\n network to deploy Private Service Connect endpoints in.\n\n For example, you can\n [deploy and configure connectivity for a Cloud SQL instance](/sql/docs/mysql/configure-private-service-connect#create-cloud-sql-instance-psc-enabled-2).\n | **Note:** A service connection policy must exist for this VPC network, region, and service class. Otherwise, the service producer that's represented by the service class is not authorized to deploy connectivity on your behalf.\n2. If all [authorization checks](/vpc/docs/about-service-connectivity-automation#authorization)\n pass, then connectivity is deployed. The\n Network Connectivity Service Account creates an internal IP\n address and Private Service Connect\n endpoint in the specified VPC network.\n\n The lifecycle of your endpoint matches the lifecycle of your managed\n service instance. The endpoint remains active and stable unless you\n reconfigure connectivity or [decommission the service instance](#decommission-service)\n3. After the Network Connectivity Service Account creates your endpoint, the\n endpoint's forwarding rule is visible in the project that you configured\n in step 1. This forwarding rule indicates that the connection has been\n accepted by the producer and includes the IP address that was assigned to\n your endpoint.\n\n The names of all forwarding rules that are created by using\n service connection policies start with `sca-auto-`. The following is an\n example of a forwarding rule that was created by using a service connection\n policy. \n\n ```\n\n kind: compute#forwardingRule\n name: sca-auto-ab3f45d\n IPAddress: 10.33.2.8\n allowPscGlobalAccess: true\n network: https://www.googleapis.com/compute/v1/projects/consumer-project/global/networks/vpc1\n pscConnectionStatus: ACCEPTED\n region: https://www.googleapis.com/compute/v1/projects/consumer-project/regions/us-central1\n selfLink: https://www.googleapis.com/compute/v1/projects/consumer-project/regions/us-central1/forwardingRules/sca-auto-ab3f45d\n serviceDirectoryRegistrations:\n -namespace: goog-psc-default\n target:\n https://www.googleapis.com/compute/v1/projects/producer-project/regions/us-central1/serviceAttachments/producer-sa\n\n ```\n4. Your service might provide information about how to connect to the\n new endpoint---for example, by providing an IP address. Use the\n provided IP address to communicate with your service through internal IP\n addresses within Google Cloud.\n\n For more information about how to configure a specific service, see that\n service's documentation.\n\n| **Caution:** The managed service fully controls the lifecycle of Private Service Connect endpoints and IP addresses that are deployed by using service connection policies. Don't directly delete or update these Google Cloud resources or else you risk losing connectivity to your managed service instance. All actions to add, remove, or update connectivity for a managed service instance should be taken directly through the administrative API or UI of the managed service.\n\nDecommission service connectivity\n---------------------------------\n\nTo decommission service connectivity or decommission a managed service instance\nthat's deployed by using service connection policies, use the administrative API\nor UI of the managed service. Delete each service instance that's associated\nwith the managed service. When service instances are deleted, service\nconnectivity automation deletes the associated connections and endpoints.\n\nTroubleshooting\n---------------\n\nThis section contains information about troubleshooting connections that are\ncreated through service connectivity automation.\n\n### Endpoint creation or deletion failure\n\nIf authorized endpoints are not created or deleted as you expect,\n[describe the service connection policy](/vpc/docs/configure-service-connection-policies#describe-policy).\nThe `pscConnections` field contains details about any blocking\nerrors and how you can resolve them.\n\nAfter any issues are resolved, the endpoint is created or deleted the next time\nservice connectivity automation automatically\n[retries the operation](/vpc/docs/about-service-connectivity-automation#endpoint-automation).\n\nAlternatively, if you don't want to wait for the retry process, you can use the\nadministrative API or UI of the managed service you are deploying to request\ndeployment and connectivity for another service instance, using a valid\nconfiguration."]]
