Update Transit gateway docs to cover more clouds (#3887)

Co-authored-by: Iain Cox <[email protected]>
timescale · Mar 3, 2025 · 7f97c6d · 7f97c6d
1 parent c57aec9
commit 7f97c6d
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 12 deletions.
diff --git a/use-timescale/page-index/page-index.js b/use-timescale/page-index/page-index.js
@@ -912,16 +912,16 @@ module.exports = [
             excerpt:
               "Connect to Timescale with a stricter SSL mode of verify-ca or verify-full",
           },
+          {
+            title: "Connect securely from any cloud",
+            href: "transit-gateway",
+            excerpt: "Peer your Timescale Cloud service with AWS Transit Gateway",
+          },
           {
             title: "VPC peering and AWS PrivateLink",
             href: "vpc",
             excerpt: "Secure your Timescale Service with VPC peering and AWS PrivateLink",
           },
-          {
-            title: "AWS Transit Gateway",
-            href: "transit-gateway",
-            excerpt: "Peer your Timescale Cloud service with AWS Transit Gateway",
-          },
           {
             title: "IP allow list",
             href: "ip-allow-list",

diff --git a/use-timescale/security/index.md b/use-timescale/security/index.md
@@ -14,12 +14,11 @@ privacy.
 *   Set up [multi-factor][mfa] and [SAML][saml] authentication
 *   Generate multiple [client credentials][client-credentials] instead of using your username and password
 *   Grant [read-only access][read-only] to your $SERVICE_LONGs
-*   Learn how to [connect with a stricter SSL mode][ssl]
-*   Secure your Timescale Cloud services with [VPC peering][vpc-peering]
-*   Peer your $SERVICE_LONGs with [AWS Transit Gateway][transit-gateway]
+*   Connect with a [stricter SSL mode][ssl]
+*   Secure your $SERVICE_LONGs with [VPC peering][vpc-peering]
+*   Connect to your $SERVICE_SHORTs from any cloud with [AWS Transit Gateway][transit-gateway]
 *   Restrict access with an [IP address allow list][ip-allowlist]
 
-
 [overview]: /use-timescale/:currentVersion:/security/overview/
 [ssl]: /use-timescale/:currentVersion:/security/strict-ssl/
 [mfa]: /use-timescale/:currentVersion:/security/multi-factor-authentication/

diff --git a/use-timescale/security/transit-gateway.md b/use-timescale/security/transit-gateway.md
@@ -9,11 +9,13 @@ cloud_ui:
         - [services, :serviceId, operations, vpc]
 ---
 
-# Peer your $SERVICE_LONGs with AWS Transit Gateway
+# Securely connect to $CLOUD_LONG from any cloud or on-premise environment
 
-You use [AWS Transit Gateway][aws-transit-gateway] as a traffic controller for your network. Instead of setting up lots of direct connections to virtual private clouds, on-premise data centers, and other AWS services, you connect everything to Transit Gateway. This simplifies your network and makes it easier to manage and scale.
+[AWS Transit Gateway][aws-transit-gateway] enables you to securely connect to your $CLOUD_LONG from AWS, GCP, Azure, or any other cloud or on-premise environment.
 
-You can create a peering connection between your $SERVICE_LONGs and AWS Transit Gateway in $CLOUD_LONG. This means that, no matter how big or complex your infrastructure is, you can connect securely to your $SERVICE_LONGs. 
+You use AWS Transit Gateway as a traffic controller for your network. Instead of setting up multiple direct connections to different clouds, on-premise data centers, and other AWS services, you connect everything to Transit Gateway. This simplifies your network and makes it easier to manage and scale.
+
+You can then create a peering connection between your $SERVICE_LONGs and AWS Transit Gateway in $CLOUD_LONG. This means that, no matter how big or complex your infrastructure is, you can connect securely to your $SERVICE_LONGs. 
 
 To configure this secure connection, you: