From 78393d20af0ff6df616d2744b6810b20fcde314d Mon Sep 17 00:00:00 2001 From: Saravana Krishnamurthy Date: Sun, 11 Feb 2024 10:00:02 -0800 Subject: [PATCH] Update Setting up GCP Private Service Connect.md --- .../Setting up GCP Private Service Connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Using AWS GCP private VPC connections/Setting up GCP Private Service Connect.md b/docs/Using AWS GCP private VPC connections/Setting up GCP Private Service Connect.md index 04221797..c403b7c1 100644 --- a/docs/Using AWS GCP private VPC connections/Setting up GCP Private Service Connect.md +++ b/docs/Using AWS GCP private VPC connections/Setting up GCP Private Service Connect.md @@ -92,7 +92,7 @@ We recommend use of a subnet dedicated to Private Service Connect endpoints in t 2. Configure the endpoint connection: ◦ Target: Published service - ◦ Target service: the `endpoint_service` value from the SkySQL DBaaS API + ◦ Target service: the value of the "Fully Qualified Domain Name" in the "Connect" window from SkySQL portal. ◦ Endpoint name: set to the Database ID from SkySQL (dbxxxxxxxx) ◦ Network: select the VPC network where the application is running ◦ Subnetwork: select the subnet where the static internal IP address is reserved