Skip to content

NGINXaaS: clarify supported regions for network attachment #1313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

NGINXaaS: clarify supported regions for network attachment #1313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions content/nginxaas-google/getting-started/create-deployment/deploy-console.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,15 +18,9 @@ Before you can deploy NGINXaaS, follow the steps in the [Prerequisites]({{< ref

### Create a network attachment

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.
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.

1. Access the [Google Cloud Console](https://console.cloud.google.com/).
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.
- The region you choose in this step must match the region where your NGINXaaS deployment will be created.
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.
1. Make a note of the network attachment ID. You will need it in the next steps to create your NGINXaaS deployment.

{{< call-out "caution" >}}NGINXaaS for Google Cloud currently supports the following regions:
{{< call-out "caution" >}}NGINXaaS for Google Cloud currently supports the following regions:

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

{{< /call-out >}}

1. Access the [Google Cloud Console](https://console.cloud.google.com/).
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.
- The region you choose in this step must match the region where your NGINXaaS deployment will be created.
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.
1. Make a note of the network attachment ID. You will need it in the next steps to create your NGINXaaS deployment.

## Access the NGINXaaS Console

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