2022
Learn about the updates, new features, and resolved bugs in F5 NGINXaaS for Azure during the year 2022.
To see the latest changes, visit the Changelog page.
To see a list of currently active issues, visit the Known issues page.
We have rolled out a fix that addresses the issue, and new customers or existing customers in a new region can create deployments.
Users can now leverage System Assigned Managed Identities with their deployment. The lifecycle of the identity is tied to the lifecycle of the corresponding deployment. See Managed Identity Types for more information.
NGINXaaS for Azure has new restrictions on file paths for certificate files, njs files, etc. See the NGINX Filesystem Restrictions table for more information. Existing configurations will not be affected unless they need to be updated.
Please visit the Logging Support documentation for more information on exporting NGINX logs with NGINXaaS for Azure.
NGINXaaS for Azure is now available in the following additional regions:
- West US 2
- East US
- Central US
- North Central US
See the Supported Regions documentation for the full list of supported regions.
Affecting new deployments only, two njs files in different subdirectories may share the same filename. For example:
```
js_path "njs";
js_import d1 as d1/test.js;
js_import d2 as d2/test.js;
```
This change improves the readability of some errors that may be returned when a certificate cannot be applied.
Added default access_log and error_log to NGINX configurations in preparation for upcoming logging features. Requires a config push to be applied.
For more information on caching with NGINXaaS for Azure, please visit the Basic Caching documentation.
For information on rate limiting with NGINXaaS for Azure, please visit the Rate Limiting documentation.
NGINXaaS for Azure is now available for public preview. Give it a try! If you find any issues please let us know by raising a support ticket.
Visit the Known issues section to learn about the issues present in this release.