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: examples/aws.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,10 @@ upstreams:
26
26
autoscaling_group: backend-two-group
27
27
port: 80
28
28
kind: http
29
+
- name: backend
30
+
autoscaling_group: backend-*
31
+
port: 80
32
+
kind: http
29
33
```
30
34
31
35
* The `api_endpoint` key defines the NGINX Plus API endpoint.
@@ -34,6 +38,6 @@ upstreams:
34
38
* The `region` key defines the AWS region where we deploy NGINX Plus and the Auto Scaling groups.
35
39
* The `upstreams` key defines the list of upstream groups. For each upstream group we specify:
36
40
* `name` – The name we specified for the upstream block in the NGINX Plus configuration.
37
-
* `autoscaling_group` – The name of the corresponding Auto Scaling group.
41
+
* `autoscaling_group` – The name of the corresponding Auto Scaling group. Use of wildcards is supported.
38
42
* `port` – The port on which our backend applications are exposed.
39
-
* `kind` – The protocol of the traffic NGINX Plus load balances to the backend application, here `http`. If the application uses TCP/UDP, specify `stream` instead.
43
+
* `kind` – The protocol of the traffic NGINX Plus load balances to the backend application, here `http`. If the application uses TCP/UDP, specify `stream` instead.
Copy file name to clipboardExpand all lines: vendor/github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2019-07-01/compute/virtualmachinescalesetvms.go
0 commit comments