Frequently Asked Questions
Common questions about NGINX for Azure.
- Not currently. This enhancement is coming in a future release.
- Not currently. This enhancement is coming soon.
- Yes. If your DNS nameservers are configured in the same VNet used by your deployment, then you can use those DNS nameservers to resolve the hostname of the upstream servers referenced in your NGINX configuration.
- This capability is not currently available. This enhancement is coming soon.
- The agent gathers stats via an internal HTTP request incrementing the request count. The Azure service health probe checks for status via a TCP connection on port 80/443 incrementing the connection count. This contributes to minimal traffic and should not affect any of these metrics greatly.
The specific permission required to deploy NGINX for Azure are:
Additionally, if you are creating the Virtual Network or IP address resources which NGINX for Azure will be using, then you probably also want those permissions as well.
Note that assigning the managed identity permissions normally requires “Owner” role.
- NGINX for Azure does not currently report on the min and max of the NGINX metrics. In this case, the service will simply report a value of zero when either of these aggregation types are selected in Azure Monitor.
I created a new NGINX deployment using the Azure portal and noticed the subnet associated with my NGINX deployment does not have a Network Security Group (NSG). How do I secure my deployment?
- You can create an NSG, seed it with necessary rules to block and/or allow traffic, and associate the NSG to your subnet. We will ensure that NGINX deployments are secure by default in the future.