Skip to content

Commit eceeb24

Browse files
committed
NGINXaaS: clarify supported regions for network attachment
This adds clarity around the network attachment needing to be created in a supported region.
1 parent 693fa7d commit eceeb24

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

content/nginxaas-google/getting-started/create-deployment/deploy-console.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,9 @@ Before you can deploy NGINXaaS, follow the steps in the [Prerequisites]({{< ref
1818

1919
### Create a network attachment
2020

21-
NGINXaaS requires a [network attachment](https://cloud.google.com/vpc/docs/about-network-attachments) to connect your consumer Virtual Private Cloud (VPC) network and your NGINXaaS deployment's VPC network.
21+
NGINXaaS requires a [network attachment](https://cloud.google.com/vpc/docs/about-network-attachments) to connect your consumer Virtual Private Cloud (VPC) network and your NGINXaaS deployment's VPC network. The network attachment must be created in a region we support.
2222

23-
1. Access the [Google Cloud Console](https://console.cloud.google.com/).
24-
1. Create a consumer VPC network and subnetwork. See [Google's documentation on creating a VPC and subnet](https://cloud.google.com/vpc/docs/create-modify-vpc-networks#console_1) for a step-by-step guide.
25-
- The region you choose in this step must match the region where your NGINXaaS deployment will be created.
26-
1. Create a network attachment in your new subnet that automatically accepts connections. See [Google's documentation on creating a network attachment](https://cloud.google.com/vpc/docs/create-manage-network-attachments#console_1) for a step-by-step guide.
27-
1. Make a note of the network attachment ID. You will need it in the next steps to create your NGINXaaS deployment.
28-
29-
{{< call-out "caution" >}}NGINXaaS for Google Cloud currently supports the following regions:
23+
{{< call-out "caution" >}}NGINXaaS for Google Cloud currently supports the following regions:
3024

3125
{{< table "table" >}}
3226
|NGINXaaS Geography | Google Cloud Regions |
@@ -37,6 +31,12 @@ NGINXaaS requires a [network attachment](https://cloud.google.com/vpc/docs/about
3731

3832
{{< /call-out >}}
3933

34+
1. Access the [Google Cloud Console](https://console.cloud.google.com/).
35+
1. Create a consumer VPC network and subnetwork. See [Google's documentation on creating a VPC and subnet](https://cloud.google.com/vpc/docs/create-modify-vpc-networks#console_1) for a step-by-step guide.
36+
- The region you choose in this step must match the region where your NGINXaaS deployment will be created.
37+
1. Create a network attachment in your new subnet that automatically accepts connections. See [Google's documentation on creating a network attachment](https://cloud.google.com/vpc/docs/create-manage-network-attachments#console_1) for a step-by-step guide.
38+
1. Make a note of the network attachment ID. You will need it in the next steps to create your NGINXaaS deployment.
39+
4040
## Access the NGINXaaS Console
4141

4242
Once you have completed the subscription process and created a network attachment, you can access the NGINXaaS Console.

0 commit comments

Comments
 (0)