Overview

This document provides details about using NGINX configuration files with your F5 NGINX as a Service for Azure deployment, restrictions, and available directives.

NGINX configuration common user workflows

NGINX configurations can be uploaded to your NGINXaaS for Azure deployment using the Azure portal, Azure CLI, or Terraform. The following documents provide detailed steps on how to upload NGINX configurations:

• Upload using the Azure portal
• Upload using the Azure CLI
• Upload using Terraform

The topics below provide information on NGINX configuration restrictions and directives that are supported by NGINXaaS for Azure when using any of the above workflows.

NGINX configuration automation workflows

NGINX configurations stored in GitHub can be applied to existing NGINXaaS for Azure deployments using custom GitHub Action workflows. See NGINXaaS for Azure Deployment Action for documentation and examples on how to incorporate these workflows in your GitHub Actions CI/CD pipelines.

NGINX filesystem restrictions

NGINXaaS for Azure places restrictions on the instance’s filesystem; only a specific set of directories are allowed to be read from and written to. Below is a table describing what directories the NGINX worker process can read and write to and what directories files can be written to. These files include certificate files and any files uploaded to the deployment, excluding NGINX configuration files.

Attempts to access other directories will be denied and result in a 5xx error.

Disallowed configuration directives

Some directives are not supported because of specific limitations. If you include one of these directives in your NGINX configuration, you’ll get an error.

You may find that a few directives are not listed here as either allowed or disallowed. Our team is working on getting these directives supported soon.

Directives that cannot be overridden

Some directives cannot be overridden by the user provided configuration.

Configuration directives list