NGINX Plus R18 introduces dynamic loading of SSL/TLS certificates, enhances our OpenID Connect reference implementation, and supports port ranges for virtual servers. It also includes enhancements to the key-value store, health checks, NGINX Plus clustering, and the NGINX JavaScript module.
There are always concerns when an enterprise acquires open source projects. NGINX CEO Gus Robertson explains why F5 is committed to maintaining and growing NGINX Open Source and other open source projects.
NGINX Plus covers all API gateway use cases, from traditional monoliths to distributed microservices. No need for the separate microgateway that first-generation API management vendors have had to bolt onto their solutions to handle modern application architectures.
NGINX Unit 1.8.0 introduces internal routing of requests based on host, URL, and HTTP method, This sets the framework for full Layer 7 request processing, necessary for further development of Unit's web server functionality.
Sort by
Filter by category
Is Your API Management Solution Really Secure?
Is your API management solution secure when vulnerabilities are found? The NGINX team builds patches into the NGINX Controller API Management Module as soon as they're available. Third-party solutions built on NGINX can leave you vulnerable while vendors test and port patches.
Protecting SSL Private Keys in NGINX with HashiCorp Vault
The second post of our series about protecting SSL private keys shows how to set up HashiCorp Vault to store the passwords that protect private keys, and to configure NGINX to retrieve the passwords. We also discuss using a hardware security module for even greater security.
Testing the Performance of the NGINX Ingress Controller for Kubernetes
This blog describes the performance you can achieve with the NGINX Ingress Controller for Kubernetes, in terms of three metrics: requests per second, SSL/TLS transactions per second, and throughput. The full NGINX and Kubernetes configurations we used are included.
Over-the-Air Updates to IoT Devices with NGINX
One of the biggest challenges in scaling deployments on the Internet of Things is device management, particularly over-the-air updates, commonly called OTA. Guest blogger DeveloperSteve shows how to automate OTA using NGINX as an API gateway, along with the NGINX JavaScript module.
Secure Distribution of SSL Private Keys with NGINX
We describe three progressively more secure ways to protect SSL private keys when configuring NGINX to handle HTTPS traffic: allowing read access only to the root user, encrypting keys with separately stored passwords, and distributing passwords from a central repository.
Ask NGINX | March 2019
In this installment of our "Ask NGINX" series, we describe how NGINX and NGINX Plus support Nagios, single sign-on, and MQTT; discuss storing cookies in the NGINX Plus key-value store; and explain how to upgrade NGINX Plus licenses from a free trial to a paid subscription.
Securing Your API Ecosystem with the NGINX Controller API Management Module
The NGINX Controller API Management Module secures your APIs at every API touchpoint – authenticating and authorizing third-party client applications and developers, rate limiting API calls to mitigate DDoS attacks, and protecting backend applications that process the API calls.
Do I Need a Service Mesh?
"Service mesh" is a hot topic, but as of early 2019 most implementations are not production-ready. In this blog we offer advice on adopting existing technologies that are likely to meet the needs of all but the most complex applications until such time as service mesh is more mature.
NGINX to Join F5: Proud to Finish One Chapter and Excited to Start the Next
F5 and NGINX today announced an agreement under which F5 will acquire NGINX for approximately $670 million. Hear from NGINX CEO Gus Robertson on why NGINX + F5 is a powerful combination that will ‘bridge the divide’ between NetOps and DevOps.
Simplifying API Definition with the NGINX Controller API Management Module
With NGINX Controller’s API Management Module, you define an API just once and publish it to as many environments as you want. This “create once, publish many” approach eliminates user errors as well as saving time and effort, especially if you have to define a lot of APIs.