You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/nginxaas-google/getting-started/create-deployment/deploy-console.md
+171-2Lines changed: 171 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,20 +85,189 @@ In the NGINXaaS Console,
85
85
86
86
To set up connectivity to your NGINXaaS deployment, you will need to configure a [Private Service Connect backend](https://cloud.google.com/vpc/docs/private-service-connect-backends).
87
87
88
-
1. Access the [Google Cloud Console](https://console.cloud.google.com/).
88
+
1. Access the [Google Cloud Console](https://console.cloud.google.com/) and choose a project where you would like to create resources for connecting to your F5 NGINXaaS deployment.
89
+
1. Create or reuse a [VPC network](https://cloud.google.com/vpc/docs/create-modify-vpc-networks).
90
+
1. Create a proxy-only subnet in your consumer VPC. See [Google's documentation on creating a proxy-only subnet](https://cloud.google.com/load-balancing/docs/tcp/set-up-ext-reg-tcp-proxy-zonal#console_1) for a step-by-step guide.
89
91
1. Create a public IP address. See [Google's documentation on reserving a static address](https://cloud.google.com/load-balancing/docs/tcp/set-up-ext-reg-tcp-proxy-zonal#console_3) for a step-by-step guide.
90
92
1. Create a Network Endpoint Group (NEG). See [Google's documentation on creating a NEG](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends#console) for a step-by-step guide.
91
93
- For **Target service**, enter your NGINXaaS deployment's Service Attachment, which is visible on the `Deployment Details` section for your deployment.
92
94
- For **Producer port**, enter the port your NGINX server is listening on. If you're using the default NGINX config, enter port `80`.
93
95
- For **Network** and **Subnetwork** select your consumer VPC network and subnet.
94
-
1. Create a proxy-only subnet in your consumer VPC. See [Google's documentation on creating a proxy-only subnet](https://cloud.google.com/load-balancing/docs/tcp/set-up-ext-reg-tcp-proxy-zonal#console_1) for a step-by-step guide.
95
96
1. Create a regional external proxy Network Load Balancer. See [Google's documentation on configuring the load balancer](https://cloud.google.com/load-balancing/docs/tcp/set-up-ext-reg-tcp-proxy-zonal#console_6) for a step-by-step guide.
96
97
- For **Network**, select your consumer VPC network.
97
98
- For **Backend configuration**, follow [Google's step-by-step guide to add a backend](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends#console_5).
98
99
- In the **Frontend configuration** section,
99
100
- For **IP address**, select the public IP address created earlier.
100
101
- For **Port number**, enter the same port as your NEG's Producer port, for example, port `80`.
101
102
103
+
{{< call-out "note" >}}
104
+
If you have multiple ports configured on NGINX, you will have to create a new network endpoint group for every port. You can also automate these steps by using the following helper script:
105
+
106
+
```bash
107
+
#!/bin/bash
108
+
109
+
# Default values
110
+
PROJECT=""
111
+
REGION=""
112
+
NETWORK=""
113
+
SA_URI=""
114
+
PORTS="80"
115
+
116
+
# Prerequisites:
117
+
# - gcloud CLI installed and configured
118
+
# - An existing projectID and a VPC network created in that project
119
+
# - A valid Service Attachment URI from F5 NGINXaaS
1. To test your deployment, go to the IP address created in [Set up connectivity to your deployment]({{< ref "/nginxaas-google/getting-started/create-deployment/deploy-console.md#set-up-connectivity-to-your-deployment" >}}) using your favorite web browser.
0 commit comments