NGINX Controller 3.0 is a complete platform upgrade that introduces application-centric management of your NGINX Plus-based infrastructure. It includes a self‑service portal for RBAC-based collaboration, a DevOps-optimized API, and a built-in certificate manager.
NGINX Unit 1.13.0 introduces reverse proxying, and version 1.14.0 adds address-based routing to the internal routing and file-serving functionality from previous releases. We combine the new features in a complete configuration example for IP address filtering and access management.
Release 1.6.0 of the NGINX Ingress Controller for Kubernetes, with improvements to NGINX Ingress Resources, support for OpenTracing, and much more.
NGINX Plus R20 builds on the enhancements made in R19 to rate limiting, adding real-time monitoring and logging; connection limiting now has the same features. We also added prefix matching in the key-value store, DNS resolution per upstream group, new PROXY Protocol variables, and improved security for HTTP/2.
Sort by
Filter by category
Rewind 2019: Highlights from the NGINX Blog
As 2019 comes to an end, we take a moment to look back at the most popular and noteworthy moments from the NGINX blog.
Customer Success with NGINX Plus: mobilcom-debitel Achieves 60% Cost Reduction, Enhanced Performance with Apigee Rip-and-Replace
In his session at NGINX Conf 2019, Felix Colaci of mobilcom-debitel shares how his team replaced Apigee with NGINX Plus as their API gateway. NGINX Plus reduced costs by 60% and improved reliability and performance. It fits perfectly into mobilcom-debitels CI/CD pipeline, enabling software update in minutes.
Real-Time APIs: Trends and Adoption
APIs are playing an increasingly important role in digital transformation at enterprises, in every vertical and region. We review trends in API usage as reported by industry analyst IDC, and explain how NGINX solves the challenges that companies face in deploying and managing APIs.
Using NGINX as a DoT or DoH Gateway
DNS over TLS (DoT) and DNS over HTTPS (DoH) are two emerging technologies for securing Domain Name System (DNS) traffic. In this post we take a look at the history of DNS and show how to implement DoT, DoH, and a DNS filter using NGINX Open Source and NGINX Plus.
How Real-Time APIs Power Our Lives
Many popular mobile apps rely on "real-time" APIs, which can process an API call end-to-end in under 30 milliseconds. Explore many real-world examples --- ride hailing, cashierless stores, credit card fraud detection, and IoT -- and learn why you need NGINX, the only real-time API solution.
Tapping NGINX for AI-Powered Insight into API Traffic
PingIdentity provides an NGINX integration with its AI-driven solution for API security, PingIntelligence for APIs. The solution uses API metadata collected by NGINX to determine whether API clients are granted access. PingIntelligence for APIs also provides dashboards, reports, and anomaly detection.
Application Isolation With NGINX Unit
Application isolation in NGINX Unit enables you to control which types of system resources your apps share with NGINX Unit and each other. Running apps in isolated environments improves security. Get all the details on how it works, and what it means for the future of NGINX Unit.
The Microservices World of Tomorrow…Today
Microservices is one technology that is leading the march towards digital transformation in the world of application development. With their high performance and small footprint, NGINX and NGINX Plus are ideal for microservices, both as API gateways and Kubernetes Ingress controllers.
Enabling OpenTracing with the NGINX Ingress Controller for Kubernetes
Trace the traffic in your Kubernetes cluster end-to-end with native support for OpenTracing when using the NGINX and NGINX Plus Ingress Controllers for Kubernetes for load balancing. Our step-by-step instructions show you how to get started, using Docker containers and Jaeger.
Addressing the PHP-FPM Vulnerability (CVE-2019-11043) with NGINX
We provide guidance on using NGINX to mitigate the recently discovered vulnerability in PHP-FPM (CVE-2019-11043). The vulnerability is triggered when the PATH_INFO variable passed to PHP-FPM with an invalid value, which can happen in a common NGINX configuration.