![]() ![]() Publish Configs with Hash Versioning to Instances.Use the Instance Manager REST API to add a commit hash to NGINX configurations if you use version control, such as Git.įor more information, see the following topics: Our new and improved Certificates and Keys webpage makes it easier than ever to efficiently manage your TLS certificates.Īdd commit hash details to NGINX configurations for version control The Certificate and Keys webpage has a new look! For a list of the supported distributions, refer to the NGINX Plus Technical Specs guide.Įvents will be triggered for CREATE, UPDATE, and DELETE actions on Templates, Instances, Certificates, Instance Groups, and Licenses. The NGINX Agent supports the same distributions as NGINX Plus. The NGINX Agent now supports Rocky Linux 8 (x86_64, aarch64) and 9 (x86_64, aarch64). You can also publish these packages using the precompiled publication mode. The Instance Manager web interface now allows you to view Attack Signatures and Threat Campaign packages published to instances and instance groups. New webpages for viewing Attack Signature and Threat Campaigns If your Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version. Instance Manager 2.9.1 supports upgrades from these previous versions: Instance Manager supports the following versions of NGINX App Protect WAF: Instance Manager SELinux errors encountered when starting NGINX Management Suite on RHEL9 with the SELinux policy installed (41327) Installing NGINX Agent on FreeBSD fails with “error 2051: not implemented” (41157) Select an issue’s ID link to view its details. When NGINX Management Suite is installed using a Helm Chart, it now defaults to a ClusterIP without an external IP address. Using systems or instance groups allows a user to see all certificates but restricts access for publishing.īy default, NGINX Management Suite is not exposed to the internet when installed with a Helm Chart Using certificates as an object controls the viewing and assigning of specific certificate and key pairs. Role Based Access Control for SSL Certificate and Key management can now use three different objects for precise controls: certificates, systems, and instance groups. Improvements to Role Based Access Control for SSL Certificate and Key management ![]() Instance Manager 2.10.0 has the following changes in default behavior: The NGINX Agent installation script now has a flag to enable the default configuration required for the Security Monitoring module. New NGINX Agent install flag for Security Monitoring You can now explicitly enable or disable ICMP scanning at the top of the “Scan” interface. These can be used to publish App Protect WAF configurations in precompiled_publication mode.Īdd option to toggle ICMP scanning in the web interface Using a user-provided NGINX repository certificate and key after the first setup of the WAF compiler, Instance Manager can automatically retrieve WAF compilers associated with NGINX App Protect instances. ![]() Instance Manager can now automatically retrieve WAF compilers associated with NGINX App Protect instances This reflects configuration for NGINX, NGINX App Protect policies, Attack Signatures, and Threat Campaigns. The most recent publication date and status for an instance’s configuration is now visible on App Security Pages. More about the VirtualServer custom resource can be found here: Ĭonfiguration Publication Status now visible in App Security pages The NGINX Management Suite Helm Chart can now generate an NGINX Ingress Controller VirtualServer definition, which can be used to expose NGINX Management Suite when running in your Kubernetes cluster. NGINX Management Suite can now use NGINX Ingress Controller to manage routing Other module versions are also visible, though older versions of API Connectivity Manager and Security Monitoring may appear as undefined. You can now look up the NGINX Management Suite and NGINX Instance Manager versions in the web interface and API. NGINX Management Suite version now visible in the web interface and API It is used to retrieve the deployment status and precompiled_publication mode, with an option for the NGINX App Protect WAF instance to use the mode for policies. The NGINX Agent installation script now has a flag to enable the default configuration required for NGINX App Protect WAF. New NGINX Agent install flag for NGINX App Protect WAF Categories for event entries include “Certs,” “Instance Groups,” and “Templates.” You can now filter entries in the Events web interface using a new “Category” filter. New “Category” Filter in the Events web interface ![]() This release includes the following updates: See Also: Refer to the Upgrade Guide for important information and steps to follow when upgrading Instance Manager and the NGINX Agent. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |