GCP: Add link to the PSC process (#3294)

* GCP: Add link to the PSC process * update GCP PSC documentation --------- Co-authored-by: Mason Egger <[email protected]>
temporalio · Jan 22, 2025 · 2893072 · 2893072
1 parent 9c1e3fe
commit 2893072
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 6 deletions.
diff --git a/docs/evaluate/temporal-cloud/gcp-private-service-connect.mdx b/docs/evaluate/temporal-cloud/gcp-private-service-connect.mdx
@@ -11,22 +11,34 @@ keywords:
   - security
   - temporal cloud
   - gcp
+  - google cloud
 tags:
   - security
   - temporal-cloud
   - gcp
+  - google cloud
   - private service connect
   - private-connectivity
 ---
 
-#### GCP Private Service Connect
+#### Google Cloud Private Service Connect
 
-[GCP Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect) allows you to open a path to Temporal without opening a public egress.
+[Google Cloud Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect) allows you to open a path to Temporal without opening a public egress.
 It establishes a private connection between your Google Virtual Private Cloud (VPC) and Temporal Cloud.
 This one-way connection means Temporal cannot establish a connection back to your service.
 This is useful if normally you block traffic egress as part of your security protocols.
 If you use a private environment that does not allow external connectivity, you will remain isolated.
 
+:::note
+
+If you are interested in leveraging Google Cloud Private Service Connect in your Namespaces, [create a support ticket](/cloud/support#support-ticket) that includes the following information:
+
+- Google Cloud Region: The Region in which your connection will go through.
+- Google Cloud Project Id: The project that you will establish the private connection from, so it can be allowed on the Temporal side.
+- Temporal Cloud Namespace names: The name of the Namespaces you want to enable Google Cloud Private Service Connect with.
+
+:::
+
 Set up Private Service Connect with Temporal Cloud with these steps:
 
 1. Open the Google Cloud console
@@ -44,10 +56,10 @@ Set up Private Service Connect with Temporal Cloud with these steps:
 
   - For **Target service**, fill in the **Service name** with the Private Service Connect Service Name for the region you’re trying to connect to:
 
-      | Region                 | Private Service Connect Service Name                                            |
-      | ---------------------- | ------------------------------------------------------------------------------- |
-      | `us-central1`          | `projects/PROJECT/regions/us-central1/serviceAttachments/temporal-api`          |
-      | `australia-southeast1` | `projects/PROJECT/regions/australia-southeast1/serviceAttachments/temporal-api` |
+      | Region                 | Private Service Connect Service Name                                                      |
+      | ---------------------- | ----------------------------------------------------------------------------------------- |
+      | `asia-south1`          | `projects/prod-d5spc2sfeshws33bg33vwdef7/regions/asia-south1/serviceAttachments/pl-7w7tw` |
+      | `us-west1   `          | `projects/prod-rbe76zxxzydz4cbdz2xt5b59q/regions/us-west1/serviceAttachments/pl-94w0x`    |
 
   - For **Endpoint name**, enter a unique identifier to use for this endpoint. It could be for instance `temporal-api` or `temporal-api-<namespace>` if you want a different endpoint per namespace.
   - For **Network** and **Subnetwork**, choose the network and subnetwork where you want to publish your endpoint.

diff --git a/docs/evaluate/temporal-cloud/security.mdx b/docs/evaluate/temporal-cloud/security.mdx
@@ -63,6 +63,7 @@ Temporal Cloud supports private connectivity to enable you to connects to Tempor
 You can find more details per cloud:
 
 - [AWS PrivateLink](aws-privatelink.mdx)
+- [Google Cloud Private Service Connect](gcp-private-service-connect.mdx)
 
 ### Temporal Nexus