NGINX has released version 1.3.0 of the NGINX Ingress Controller for Kubernetes. This release features Prometheus support, better Helm charts, mergeable Ingress resources, easier custom template management, health checks, and status reporting. Come to Github and get it.
The $ssl_preread_protocol variable introduced in NGINX 1.15.2 allows you to distinguish between SSL/TLS and other protocols when forwarding traffic using a TCP proxy. This is useful if you want to avoid firewall restrictions by running (for example) SSL/TLS and SSH services on the same port.
The NGINX Web Application Firewall (WAF) is now certified in the Google Cloud Security Partner Ecosystem, protecting applications hosted on the Google Cloud Platform from Layer 7 attacks like SQLi and RCE.
Red Hat OpenShift is a container platform built on top of Kubernetes. It's available as an open source project, OpenShift Origin, and a commercially supported product, OpenShift Container Platform. You can now use NGINX and NGINX Plus as a Router within OpenShift.
NGINX Unit 1.3, available now, adds configuration parameters for various timeouts, configurable request body size, Ansible integration, and more. As in previous releases, all parameters can be defined dynamically, with no disruption to running services or loss of connectivity.
NGINX Controller R1, a new management tool for NGINX Plus instances, was released June 26th, 2018. It offers simplified configuration management; monitoring, alerting and troubleshooting; tagging; a configuration analyzer; instance inventory; and multi-cloud support.
NGINX Controller launches today. With an intuitive interface, Controller helps you configure, deploy, and monitor instances, set up alerts, create dashboards, and troubleshoot. With NGINX Controller, you can reduce costs and improve performance, reliability, and availability for NGINX Plus.
NGINX Unit 1.2, available now, adds environment variables across application languages, versions, and sessions; php.ini configuration; and command-line configuration for Go executables. Parameters can still be defined dynamically, with no disruption to running services or loss of connectivity.
In the second post in our API gateway series, Liam shows you how to batten down the hatches on your API services. You can use rate limiting, access restrictions, request size limits, and request body validation to frustrate illegitimate or overly burdensome requests.
It's easy to implement PCI DSS best practices, such as using new versions of TLS rather than the older SSL, encrypting upstream as well as downstream communications, and adding a WAF, with NGINX Plus. Taking these steps will help you pass PCI DSS audits. Here's how to implement them.