Deployment issues for new customers

Currently, all new-customer deployments are non-functional. Existing customers deploying into a new region are also affected. See Known Issues for updates.

Deploy NGINX as a Service for Azure

Learn how to create an NGINX as a Service for Azure deployment.

Find the NGINX as a Service for Azure offer in the Azure portal

  1. Sign in to the Azure portal with your Azure account.

  2. Use the Azure portal to find the NGINXaaS for Azure offer.

  3. Select Marketplace from the available options (or search for Marketplace).

    NGINXaaS for Azure offer
  4. Search for NGINXaaS - An Azure Native ISV Service offer in the Marketplace.

    NGINXaaS for Azure available offer
  5. Select the offer to Subscribe.

Create a deployment

Basics tab

  1. On the Create NGINXaaS Deployment Basics page, provide the following information:

    Resource Basics Tab


    Field Description
    Subscription Select the appropriate Azure subscription that you have access to.
    Resource group Specify whether you want to create a new resource group or use an existing one.
    For more information, see Azure Resource Group overview.
    Name Provide a unique name for your deployment.
    Region Select the region you want to deploy to.
    Pricing Plan Select the Public Preview plan.
    Billing Term Select Monthly (only option supported currently).

  2. Select Next: Networking.

Networking tab

  1. On the Create NGINXaaS Deployment Networking page, provide the following information:

    Resource Networking Tab

    Field Description
    Virtual Network A virtual network is required for communication between the resources you create.
    You can create a new virtual network or use an existing one (for an existing one see note below).
    Additionally, you can peer a new virtual network with existing ones (in any region) to create network access from NGINXaaS for Azure to your upstream servers. To peer the virtual network with another see Create, change, or delete a virtual network peering.
    Subnet If you selected an existing virtual network, you can select the existing subnet to be used.
    Otherwise, if you have chosen to create a new virtual network, a new subnet will be selected by default. The minimum size subnet is /27; however, we recommend a subnet size of /24.
    The subnet can contain other resources and is not dedicated to the NGINXaaS for Azure resource.
    Allow NGINX access to Virtual Network Confirm that you allow:
    - Registration of the NGINX provider to your Azure subscription.
    - Delegation of the subnet to the NGINX provider.
    IP address Set the IP address (public or private) that the service listens to for requests:

    If you select a public IP address:
    - Create a new public IP or use an existing one (for an existing one see the note below).
    - Set the resource name for your public IP address.
    Newly created public IPs are zone-redundant in supported regions.

    If you select a private IP address:
    - Provide a static IP address from the same subnet range set previously.

  2. Select Next: Tags.

Note:

If you are selecting existing Network resources (VNET, Public IP), then the following caveats apply:

  • The subnet used by NGINXaaS for Azure needs to have a Network Security Group (NSG) applied to it to ensure your deployment is locked down and only allows inbound connections on ports that the NGINX service is listening on.

Tags Tab

  1. Add custom tags for the new NGINXaaS Deployment. Each tag consists of a name and value.

    Resource Tags Tab
  2. After adding the tags, select Next: Review+Create

Review + Create Tab

  1. On the Review + create tab, your configuration is validated. You can review the selections made in the previous screens.

    Resource Review+Create Tab
  2. After validation has succeeded and you’ve reviewed the terms, select Create for Azure to start the deployment.

    Resource Deployment
  3. After the deployment finishes, select the NGINX deployment to view information about the deployed resource.

    Resource Deployment Completed

Test Your Deployment

At this point, you can go to the IP address noted on the overview page to test your deployment. You will get the default NGINX welcome screen.

Note:
Update the network security group associated with the subnet used by this deployment by opening up TCP port 80 (HTTP) inbound. This allows you to browse to the IP address.

Test Deployment

What’s Next