From cab3925acaa235dda2bde623f48d6fa7acfa9f9c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 4 Aug 2023 05:15:27 -0400 Subject: [PATCH 1/9] BigAnimal: auto tuning support --- advocacy_docs/pg_extensions/pg_tuner/using.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/advocacy_docs/pg_extensions/pg_tuner/using.mdx b/advocacy_docs/pg_extensions/pg_tuner/using.mdx index f1c2c704c77..d70ea82fa88 100644 --- a/advocacy_docs/pg_extensions/pg_tuner/using.mdx +++ b/advocacy_docs/pg_extensions/pg_tuner/using.mdx @@ -9,6 +9,9 @@ You can use EDB Postgres Tuner in two ways: to automatically apply all tuning re To automatically apply all tuning recommendations, set the `edb_pg_tuner.autotune` parameter to `true`. Restart Postgres to apply the change. EDB Postgres Tuner then begins applying tuning recommendations. +!!! Note + Automatic tuning isn't currently supported for BigAnimal. + ## Manual tuning To manually apply selected tuning recommendations, make sure the `edb_pg_tuner.autotune` parameter is set to `false`, which is the default. Then, use the `edb_pg_tuner_recommendations` function to inspect the tuning recommendations from the output. From 267b22b98477aebb02024e730b0125360315b3df Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 3 Aug 2023 10:51:33 -0400 Subject: [PATCH 2/9] BigAnimal: GCP private endpoints --- .../connecting_from_gcp/index.mdx | 130 +++++++++++++++++- 1 file changed, 127 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx index f495f9f6768..11a1906b2a6 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx @@ -2,9 +2,133 @@ title: Connecting from Google Cloud --- -If you are using your Google Cloud account, you can use Google Cloud's [Private Service Connect](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer) to publish services using internal IP addresses in your VPC network. Private Service Connect is a network interface that securely connects a private IP address from your Google Cloud VPC to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource VPC, thus ensuring maximum network isolation. +If you are using your own Google Cloud account, you can use Google Cloud [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer) to publish services using internal IP addresses in your VPC network. PSC is a network interface that securely connects a private IP address from your Google Cloud VPC to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource VPC, thus ensuring maximum network isolation. -Private Service Connect provides two methods to connect to published services: using endpoints or load balancers (also referred to as Private Service Connect backends). We provide step-by-step directions in the knowledge base for the method using load balancers (see [Connect to BigAnimal private cluster using GCP Private Service Connect](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect)). Private Service Connect backends use a load balancer configured with Private Service Connect network endpoint group (NEG) backends. For more information, see [About Private Service Connect backends](https://cloud.google.com/vpc/docs/private-service-connect-backends) and [Create a Private Service Connect backend](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends). +PSC provides two methods to connect to published services: using PSC-connected endpoints or load balancers (also referred to as PSC backends). We provide step-by-step directions in the knowledge base for the method using load balancers (see [Connect to BigAnimal private cluster using GCP Private Service Connect](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect)). PSC backends use a load balancer configured with PSC network endpoint group (NEG) backends. For more information, see [About Private Service Connect backends](https://cloud.google.com/vpc/docs/private-service-connect-backends) and [Create a Private Service Connect backend](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends). -While we recommend using Private Service Connect when using your Google Cloud account, another option is VPC peering. See [VPC peering](vpc_peering) for more information. +While we recommend using PSC-connected endpoints when using your own Google Cloud account, another option is VPC peering. See [VPC peering](vpc_peering) for more information. +## PSC-connected endpoint + +The way you create a private PSC-connected endpoint differs when you're using your Google Cloud project versus using BigAnimal's cloud account. + +### Using BigAnimal's cloud account + +When using BigAnimal's cloud account, you provide BigAnimal with your Google Cloud project ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/#network-logs--telemetry-section)). BigAnimal, in turn, provides you with a Google Cloud Service Attachment, which you can use to connect to your cluster privately. + +1. When creating your cluster, on the **Cluster Settings** tab, in the **Network** section: + 1. Select **Private**. + + 1. Enter your application's Google Cloud project ID. + +1. After the cluster is created, go to the cluster details to see the corresponding Service Attachment. You need the Service Attachment while creating a PSC-connected endpoint. + +1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. The steps are available [here](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). + +1. In your application's Google Cloud, select **Private Service Connect**, and then select **Connected Endpoints**. Select the endpoint you created previously, and use the Service Attachment provided in the details section in BigAnimal to access your cluster. + +### Using your own Google Cloud account + +Two different methods enable you to connect to your private cluster from your application's VPC in Google Cloud. Each method offers different levels of accessibility and security. The PSC-connected endpoint method is recommended and is most commonly used. However, you can also use the VPC peering connection method if required by your organization. + +--------------- +Remainder of topic is copied from AWS topic - it hasn't been checked by Jason, but some references to AWS have been changed to GCP +--------------- +### PSC-connected endpoint example + +This example shows how to connect your cluster using PSC-connected endpoints. + +Assume that your cluster is on a project called `development` and is being accessed from a client on another account called `test`. It has the following properties: + +- BigAnimal cluster: + - Google Cloud project: `development` + - Amazon resource name (ARN): `arn:aws:iam::123456789123:root` + - Cluster ID: `p-mckwlbakq5` + - Account ID: `brcxzr08qr7rbei1` + - Organization's domain name: `biganimal.io` + +- Client: + - AWS account: `test` + - Resource group: `rg-client` + - VPC: `vpc-client` + - VPC subnet: `snet-client` + +#### Prerequisites + +To walk through an example in your own environment, you need: + +- Your cluster URL. You can find the URL in the **Connect** tab of your cluster instance in the BigAnimal portal. + + +#### Step 1: Create an endpoint service for your cluster + +In the Google Cloud project connected to BigAnimal, create a PSC-connected endpoint to provide access to your clusters from other VPCs in other Google Cloud projects. Perform this procedure for each cluster to which you want to provide access. + +1. Open the [Amazon EC2 console](https://console.aws.amazon.com/ec2/). Ensure that the region where your cluster is deployed is selected in the upper-right corner of the console. + +1. In the navigation pane, under **Load Balancing**, select **Load Balancers**. + +1. Identify the load balancer that's tagged with the ID of the cluster to which you want to connect (`-rw-internal-lb`), for example, `p-96fh28m3cb-rw-internal-lb`. Note the name of that network load balancer. + +1. Open the [Amazon VPC console](https://console.aws.amazon.com/vpc/). + +1. From the navigation pane on the left, under **Virtual Private Cloud**, select **Endpoint Services**, and then select **Create endpoint service**. + +1. Enter a suitable name for the endpoint service. + +1. Select **Network** for the load balancer type. + +1. Under **Available load balancers**, select the network load balancer of the cluster to which you want to connect. + +1. Leave all the other fields with their default values, and select **Create**. + +1. Under **Details**, note the **Service name** of the created endpoint service (for example, `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc123198abc`). You need the service name while creating a VPC endpoint. + +1. In the navigation pane, select **Endpoint Services**. + +1. Select your endpoint service from the **Actions** list, and select **Allow principals**. + +1. Add the AWS account with which you want to connect to the endpoint service by specifying the ARN for the principal. The ARN must be in this format: + + arn:aws:iam::<AWS ACCOUNT ID>:root + + +#### Step 2: Create a VPC endpoint in the client's VPC + +Now that your endpoint service is created, you can connect it to the cluster VPC using a VPC endpoint. Perform this procedure in your application's AWS account. + +!!! Note + In your application's AWS account, ensure that you allow your application's security group to connect to your cluster. + +1. Open the [Amazon VPC console](https://console.aws.amazon.com/vpc/). + +1. Ensure that the region where your cluster is deployed is selected in the upper-right corner of the console. + +1. From the navigation pane on the left, under **Virtual Private Cloud**, select **Endpoints**, and then select **Create endpoint**. + +1. Enter a suitable name for the endpoint service. + +1. Under **Service category**, select **Other endpoint services**. + +1. Under **Service Name**, enter the name of the endpoint service that you created earlier: + + - If following the example using your own AWS account: `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc123198abc` + - If using BigAnimal's cloud: the service name provided in your BigAnimal cluster's details + + To verify whether you successfully allowed access to the endpoint, select **Verify service**. + +1. Under VPC, select the client's VPC in which to create the endpoint. + +1. Under **Subnets**, select the subnets (availability zones) in which to create the endpoint network interfaces. Enable the endpoint in all availability zones used by your application. + +1. Select **Create endpoint**. + +#### Step 3: Accept and test the connection + +1. In your AWS account connected to BigAnimal, select **VPCs**, and then select **Endpoint services**. + +1. Select the endpoint service instance you created previously, and accept the endpoint connection request under **Endpoint connections**. + +1. You can now successfully connect to your cluster. + + In your application's AWS account, select **VPC** and then select **Endpoints**. Select the endpoint you created previously and use the DNS name provided in the details section to access your cluster. From d126eee06f8870cac1ef614ddbbb04cd4e89e9a2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 4 Aug 2023 16:36:28 -0400 Subject: [PATCH 3/9] updates from Jason's doc --- .../connecting_from_gcp/index.mdx | 160 +++++++++--------- 1 file changed, 77 insertions(+), 83 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx index 11a1906b2a6..b38457f8abd 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx @@ -2,133 +2,127 @@ title: Connecting from Google Cloud --- -If you are using your own Google Cloud account, you can use Google Cloud [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer) to publish services using internal IP addresses in your VPC network. PSC is a network interface that securely connects a private IP address from your Google Cloud VPC to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource VPC, thus ensuring maximum network isolation. - -PSC provides two methods to connect to published services: using PSC-connected endpoints or load balancers (also referred to as PSC backends). We provide step-by-step directions in the knowledge base for the method using load balancers (see [Connect to BigAnimal private cluster using GCP Private Service Connect](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect)). PSC backends use a load balancer configured with PSC network endpoint group (NEG) backends. For more information, see [About Private Service Connect backends](https://cloud.google.com/vpc/docs/private-service-connect-backends) and [Create a Private Service Connect backend](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends). - -While we recommend using PSC-connected endpoints when using your own Google Cloud account, another option is VPC peering. See [VPC peering](vpc_peering) for more information. - -## PSC-connected endpoint - -The way you create a private PSC-connected endpoint differs when you're using your Google Cloud project versus using BigAnimal's cloud account. - -### Using BigAnimal's cloud account +The way you create a private Google Cloud endpoint differs when you're using your Google Cloud account versus using BigAnimal's cloud account. +## Using BigAnimal's cloud account When using BigAnimal's cloud account, you provide BigAnimal with your Google Cloud project ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/#network-logs--telemetry-section)). BigAnimal, in turn, provides you with a Google Cloud Service Attachment, which you can use to connect to your cluster privately. 1. When creating your cluster, on the **Cluster Settings** tab, in the **Network** section: 1. Select **Private**. - 1. Enter your application's Google Cloud project ID. 1. After the cluster is created, go to the cluster details to see the corresponding Service Attachment. You need the Service Attachment while creating a PSC-connected endpoint. -1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. The steps are available [here](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). +1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. See [Step 2: Create a Connected Endpoint for the VM client / application](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). 1. In your application's Google Cloud, select **Private Service Connect**, and then select **Connected Endpoints**. Select the endpoint you created previously, and use the Service Attachment provided in the details section in BigAnimal to access your cluster. -### Using your own Google Cloud account +## Using your Google Cloud account -Two different methods enable you to connect to your private cluster from your application's VPC in Google Cloud. Each method offers different levels of accessibility and security. The PSC-connected endpoint method is recommended and is most commonly used. However, you can also use the VPC peering connection method if required by your organization. +Two different methods enable you to connect to your private cluster from your application's VPC in Google Cloud. Each method offers different levels of accessibility and security. ---------------- -Remainder of topic is copied from AWS topic - it hasn't been checked by Jason, but some references to AWS have been changed to GCP ---------------- -### PSC-connected endpoint example +- You can use Google Cloud [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer) to publish services using internal IP addresses in your VPC network. PSC is a network interface that securely connects a private IP address from your Google Cloud VPC to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource VPC, thus ensuring maximum network isolation. We refer to this process of connecting as using PSC-connected endpoints. -This example shows how to connect your cluster using PSC-connected endpoints. +- We recommend the PSC-connected endpoint method and it is most commonly used. This method is described in this topic. However, you can also use the [VPC peering](vpc_peering) connection method, if required by your organization. + +### PSC-connected endpoint example +This example shows how to connect your cluster using PSC-connected endpoints. Assume that your cluster is on a project called `development` and is being accessed from a client on another account called `test`. It has the following properties: -- BigAnimal cluster: - - Google Cloud project: `development` - - Amazon resource name (ARN): `arn:aws:iam::123456789123:root` - - Cluster ID: `p-mckwlbakq5` - - Account ID: `brcxzr08qr7rbei1` - - Organization's domain name: `biganimal.io` +- BigAnimal cluster: + - Google Cloud Project Project: development + - Google Cloud Project ID: development-001 + - BigAnimal Cluster ID: p-mckwlbakq5 + - Region where BigAnimal cluster is deployed: us-central1 + - BigAnimal Organization ID: brcxzr08qr7rbei1 + - Organization's domain name: biganimal.io + - Host Name: p-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io +- VM Client: + - Google Cloud Project Name: test + - Google Cloud Project ID: test-001 + - VM Client/App: test-app-1 + - VM Client’s VPC: client-app-vpc + - VM Client’s Subnet: client-app-subnet -- Client: - - AWS account: `test` - - Resource group: `rg-client` - - VPC: `vpc-client` - - VPC subnet: `snet-client` -#### Prerequisites +### Prerequisites To walk through an example in your own environment, you need: -- Your cluster URL. You can find the URL in the **Connect** tab of your cluster instance in the BigAnimal portal. - +- A BigAnimal Postgres cluster deployed with private connectivity. +- A VM with a client/application installed in your Google Cloud project. +- The VM’s VPC has a subnet in the same region as the BigAnimal cluster. -#### Step 1: Create an endpoint service for your cluster -In the Google Cloud project connected to BigAnimal, create a PSC-connected endpoint to provide access to your clusters from other VPCs in other Google Cloud projects. Perform this procedure for each cluster to which you want to provide access. +### Step 1: Create an endpoint service for your cluster (if using your own project) -1. Open the [Amazon EC2 console](https://console.aws.amazon.com/ec2/). Ensure that the region where your cluster is deployed is selected in the upper-right corner of the console. - -1. In the navigation pane, under **Load Balancing**, select **Load Balancers**. - -1. Identify the load balancer that's tagged with the ID of the cluster to which you want to connect (`-rw-internal-lb`), for example, `p-96fh28m3cb-rw-internal-lb`. Note the name of that network load balancer. +!!! Note + Performed in the Google Cloud project connected to your BigAnimal subscription. -1. Open the [Amazon VPC console](https://console.aws.amazon.com/vpc/). +In the Google Cloud project connected to BigAnimal, create a PSC Published Service to provide access to your cluster from other VPCs in other Google Cloud projects. Perform this procedure for each Postgres cluster to which you want to provide access. -1. From the navigation pane on the left, under **Virtual Private Cloud**, select **Endpoint Services**, and then select **Create endpoint service**. +1. Get the hostname of your Postgres cluster from the Connect tab of the Cluster page on the BigAnimal portal: +`P-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io`. -1. Enter a suitable name for the endpoint service. +1. Using Cloudshell, the command prompt, or other terminal, get the internal IP address of the host by performing a ping or nslookup or dig +short <host> against the hostname: +`10.247.200.9`. -1. Select **Network** for the load balancer type. +1. In the Google Cloud portal, go Network Services > Load balancing. -1. Under **Available load balancers**, select the network load balancer of the cluster to which you want to connect. - -1. Leave all the other fields with their default values, and select **Create**. +1. In the Filter area, choose Addresses under **LOAD BALANCERS**, and filter for the host IP (`10.247.200.9`) Note the load balancer name (`a58262cd80b234a3aa917b719e69843f`). -1. Under **Details**, note the **Service name** of the created endpoint service (for example, `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc123198abc`). You need the service name while creating a VPC endpoint. +1. Navigate to **Private Service Connect -> PUBLISHED SERVICES -> + PUBLISH SERVICE. -1. In the navigation pane, select **Endpoint Services**. +1. Select **+ PUBLISH SERVICE**. + 1. Under **Load Balancer Type**: + 1. Select **Internal passthrough Network Load Balancer** + 1. Paste the load balancer name (`a58262cd80b234a3aa917b719e69843f`) in the **Internal load balancer** field. + 1. For Service Name, give the published service a name (`p-mckwlbakq5`). + 1. For Subnets, choose RESERVE NEW SUBNET from the dropdown. -1. Select your endpoint service from the **Actions** list, and select **Allow principals**. - -1. Add the AWS account with which you want to connect to the endpoint service by specifying the ARN for the principal. The ARN must be in this format: +1. In the Reserve subnet for Private Service Connect window, enter the following details, then select **ADD**. + 1. For Name, use the name of the Postgres cluster p-mckwlbakq5. + 1. For IPv4 range, assign the CIDR for the field IPv4 range. For example, 10.247.214.0/29. + !!! Note Recommendations for IP Range: + - Allocate at least 8 IP addresses to the CIDR, so the subnet mask should not be greater than 29. + - Avoid overlap with other reserved IP ranges by not allocating too many IP addresses at one time. + - If you encounter the error "This IPv4 address range overlaps with a subnet you already added. Enter an address range that doesn't overlap.", you’ll need to use another CIDR block (until no error returns). - arn:aws:iam::<AWS ACCOUNT ID>:root +1. (Optional) Add the consumer (where the client app resides) Google Cloud project ID (test-001) to accept connections automatically. +1. ADD SERVICE and get the name of the service attachment. You may need to select the newly created Published service to find the name of the service attachment. (Service Attachment: projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5). -#### Step 2: Create a VPC endpoint in the client's VPC +1. Proceed to Step 2: Create a Connected Endpoint for the VM client / application -Now that your endpoint service is created, you can connect it to the cluster VPC using a VPC endpoint. Perform this procedure in your application's AWS account. +### Step 2: Create a connected endpoint for the VM client / application !!! Note - In your application's AWS account, ensure that you allow your application's security group to connect to your cluster. - -1. Open the [Amazon VPC console](https://console.aws.amazon.com/vpc/). - -1. Ensure that the region where your cluster is deployed is selected in the upper-right corner of the console. - -1. From the navigation pane on the left, under **Virtual Private Cloud**, select **Endpoints**, and then select **Create endpoint**. - -1. Enter a suitable name for the endpoint service. - -1. Under **Service category**, select **Other endpoint services**. - -1. Under **Service Name**, enter the name of the endpoint service that you created earlier: - - - If following the example using your own AWS account: `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc123198abc` - - If using BigAnimal's cloud: the service name provided in your BigAnimal cluster's details - - To verify whether you successfully allowed access to the endpoint, select **Verify service**. - -1. Under VPC, select the client's VPC in which to create the endpoint. + Performed in the Google Cloud project where your VM client / application resides. -1. Under **Subnets**, select the subnets (availability zones) in which to create the endpoint network interfaces. Enable the endpoint in all availability zones used by your application. +1. From the Google Cloud console, switch over to the project where your VM client / application resides (`test`). -1. Select **Create endpoint**. +1. Go to **Compute Engine -> VM Instances -> Network Interface -> Network** to get the VPC of your VM(client-app-vpc). -#### Step 3: Accept and test the connection +1. Go to **Network Services -> Private Service Connect -> CONNECTED ENDPOINTS -> +CONNECT ENDPOINT** to create an endpoint with the VPC. + 1. For the Target, select Published service, and use the Service Attachment captured earlier (projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5). + 1. For the Endpoint name, use the name of your VM Client / App (test-app-1). + 1. For the Network (VPC), use the name of your VM Client’s VPC (client-app-vpc). + 1. For the Subnetwork, use your VM Client’s Subnet (client-app-subnet). + !!! Note + If no subnet is available, create a subnet in the VPC for the region where your Postgres cluster was created. Refer to the steps in [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4NMNNSFQXNTX78W08Q3G39K). + 1. For the IP address, create an IP address, or choose an existing IP that is not used by the other endpoints + 1. Enable Global Access. + !!! Note + If your VM is running in a different region from BigAnimal, then Global Access should always be enabled. +1. Select ** ADD ENDPOINT**. -1. In your AWS account connected to BigAnimal, select **VPCs**, and then select **Endpoint services**. +1. Check to see if the endpoint status is Accepted, and obtain the IP address. + !!! Note + If the endpoint status is Pending, refer to the steps in [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4NMPGXCSC9V30WNESV52FAV). -1. Select the endpoint service instance you created previously, and accept the endpoint connection request under **Endpoint connections**. +1. Connect to your BigAnimal cluster from your client application using the endpoint IP address (for example, `psql "postgres://edb_admin@:5432/edb_admin?sslmode=require"`). -1. You can now successfully connect to your cluster. +### Step 3: Set up a Private DNS Zone (optional) +Setting up a Private DNS Zone in your Google Cloud project allows you to connect BigAnimal with the host. For instructions on setting up a Private DNS Zone, refer to [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4QMHF1DJGKW5ED2BQ6YCT29). - In your application's AWS account, select **VPC** and then select **Endpoints**. Select the endpoint you created previously and use the DNS name provided in the details section to access your cluster. From 074361062a8975657ba1a86192cc2dc5c747b2d5 Mon Sep 17 00:00:00 2001 From: Jason Parton <90264119+jasonparton@users.noreply.github.com> Date: Fri, 4 Aug 2023 22:13:13 -0400 Subject: [PATCH 4/9] Update index.mdx Jason's minor updates --- .../connecting_from_gcp/index.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx index b38457f8abd..17a65247165 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx @@ -28,7 +28,7 @@ Two different methods enable you to connect to your private cluster from your ap ### PSC-connected endpoint example This example shows how to connect your cluster using PSC-connected endpoints. -Assume that your cluster is on a project called `development` and is being accessed from a client on another account called `test`. It has the following properties: +Assume that your cluster is in a project called `development` and is being accessed from a client in another project called `test`. It has the following properties: - BigAnimal cluster: - Google Cloud Project Project: development @@ -55,7 +55,7 @@ To walk through an example in your own environment, you need: - The VM’s VPC has a subnet in the same region as the BigAnimal cluster. -### Step 1: Create an endpoint service for your cluster (if using your own project) +### Step 1: Publish a Service from BigAnimal !!! Note Performed in the Google Cloud project connected to your BigAnimal subscription. @@ -65,10 +65,10 @@ In the Google Cloud project connected to BigAnimal, create a PSC Published Servi 1. Get the hostname of your Postgres cluster from the Connect tab of the Cluster page on the BigAnimal portal: `P-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io`. -1. Using Cloudshell, the command prompt, or other terminal, get the internal IP address of the host by performing a ping or nslookup or dig +short <host> against the hostname: +1. Using Cloudshell, the command prompt, or other terminal, get the internal IP address of the host by performing a ping, nslookup, or dig +short <host> against the hostname: `10.247.200.9`. -1. In the Google Cloud portal, go Network Services > Load balancing. +1. In the Google Cloud portal, go to Network Services > Load balancing. 1. In the Filter area, choose Addresses under **LOAD BALANCERS**, and filter for the host IP (`10.247.200.9`) Note the load balancer name (`a58262cd80b234a3aa917b719e69843f`). @@ -85,7 +85,7 @@ In the Google Cloud project connected to BigAnimal, create a PSC Published Servi 1. For Name, use the name of the Postgres cluster p-mckwlbakq5. 1. For IPv4 range, assign the CIDR for the field IPv4 range. For example, 10.247.214.0/29. !!! Note Recommendations for IP Range: - - Allocate at least 8 IP addresses to the CIDR, so the subnet mask should not be greater than 29. + - Allocate at least 8 IP addresses to the CIDR. The subnet mask should not be greater than 29. - Avoid overlap with other reserved IP ranges by not allocating too many IP addresses at one time. - If you encounter the error "This IPv4 address range overlaps with a subnet you already added. Enter an address range that doesn't overlap.", you’ll need to use another CIDR block (until no error returns). @@ -95,7 +95,7 @@ In the Google Cloud project connected to BigAnimal, create a PSC Published Servi 1. Proceed to Step 2: Create a Connected Endpoint for the VM client / application -### Step 2: Create a connected endpoint for the VM client / application +### Step 2: Create a Connected Endpoint for the VM client / application !!! Note Performed in the Google Cloud project where your VM client / application resides. @@ -121,7 +121,7 @@ In the Google Cloud project connected to BigAnimal, create a PSC Published Servi !!! Note If the endpoint status is Pending, refer to the steps in [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4NMPGXCSC9V30WNESV52FAV). -1. Connect to your BigAnimal cluster from your client application using the endpoint IP address (for example, `psql "postgres://edb_admin@:5432/edb_admin?sslmode=require"`). +1. Connect to your BigAnimal cluster from your client application using the endpoint IP address (for example, `psql "postgres://edb_admin@:5432/edb_admin?sslmode=require"`). ### Step 3: Set up a Private DNS Zone (optional) Setting up a Private DNS Zone in your Google Cloud project allows you to connect BigAnimal with the host. For instructions on setting up a Private DNS Zone, refer to [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4QMHF1DJGKW5ED2BQ6YCT29). From 88e9f0ca0cee318fff2f987a4f8689622896e3e2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 5 Aug 2023 06:34:47 -0400 Subject: [PATCH 5/9] further cleanup --- .../01_connecting_from_azure/index.mdx | 1 + .../02_connecting_from_aws/index.mdx | 1 + .../connecting_from_a_client.mdx | 1 + .../connecting_from_gcp/index.mdx | 98 ++++++++++--------- 4 files changed, 54 insertions(+), 47 deletions(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx index 452858da15b..936aa93b8c3 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx @@ -1,5 +1,6 @@ --- title: Connecting from Azure +navTitle: From Azure redirects: - /biganimal/release/using_cluster/connecting_your_cluster/01_connecting_from_azure - /biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx index 6157eda68a2..0d6c7864b44 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/index.mdx @@ -1,5 +1,6 @@ --- title: Connecting from AWS +navTitle: From AWS redirects: - /biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint/ --- diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_a_client.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_a_client.mdx index 3fd6ef6b9a6..723c994de23 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_a_client.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_a_client.mdx @@ -1,5 +1,6 @@ --- title: Connecting from a client app +navTitle: From a client app --- You can connect to your cluster using the client of your choice including: diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx index 17a65247165..a5f76914956 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx @@ -1,21 +1,23 @@ --- title: Connecting from Google Cloud +navTitle: From Google Cloud --- The way you create a private Google Cloud endpoint differs when you're using your Google Cloud account versus using BigAnimal's cloud account. ## Using BigAnimal's cloud account -When using BigAnimal's cloud account, you provide BigAnimal with your Google Cloud project ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/#network-logs--telemetry-section)). BigAnimal, in turn, provides you with a Google Cloud Service Attachment, which you can use to connect to your cluster privately. +When using BigAnimal's cloud account, you provide BigAnimal with your Google Cloud project ID when creating a cluster (see [Networking](/biganimal/latest/getting_started/creating_a_cluster/#network-logs--telemetry-section)). BigAnimal, in turn, provides you with a Google Cloud service attachment, which you can use to connect to your cluster privately. 1. When creating your cluster, on the **Cluster Settings** tab, in the **Network** section: 1. Select **Private**. + 1. Enter your application's Google Cloud project ID. -1. After the cluster is created, go to the cluster details to see the corresponding Service Attachment. You need the Service Attachment while creating a PSC-connected endpoint. +1. After the cluster is created, go to the cluster details to see the corresponding service attachment. You need the service attachment while creating a PSC-connected endpoint. -1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. See [Step 2: Create a Connected Endpoint for the VM client / application](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). +1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. See [Step 2: Create a Connected Endpoint for the VM client/application](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). -1. In your application's Google Cloud, select **Private Service Connect**, and then select **Connected Endpoints**. Select the endpoint you created previously, and use the Service Attachment provided in the details section in BigAnimal to access your cluster. +1. In your application's Google Cloud, select **Private Service Connect**, and then select **Connected Endpoints**. Select the endpoint you created previously, and use the service attachment provided in the details section in BigAnimal to access your cluster. ## Using your Google Cloud account @@ -23,7 +25,7 @@ Two different methods enable you to connect to your private cluster from your ap - You can use Google Cloud [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer) to publish services using internal IP addresses in your VPC network. PSC is a network interface that securely connects a private IP address from your Google Cloud VPC to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource VPC, thus ensuring maximum network isolation. We refer to this process of connecting as using PSC-connected endpoints. -- We recommend the PSC-connected endpoint method and it is most commonly used. This method is described in this topic. However, you can also use the [VPC peering](vpc_peering) connection method, if required by your organization. +- We recommend the PSC-connected endpoint method and it is most commonly used. It's the method we describe in this topic. However, you can also use the [VPC peering](vpc_peering) connection method, if required by your organization. ### PSC-connected endpoint example This example shows how to connect your cluster using PSC-connected endpoints. @@ -31,87 +33,89 @@ This example shows how to connect your cluster using PSC-connected endpoints. Assume that your cluster is in a project called `development` and is being accessed from a client in another project called `test`. It has the following properties: - BigAnimal cluster: - - Google Cloud Project Project: development - - Google Cloud Project ID: development-001 - - BigAnimal Cluster ID: p-mckwlbakq5 - - Region where BigAnimal cluster is deployed: us-central1 - - BigAnimal Organization ID: brcxzr08qr7rbei1 - - Organization's domain name: biganimal.io - - Host Name: p-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io + - Google Cloud Project Project: `development` + - Google Cloud Project ID: `development-001` + - BigAnimal Cluster ID: `p-mckwlbakq5` + - Region where BigAnimal cluster is deployed: `us-central1` + - BigAnimal Organization ID: `brcxzr08qr7rbei1` + - Organization's domain name: `biganimal.io` + - Host Name: `p-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io` - VM Client: - - Google Cloud Project Name: test - - Google Cloud Project ID: test-001 - - VM Client/App: test-app-1 - - VM Client’s VPC: client-app-vpc - - VM Client’s Subnet: client-app-subnet + - Google Cloud Project Name: `test` + - Google Cloud Project ID: `test-001` + - VM Client/App: `test-app-1` + - VM Client’s VPC: `client-app-vpc` + - VM Client’s Subnet: `client-app-subnet` ### Prerequisites -To walk through an example in your own environment, you need: +To walk through an example in your own environment, you need a: -- A BigAnimal Postgres cluster deployed with private connectivity. -- A VM with a client/application installed in your Google Cloud project. -- The VM’s VPC has a subnet in the same region as the BigAnimal cluster. +- BigAnimal Postgres cluster deployed with private connectivity. +- VM with a client/application installed in your Google Cloud project. +- Subnet in the VM’s VPC in the same region as the BigAnimal cluster. -### Step 1: Publish a Service from BigAnimal +### Step 1: Publish a service from BigAnimal !!! Note - Performed in the Google Cloud project connected to your BigAnimal subscription. + Perform this procedure in the Google Cloud project connected to your BigAnimal subscription. In the Google Cloud project connected to BigAnimal, create a PSC Published Service to provide access to your cluster from other VPCs in other Google Cloud projects. Perform this procedure for each Postgres cluster to which you want to provide access. -1. Get the hostname of your Postgres cluster from the Connect tab of the Cluster page on the BigAnimal portal: -`P-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io`. +1. Get the hostname of your Postgres cluster from the Connect tab of the Cluster page on the BigAnimal portal (`P-mckwlbakq5.private.brcxzr08qr7rbei1.biganimal.io`). -1. Using Cloudshell, the command prompt, or other terminal, get the internal IP address of the host by performing a ping, nslookup, or dig +short <host> against the hostname: -`10.247.200.9`. +1. Using Cloudshell, the command prompt, or other terminal, get the internal IP address of the host by performing a ping, nslookup, or dig +short <host> against the hostname (`10.247.200.9`). -1. In the Google Cloud portal, go to Network Services > Load balancing. +1. In the Google Cloud portal, go to **Network Services > Load balancing**. -1. In the Filter area, choose Addresses under **LOAD BALANCERS**, and filter for the host IP (`10.247.200.9`) Note the load balancer name (`a58262cd80b234a3aa917b719e69843f`). +1. In the Filter area, choose Addresses under **LOAD BALANCERS**, and filter for the host IP (`10.247.200.9`). Note the load balancer name (`a58262cd80b234a3aa917b719e69843f`). -1. Navigate to **Private Service Connect -> PUBLISHED SERVICES -> + PUBLISH SERVICE. +1. Navigate to **Private Service Connect > PUBLISHED SERVICES > + PUBLISH SERVICE**. 1. Select **+ PUBLISH SERVICE**. 1. Under **Load Balancer Type**: + 1. Select **Internal passthrough Network Load Balancer** + 1. Paste the load balancer name (`a58262cd80b234a3aa917b719e69843f`) in the **Internal load balancer** field. - 1. For Service Name, give the published service a name (`p-mckwlbakq5`). - 1. For Subnets, choose RESERVE NEW SUBNET from the dropdown. + 1. For **Service Name**, enter the published service a name (`p-mckwlbakq5`). + 1. For **Subnets**, choose RESERVE NEW SUBNET. 1. In the Reserve subnet for Private Service Connect window, enter the following details, then select **ADD**. - 1. For Name, use the name of the Postgres cluster p-mckwlbakq5. - 1. For IPv4 range, assign the CIDR for the field IPv4 range. For example, 10.247.214.0/29. + 1. For **Name**, use the name of the Postgres cluster (`p-mckwlbakq5`). + + 1. For **IPv4 range**, assign the CIDR for the field IPv4 range. For example, `10.247.214.0/29`. !!! Note Recommendations for IP Range: - Allocate at least 8 IP addresses to the CIDR. The subnet mask should not be greater than 29. - Avoid overlap with other reserved IP ranges by not allocating too many IP addresses at one time. - If you encounter the error "This IPv4 address range overlaps with a subnet you already added. Enter an address range that doesn't overlap.", you’ll need to use another CIDR block (until no error returns). -1. (Optional) Add the consumer (where the client app resides) Google Cloud project ID (test-001) to accept connections automatically. +1. (Optional) Add the consumer (where the client app resides) Google Cloud project ID (`test-001`) to accept connections automatically. -1. ADD SERVICE and get the name of the service attachment. You may need to select the newly created Published service to find the name of the service attachment. (Service Attachment: projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5). +1. Select **ADD SERVICE** and get the name of the service attachment. You may need to select the newly created Published service to find the name of the service attachment. (`projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5`). -1. Proceed to Step 2: Create a Connected Endpoint for the VM client / application +1. Proceed to Step 2: Create a connected endpoint for the VM client/application. -### Step 2: Create a Connected Endpoint for the VM client / application +### Step 2: Create a connected endpoint for the VM client/application !!! Note - Performed in the Google Cloud project where your VM client / application resides. + You perform this procedure in the Google Cloud project where your VM client/application resides. -1. From the Google Cloud console, switch over to the project where your VM client / application resides (`test`). +1. From the Google Cloud console, switch over to the project where your VM client/application resides (`test`). -1. Go to **Compute Engine -> VM Instances -> Network Interface -> Network** to get the VPC of your VM(client-app-vpc). +1. Go to **Compute Engine > VM Instances > Network Interface > Network** to get the VPC of your VM (`client-app-vpc`). -1. Go to **Network Services -> Private Service Connect -> CONNECTED ENDPOINTS -> +CONNECT ENDPOINT** to create an endpoint with the VPC. - 1. For the Target, select Published service, and use the Service Attachment captured earlier (projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5). - 1. For the Endpoint name, use the name of your VM Client / App (test-app-1). - 1. For the Network (VPC), use the name of your VM Client’s VPC (client-app-vpc). - 1. For the Subnetwork, use your VM Client’s Subnet (client-app-subnet). +1. Go to **Network Services > Private Service Connect - CONNECTED ENDPOINTS > +CONNECT ENDPOINT** to create an endpoint with the VPC. + 1. For the Target, select Published service, and use the service attachment captured earlier (`projects/development-001/regions/us-central1/serviceAttachments/p-mckwlbakq5`). + + 1. For the Endpoint name, use the name of your VM client/application (`test-app-1`). + 1. For the Network (VPC), use the name of your VM Client’s VPC (`client-app-vpc`). + 1. For the Subnetwork, use your VM Client’s Subnet (`client-app-subnet`). !!! Note If no subnet is available, create a subnet in the VPC for the region where your Postgres cluster was created. Refer to the steps in [this knowledge base article](https://support.biganimal.com/hc/en-us/articles/20383247227801-GCP-Connect-to-BigAnimal-private-cluster-using-GCP-Private-Service-Connect#h_01H4NMNNSFQXNTX78W08Q3G39K). - 1. For the IP address, create an IP address, or choose an existing IP that is not used by the other endpoints + 1. For the IP address, create an IP address, or choose an existing IP that is not used by the other endpoints. 1. Enable Global Access. !!! Note If your VM is running in a different region from BigAnimal, then Global Access should always be enabled. From 4b25ca994a3fd3305866941a3d74eedd834b7cda Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Sat, 5 Aug 2023 02:44:20 +0000 Subject: [PATCH 6/9] Use correct path for PDF noindex headers ...maybe? --- gatsby-config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gatsby-config.js b/gatsby-config.js index 48814d8a2d2..3a13673d006 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -196,7 +196,7 @@ module.exports = { mergeCachingHeaders: false, allPageHeaders: isProduction ? [] : ["X-Robots-Tag: noindex"], headers: { - "/pdf/*": [ + "/docs/pdfs/*": [ "X-Robots-Tag: noindex", "X-Printshop-Directive: spiralbound", ], From 2cf0eb6a2014da4c17d0ca9073926caf5e2652ff Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Sat, 5 Aug 2023 02:46:34 +0000 Subject: [PATCH 7/9] Temp: build PDFs in draft deploy --- .github/workflows/deploy-draft.yml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/.github/workflows/deploy-draft.yml b/.github/workflows/deploy-draft.yml index 14e86e4efa5..08fa560ca96 100644 --- a/.github/workflows/deploy-draft.yml +++ b/.github/workflows/deploy-draft.yml @@ -50,6 +50,25 @@ jobs: - name: Run NPM install scripts run: | npm rebuild + + - uses: actions/setup-python@v4 + with: + python-version: "3.x" + - uses: r-lib/actions/setup-pandoc@v2 + with: + pandoc-version: "2.14.1" + - name: Install wkhtmltopdf + run: | + curl -L https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6-1/wkhtmltox_0.12.6-1.focal_amd64.deb > wkhtmltopdf.deb + sudo apt-get install ./wkhtmltopdf.deb + - name: Install Python dependencies + run: pip install -r requirements-ci.txt + - name: Install PDF Node dependencies + working-directory: ./scripts/pdf + run: | + npm install + - name: Build all pdfs + run: npm run pdf:build-all-ci - name: Checking Gatsby cache id: gatsby-cache-build From 9a0b4e55bb555446ca38af0e9f82dc2257ed8229 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 7 Aug 2023 03:45:02 +0000 Subject: [PATCH 8/9] Revert "Temp: build PDFs in draft deploy" This reverts commit b22c541538978ff767640ec50ab7287913f40c3e. --- .github/workflows/deploy-draft.yml | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/.github/workflows/deploy-draft.yml b/.github/workflows/deploy-draft.yml index 08fa560ca96..14e86e4efa5 100644 --- a/.github/workflows/deploy-draft.yml +++ b/.github/workflows/deploy-draft.yml @@ -50,25 +50,6 @@ jobs: - name: Run NPM install scripts run: | npm rebuild - - - uses: actions/setup-python@v4 - with: - python-version: "3.x" - - uses: r-lib/actions/setup-pandoc@v2 - with: - pandoc-version: "2.14.1" - - name: Install wkhtmltopdf - run: | - curl -L https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6-1/wkhtmltox_0.12.6-1.focal_amd64.deb > wkhtmltopdf.deb - sudo apt-get install ./wkhtmltopdf.deb - - name: Install Python dependencies - run: pip install -r requirements-ci.txt - - name: Install PDF Node dependencies - working-directory: ./scripts/pdf - run: | - npm install - - name: Build all pdfs - run: npm run pdf:build-all-ci - name: Checking Gatsby cache id: gatsby-cache-build From 46c94cd943392cc29fbf7ed15d5416531f7aa7c7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 7 Aug 2023 17:08:44 -0400 Subject: [PATCH 9/9] Fix BigAnimal link in release branch --- .../02_connecting_your_cluster/connecting_from_gcp/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx index a5f76914956..86c3f458a77 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx @@ -15,7 +15,7 @@ When using BigAnimal's cloud account, you provide BigAnimal with your Google Clo 1. After the cluster is created, go to the cluster details to see the corresponding service attachment. You need the service attachment while creating a PSC-connected endpoint. -1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. See [Step 2: Create a Connected Endpoint for the VM client/application](#step-2-create-a-vpc-endpoint-in-the-clients-vpc). +1. Create a connected endpoint in the client's VPC. The steps for creating a connected endpoint in the client's VPC are the same whether you're using BigAnimal's cloud or your cloud. See [Step 2: Create a connected endpoint for the VM client/application](#step-2-create-a-connected-endpoint-for-the-vm-clientapplication). 1. In your application's Google Cloud, select **Private Service Connect**, and then select **Connected Endpoints**. Select the endpoint you created previously, and use the service attachment provided in the details section in BigAnimal to access your cluster.