End of Sale Notice:

F5 NGINX is announcing the End of Sale (EoS) for NGINX Controller API Management Module, effective January 1, 2024.

F5 maintains generous lifecycle policies that allow customers to continue support and receive product updates. Existing NGINX Controller API- Management customers can continue to use the product past the EoS date. License renewals are not available after September 30, 2024.

See our End of Sale announcement for more details.
End of Sale Notice:

F5 NGINX is announcing the End of Sale (EoS) for NGINX Controller Application Delivery Module, effective January 1, 2024.

F5 maintains generous lifecycle policies that allow customers to continue support and receive product updates. Existing NGINX Controller Application Delivery customers can continue to use the product past the EoS date. License renewals are not available after September 30, 2024.

See our End of Sale announcement for more details.

Add an Azure NGINX Instance

Learn how to deploy an Azure NGINX instance using NGINX Controller.

Overview

You can use NGINX Controller to deploy and manage NGINX instances on Microsoft Azure.

This tutorial explains how to deploy NGINX Plus on Azure by defining an Azure Integration, a Location, and an Instance Template in NGINX Controller.

Important:
You are responsible for applying software and security updates on your NGINX instances. NGINX Controller does not manage these updates for you.

 

Before You Begin

Before you can create an Azure Integration in NGINX Controller, you need to register an app in Azure and create a client secret. You’ll need to copy and save the following information to use when creating an Azure Integration:

  • Application (client) ID
  • Directory (tenant) ID
  • Client secret value

Register an App in the Azure Portal

To register an app in Azure, take the following steps:

  1. Sign in to the Microsoft Azure Portal.

  2. Search for and select Microsoft Entra.

  3. Under Manage, select App registrations > New registration.

  4. Type a name to use for the app.

  5. Specify who can see the app.

  6. Select Register. The overview page for the app is displayed.

  7. On the app overview page, copy and save the following information:

    • Application (client) ID
    • Directory (tenant) ID

Add a Client Secret

To add a client secret to your app registration:

  1. Select your application in App registrations in the Azure portal.
  2. Select Certificates & secrets > New client secret.
  3. Add a description for your client secret.
  4. Select a duration.
  5. Select Add.
  6. Copy and save the secret’s value for use when creating an Azure Integration in NGINX Controller – this value is never displayed again after leaving this page.

 

Create an Azure Integration

Integrations give NGINX Controller permission to deploy and manage NGINX instances on external systems, such as cloud providers like Azure.

To create an Integration for Azure using the NGINX Controller API, send a POST request similar to the following example to the Integrations API endpoint.

In the JSON request, provide the clientID, tenantID, and clientSecret that you copied and saved when you registered an app with Azure.

{
  "metadata": {
    "name": "azure"
  },
  "desiredState": {
    "credential": {
      "type": "AZURE_SERVICE_PRINCIPAL",
      "clientID": "...",
      "clientSecret": "...",
      "tenantID": "..."
    },
    "type": "AZURE_INTEGRATION"
  }
}

 

Create a Location

After you’ve created an Integration for Azure, take the following steps to create a Location. Locations are a way to logically group your NGINX Plus instances by their physical locations. The Location you define in NGINX Controller corresponds to the Azure location that your resource group is running in.

Prerequisites

To create a Location, you’ll need your Azure resource group name, region, and subscription ID. To gather this information:

  1. Sign in to the Microsoft Azure Portal.

  2. Search for and select Resource groups.

  3. Select the name of your resource group. Make a note of this name to use for later.

  4. Under Essentials, copy and save the following information:

    • Subscription ID
    • Location

Create a Location by using the REST API

To create a Location using the NGINX Controller API, send a POST request similar to the following example to the Locations API endpoint.

In the JSON request, provide the resourceGroup name, region, and subscriptionID that you copied and saved in the previous steps.

{
  "metadata": {
    "name": "washington",
    "tags": []
  },
  "desiredState": {
    "type": "AZURE_LOCATION",
    "integrationRef": {
      "ref": "/platform/integrations/azure"
    },
    "resourceGroup": "...",
    "region": "...",
    "subscriptionID": "..."
  }
}

 

Create an Instance Template for Azure NGINX Instances

An Instance Template defines the parameters to use when creating an NGINX instance. Instance Templates are ideal for cloud orchestration and make managing your cloud resources easy and quick.

For the Instance Template, you can provide the details for an NGINX image on the Azure Marketplace, or you can provide the image and network details for your own instance. Refer to the NGINX Controller Technical Specifications guide for the NGINX Plus requirements.

  • To create an Instance Template for an Azure Marketplace image using the NGINX Controller REST API, send a POST request similar to the following example to the Instance Templates API endpoint. You can find descriptions of the instance parameters in the API Reference documentation.

    Tip:
    To look up the image details — publisher, offer, sku, and version — that you’ll need to define the Instance Template, you can attempt to deploy an NGINX instance from the Azure Marketplace and look at the template that Azure creates to get the image details.

     

    {
  "metadata": {
    "name": "us-west-azure"
  },
  "desiredState": {
    "type": "AZURE_INSTANCE_TEMPLATE",
    "image": {
      "type": "AZURE_IMAGE_REFERENCE",
      "publisher": "nginxinc",
      "offer": "nginx-plus-v1",
      "sku": "nginx-plus-ub1804",
      "version": "latest"
    },
    "instanceType": "Standard_A1",
    "adminUser": "azureuser",
    "publicKey": "<the complete ssh-rsa string>",
    "networkInterface": {
      "type": "AZURE_NIC_CONFIG",
      "name": "",
      "virtualNetwork": "",
      "subnet": "default",
      "securityGroup": "",
      "publicIpName": ""
    }
  }
}

  • To create an Azure Instance Template for your own instance using the [NGINX Controller REST API](/nginx-controller/api/reference/, send a POST request similar to the following example to the Instance Templates API endpoint.

    {
  "metadata": {
  "name": "my-azure-template-for-standard-A1",
  },
  "desiredState": {
    "type": "AZURE_INSTANCE_TEMPLATE",
    "image": {
      "type": "AZURE_IMAGE_ID",
      "imageID": "<the resource ID for the Azure image>"
    },
    "instanceType": "Standard_A1",
    "adminUser": "azureuser",
    "publicKey": "<the complete ssh-rsa string>",
    "networkInterface": {
      "type": "AZURE_NIC_ID",
      "nicID": "<the ID for the Azure network interface>"
    }
  }
}

 

Add an Azure NGINX Instance to NGINX Controller

Now that you’ve defined a Location and made an Instance Template for an NGINX instance on Azure, you’re ready to add the instance to NGINX Controller.

To add an Azure NGINX instance to NGINX Controller using the NGINX Controller REST API, send a POST request similar to the following example to the Instances API endpoint. For the templateRef parameter, use the Instance Template that you created in the previous procedure.

{
  "metadata": {
    "name": "azure1"
  },
  "desiredState": {
    "type": "AZURE_INSTANCE",
    "templateRef": {
      "ref": "/infrastructure/locations/washington/instance-templates/us-west-azure"
    }
  }
}

 

What’s Next