NGINX Plus Premium - RHEL 8 AMI

I am generally satisfied with NGINX Plus ; it is good, the policies are fine-tuned and superb, but there are vulnerabilities in that platform which were exploited in the wild some months last year.

Load balancing in NGINX Plus  is used by the IT team mostly because they manage it; from the security perspective, I focus on the policies and the signatures and how they are configured.

The web application firewall feature has helped enhance security for our applications because most of the attacks which are performed on our website are being blocked by it, so the web application firewall is good.

Operation is very good; we have not much impact because most of our attacks from different countries are blocked to it, and we have also whitelisted and blacklisted some countries, so the traffic is also very minimal, and the attacks which have been detected are also from a region from where the traffic is allowed, but it is very minimal, and the detection capabilities are also good.

There were some vulnerabilities in F5.

They tried to fix it, but the fixes were not available at the time because they were zero days, so they attempted to fix it, but their support was not proper.

Their support should be improved because sometimes features which we need for customization take time, and they are sometimes feasible and sometimes not feasible by the team, so their support and the engineering team should improve their product.

I would like to see more features regarding customization which should be built into the application, and the tool optimization should be good, and the dashboard should be more crisp and clear.

I have been working with NGINX Plus for three years.

I would rate their technical support an eight out of ten.

Response time is good because they have assigned and dedicated support engineers to us, and we have weekly cadence calls. If we have any issues with the product, we discuss that, and they also provide us any updates if there are any major changes with new features or whatever we need.

I was part of the configuration for the initial setup.

It was not that straightforward, but it was fine; we were able to manage it, and it took time.

Integrations were the difficulties I faced with the deployment.

We have seen a return on investment with NGINX Plus, and we have calculated that based on our analysis.

Pricing is reasonable and that is fine.

Applications were particularly problematic to integrate with NGINX Plus, and because sometimes there were customers facing applications which were not integrated properly. I would rate this review an eight out of ten overall.

I primarily use this solution for API management, WebSocket, and WebServer.

I use NGINX , which is integrated with our engineering server, SparkFi. We are using NGINX Plus , which functions as a responsible application, serving as a reverse proxy and a small web server. For API management, the WebSocket, and the WebServer, NGINX provides a cost advantage, value addition, and effective support.

Initially, I experienced hiccups whenever I installed the application. As with any application, there were initial issues, however, after receiving support, everything was rectified.

I have been using the engineering solution for two months.

At this moment, it is stable.

I receive very good support.

The solution offers a cost advantage.

Not much maintenance is required. My experience spans six to seven applications. Initially, I had hiccups whenever I installed the application. After receiving support, everything was rectified. I am happy with it now. For the initial hiccups, I received adequate support, and as of now, I am content with the solution.

Overall product rating: 8 out of ten.

I use NGINX  to port our local server to a public server where people can access the URL. The main use case is for reverse proxy to support our local server, making it publicly accessible through our DNS system.

The primary valuable feature of NGINX  for me is its ability to provide a reverse proxy. I have found that this feature supports our local server, and I am able to connect through our DNS system, making it accessible publicly.

Additionally, the integration with SSL certificates and the configuration capabilities make it a valuable solution for my use case. Without NGINX, users would not be able to access our application, which means there is positive ROI from using NGINX as it is crucial for the functioning of my organization.

One area of improvement could be that NGINX could provide a means to generate self-signed SSL certificates. This would eliminate the need to use third-party software such as SaaS Boost for generating these certificates.

I have been working with NGINX for seven months.

NGINX is very stable. In my use case, I require ninety-nine point nine percent uptime, and NGINX has been pivotal in helping me achieve this along with our other DNS services. I have not encountered any stability issues.

While some people use NGINX for web servers, my current use case focuses on networking and tunneling, which does not necessitate much scaling. However, by adding more resources to our system, I can maintain and ensure everything runs smoothly.

Prior to NGINX, I didn't use any other similar solutions.

The initial setup of NGINX was straightforward and very easy. It was completed in about one hour.

The entire deployment process required only one person.

Without NGINX, users would not be able to access our application, which means there is positive ROI from using NGINX as it is crucial for the functioning of my organization.

My use case involves using the free and open-source version of NGINX, making it cost-effective as I haven't incurred any costs.

I did not evaluate other options because NGINX is popular in the tech world and was an easy choice for me.

NGINX is a great product for anyone interested in reverse proxy. It is a reliable solution and has proven effective in my use case. I would recommend it to anyone considering similar needs.

The overall product rating is ten out of ten.

The primary use cases involve using NGINX  for various features including WAF , API security, DDoS protection, and bot protection. Additionally, it facilitates network discovery and provides visibility into network activities, allowing us to uncover solutions and identify any areas we might have missed.

I utilize NGINX  for its capability to provide visibility and discovery options. It helps discover and identify networks, which is crucial for ensuring application performance, managing latency, and checking server reachability. NGINX communicates with XE and uses Linux command terminology, thus providing visibility by interacting with the nearest POP.

The need for human involvement is high due to the complexity of NGINX's Linux-based terminology. More tactics and techniques can enhance its usability. Additionally, it is not a cost-effective solution for few applications.

We have been using this technology for the last five to ten years, so we are familiar with how it works.

I have not encountered any challenges with NGINX's stability, as it works effectively with Big IP, XC, and Palo Alto.

Support is available in the market with options like FYSE, which provides assistance during critical tasks.

We have experience using Palo Alto Networks, Sophos, SonicWall Firewalls , and other technologies.

NGINX is not cost-effective, especially for few applications, and is considered higher-priced.

Alternatives evaluated include Redway, cloud solutions, and services providing CDN  options. Some gaps exist in NGINX not covering certain API options.

I would rate the solution an eight and a half out of ten. It's important to understand the requirements before recommending its implementation.