Dyaffe patch 1 (#1241)

* Create google-cloud-sql-postgres.md * Update PostgreSQL.md * Update google-cloud-sql-postgres.md * Create google-cloud-sql-mysql.md * Update MySQL.md * Update sqlserver.md * Create google-cloud-sql-sqlserver.md * Update google-cloud-sql-mysql.md * Update mysql.md * Update sqlserver.md * Update PostgreSQL.md * Create google-cloud-sql-postgres.md * Create google-cloud-sql-mysql.md * Create google-cloud-sql-sqlserver.md * Update google-cloud-sql-postgres.md * Update google-cloud-sql-postgres.md Updating as per Olivia's feedback * Update google-cloud-sql-sqlserver.md Updating as per Olivias comments * Update google-cloud-sql-postgres.md Updating as per Olivia's feedback * Update google-cloud-sql-postgres.md Finishing Olivias feedback on source postgres * Update google-cloud-sql-mysql.md Updating as per olivia's feedback
estuary · Oct 17, 2023 · 8eddfa4 · 8eddfa4
1 parent ffc6356
commit 8eddfa4
Show file tree

Hide file tree

Showing 12 changed files with 1,286 additions and 18 deletions.
diff --git a/site/docs/reference/Connectors/capture-connectors/MySQL.md b/site/docs/reference/Connectors/capture-connectors/MySQL.md
@@ -84,7 +84,7 @@ You're able to apply the connector directly to the primary instance if you'd lik
 
 1. Allow connections to the database from the Estuary Flow IP address.
 
-   1. [Modify the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html), setting **Public accessibility** to **Yes**.
+   1. [Modify the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html), setting **Public accessibility** to **Yes**.  See the directions below to use a SSH Tunnel instead of enabling public access.
 
    1. Edit the VPC security group associated with your database, or create a new VPC security group and associate it with the database.
       Refer to the [steps in the Amazon documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html#Overview.RDSSecurityGroups.Create).
@@ -157,7 +157,7 @@ For each step, take note of which entity you're working with.
 
 1. Allow connections to the database from the Estuary Flow IP address.
 
-   1. [Modify the instance](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.html#Aurora.Modifying.Instance), choosing **Publicly accessible** in the **Connectivity** settings.
+   1. [Modify the instance](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.html#Aurora.Modifying.Instance), choosing **Publicly accessible** in the **Connectivity** settings.  See the directions below to use a SSH Tunnel instead of enabling public access.
 
    2. Edit the VPC security group associated with your instance, or create a new VPC security group and associate it with the instance.
       Refer to the [steps in the Amazon documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html#Overview.RDSSecurityGroups.Create).
@@ -216,7 +216,7 @@ CALL mysql.rds_set_configuration('binlog retention hours', 168);
 1. Allow connections to the DB instance from the Estuary Flow IP address.
 
    1. [Enable public IP on your database](https://cloud.google.com/sql/docs/mysql/configure-ip#add) and add
-      `34.121.207.128` as an authorized IP address.
+      `34.121.207.128` as an authorized IP address.  See the directions below to use a SSH Tunnel instead of enabling public access.
 
    :::info
    Alternatively, you can allow secure connections via SSH tunneling. To do so:

diff --git a/site/docs/reference/Connectors/capture-connectors/PostgreSQL.md b/site/docs/reference/Connectors/capture-connectors/PostgreSQL.md
@@ -101,8 +101,9 @@ ALTER SYSTEM SET wal_level = logical;
 1. Allow connections to the database from the Estuary Flow IP address.
 
    1. [Modify the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html), setting **Public accessibility** to **Yes**.
+      See directions below to use a SSH Tunnel instead of enabling public access.
 
-   2. Edit the VPC security group associated with your database, or create a new VPC security group and associate it with the database.
+   3. Edit the VPC security group associated with your database, or create a new VPC security group and associate it with the database.
       Refer to the [steps in the Amazon documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html#Overview.RDSSecurityGroups.Create).
       Create a new inbound rule and a new outbound rule that allow all traffic from the IP address `34.121.207.128`.
 
@@ -157,8 +158,9 @@ For each step, take note of which entity you're working with.
 1. Allow connections to the DB instance from the Estuary Flow IP address.
 
    1. [Modify the instance](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.html#Aurora.Modifying.Instance), choosing **Publicly accessible** in the **Connectivity** settings.
+      See directions below to use a SSH Tunnel instead of enabling public access.
 
-   2. Edit the VPC security group associated with your instance, or create a new VPC security group and associate it with the instance.
+   3. Edit the VPC security group associated with your instance, or create a new VPC security group and associate it with the instance.
       Refer to the [steps in the Amazon documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html#Overview.RDSSecurityGroups.Create).
       Create a new inbound rule and a new outbound rule that allow all traffic from the IP address `34.121.207.128`.
 
@@ -209,7 +211,7 @@ and set up the watermarks table and publication.
 1. Allow connections to the database from the Estuary Flow IP address.
 
    1. [Enable public IP on your database](https://cloud.google.com/sql/docs/mysql/configure-ip#add) and add
-      `34.121.207.128` as an authorized IP address.
+      `34.121.207.128` as an authorized IP address.  See directions below to use a SSH Tunnel instead of enabling public access.
 
    :::info
    Alternatively, you can allow secure connections via SSH tunneling. To do so:
@@ -416,4 +418,4 @@ It is recommended that the publication used by the capture only contain the tabl
 CREATE PUBLICATION flow_publication FOR ALL TABLES WITH (publish_via_partition_root = true);
 ```
 
-Caution must be used if creating the publication in this way as all existing tables (even those not part of the capture) will be included in it, and if any of them do not have a primary key they will no longer be able to process updates or deletes.
+Caution must be used if creating the publication in this way as all existing tables (even those not part of the capture) will be included in it, and if any of them do not have a primary key they will no longer be able to process updates or deletes.