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.
NGINX Plus Standard - Amazon Linux 2 (LTS) ARM Graviton
NGINX, Inc. | v1.17Linux/Unix, Amazon Linux 2 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
Gain visibility and network discovery with advanced capabilities
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using this technology for the last five to ten years, so we are familiar with how it works.
What do I think about the stability of the solution?
I have not encountered any challenges with NGINX's stability, as it works effectively with Big IP, XC, and Palo Alto.
How are customer service and support?
Support is available in the market with options like FYSE, which provides assistance during critical tasks.
Which solution did I use previously and why did I switch?
We have experience using Palo Alto Networks, Sophos, SonicWall Firewalls, and other technologies.
What's my experience with pricing, setup cost, and licensing?
NGINX is not cost-effective, especially for few applications, and is considered higher-priced.
Which other solutions did I evaluate?
Alternatives evaluated include Redway, cloud solutions, and services providing CDN options. Some gaps exist in NGINX not covering certain API options.
What other advice do I have?
I would rate the solution an eight and a half out of ten. It's important to understand the requirements before recommending its implementation.
Functions as both a reverse proxy and a web server, offering a lot of flexibility and performs well
What is our primary use case?
We use NGINX as a reverse proxy. For example, if you access www.google.com, NGINX accepts the external traffic and forwards it to the internal application servers.
What is most valuable?
NGINX can also be used for load balancing, which makes it better than Apache in a lot of cases. Additionally, it functions as both a reverse proxy and a web server, offering a lot of flexibility.
Moreover, it performs very well. That's one of the primary reasons we use NGINX.
What needs improvement?
I would like the configuration process to be more simplified. Both Apache and NGINX involve some complex configuration steps. Easier configuration and troubleshooting would make it a perfect ten for me.
For how long have I used the solution?
I've used NGINX Plus for about one and a half years. However, I'm not actively configuring it right now since I'm working on microservices.
I've deployed NGINX Plus both within AWS EC2 instances and on our on-premises virtual machines.
What do I think about the stability of the solution?
I haven't experienced any major performance issues.
What do I think about the scalability of the solution?
Around 100 people had access to it. In my previous team, around 10 to 14 engineers were actively using it for configuration and management.
It's quite scalable. We can host multiple frontend applications on it.
Which solution did I use previously and why did I switch?
I used Apache. I configured Apache as a web server for a front-end web application deployment. I used it on a Linux virtual machine.
I actively used Apache for over a year. We configured applications for front-end hosting and used Apache as a web server to route traffic from the public to the virtual machine. It was listening on port 80 or 443 and forwarding traffic to the internal application.
I used it more than a year ago. Since then, I've primarily been using NGINX.
How was the initial setup?
I've installed NGINX several times, and it was straightforward. It was not a tedious task, so the process was easy.
NGINX's graphical user interface is fine. I've deployed frontend applications.
What's my experience with pricing, setup cost, and licensing?
There's an open-source version of NGINX that is free. There's also NGINX Plus, which is a paid version with additional features.
What other advice do I have?
I would recommend it because it's a very versatile tool for load balancing and other scenarios. For example, you can use it to host front-end applications.
I would give NGINX an eight out of ten. It's great for load balancing, reverse proxying, and serving as a web server. Its versatility makes it superior to Apache in many ways. I haven't tried other similar tools, so that's why I wouldn't give it a perfect ten.