Overview
This offering includes a free, 30-day trial. Deliver applications with performance, reliability, security, and scale with NGINX Plus on AWS. Deploy quickly and cost-effectively, and benefit from speeds <30ms. NGINX plus is the all in one (yet surprisingly lightweight) load balancer, reverse proxy, API gateway and content cache. Try it for free today!
NGINX Plus brings enterprise-grade features such as session persistence, configuration via API, and active health checks so that you can add advanced application load balancing, monitoring and management to your AWS application stack. NGINX Plus is fully supported by NGINX and will help you deliver your apps with performance, reliability, security and scale from AWS.
Highlights
- NGINX Plus hourly or annual subscription, fully tested and supported by the NGINX engineering team.
- Core features include: HTTP/TCP/UDP load balancer; content cache, web server, HTTP/2, Dual-stack RSA/ECC SSL/TLS offloading; WebSockets; rate limiting; web acceleration; JWT authentication.
- Additional NGINX Plus features include: advanced load balancing methods, application health checks; session persistence; status monitoring; on-the-fly reconfiguration; support for Adobe HDS and Apple HLS; high availability.
Details
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
---|---|
c6g.4xlarge Recommended | $0.48 |
a1.2xlarge | $0.48 |
m6g.12xlarge | $0.48 |
r6g.16xlarge | $0.48 |
a1.medium | $0.48 |
m6g.xlarge | $0.48 |
r6g.large | $0.48 |
r6g.8xlarge | $0.48 |
c6g.12xlarge | $0.48 |
c6g.xlarge | $0.48 |
Vendor refund policy
We do not offer refunds for hourly usage fees after free trial has expired
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (Arm) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Release notes can be found at https://docs.nginx.com/nginx/releases/Â
Additional details
Usage instructions
When a new AMI is deployed for the first time, the latest version of NGINX Plus will be installed, auto-configured and started. NGINX Plus status can then be checked by running: service nginx status, and the NGINX Plus default index page will be accessible on public EC2 instance address. Please use SSH to access your instance for management purposes with the following usernames, for Ubuntu: "ubuntu", CentOS: "centos", Amazon Linux/RHEL: "ec2-user", Debian: "admin". NGINX Plus configuration can be found in /etc/nginx and the documentation is available on the instance locally (as a PDF), and at https://docs.nginx.com/nginx/Â .
Resources
Support
Vendor support
The Standard edition includes business hour access (9am-5pm, customer time zone) email and phone support for an unlimited number of incidents. SLA within 30 minutes for urgent Severity 1 requests, 24 hours response for low Severity requests. Documentation questions answered within 24 hours. Receive hot bug fixes and email notifications of all NGINX software updates. o engage our support team, please first activate your account at http://www.myf5.com where you'll be able to register and open To engage the F5 support team, please first activate your account at https://account.f5.com/myf5/signin/register where you'll be able to register and open a support case. For assistance on working in http://www.myf5.com and to open a support case, please see our complete self-help article at https://support.f5.com/csp/article/K23782072 . Support response times vary with
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Cost efficienct with robust proxy features but has installation hiccups
What is our primary use case?
I primarily use this solution for API management, WebSocket, and WebServer.
What is most valuable?
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.
What needs improvement?
Initially, I experienced hiccups whenever I installed the application. As with any application, there were initial issues, however, after receiving support, everything was rectified.
For how long have I used the solution?
I have been using the engineering solution for two months.
What do I think about the stability of the solution?
At this moment, it is stable.
How are customer service and support?
I receive very good support.
How would you rate customer service and support?
Neutral
What's my experience with pricing, setup cost, and licensing?
The solution offers a cost advantage.
What other advice do I have?
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.
Enables public access and secure configurations through reverse proxy
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with NGINX for seven months.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
Prior to NGINX, I didn't use any other similar solutions.
How was the initial setup?
The initial setup of NGINX was straightforward and very easy. It was completed in about one hour.
What about the implementation team?
The entire deployment process required only one person.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My use case involves using the free and open-source version of NGINX, making it cost-effective as I haven't incurred any costs.
Which other solutions did I evaluate?
I did not evaluate other options because NGINX is popular in the tech world and was an easy choice for me.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Gain visibility and network discovery with advanced capabilities
What is our primary use case?
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.
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Offers advanced load balancing, caching, security, and monitoring capabilities requires more technical expertise for setup and management
What is our primary use case?
I find NGINX Plus incredibly versatile. It is my go-to for serving web content efficiently, balancing loads across servers, and securely managing traffic as a reverse proxy. Plus, it is fantastic for streaming ports like SMTP and handling non-SAP protocol traffic.
What is most valuable?
Using NGINX Plus for web traffic distribution is fantastic. It offers performance similar to physical load balancers but with added flexibility. However, I have faced challenges with DNS configurations. Sometimes, updates to domain name IPs take time to reflect, causing delays or caching issues.
What needs improvement?
In terms of improvement, I would suggest adding GUI-based configuration panels to NGINX Plus to simplify setup and management tasks. This would allow users to easily create and manage policies, rules, load balancers, and traffic shaping without relying solely on the command line interface.Â
Additionally, another area for improvement in NGINX Plus is its integration with NGINX App Protect. Currently, to utilize NGINX Protect, you need to have NGINX Plus, which might not be necessary for everyone. It would be beneficial to have the option to use NGINX Protect independently without requiring NGINX Plus.
For how long have I used the solution?
I have been using NGINX Plus for a couple of years.
What do I think about the stability of the solution?
It is a fairly stable solution.
What do I think about the scalability of the solution?
NGINX Plus is scalable and allows us to increase server capacity according to our desired configurations.
How was the initial setup?
Setting up NGINX Plus is generally straightforward and not very complex. While some modules may not be included in the documentation, finding and installing them is manageable. The deployment process is relatively simple and can be started right away, especially if you have prior knowledge of NGINX.Â
For deploying and maintaining NGINX Plus, the team size varies based on the environment's scale. In a large setup, we might need four to five people, while in smaller environments, two technically sound individuals can handle it.
What was our ROI?
The return on investment for NGINX Plus depends on factors like cost and management ease. Compared to hardware load balancers, NGINX Plus can be pricier, but it offers flexibility and scalability. However, other hardware load balancers like Array may have lower upfront costs and easier setup.
What's my experience with pricing, setup cost, and licensing?
The pricing of NGINX Plus is a bit steep compared to other options I have used. NGINX Plus licensing is annual or three-year based, and it is socket-based. You pay for the license according to the number of server sockets you need. The license is bound to a specific server or virtual server, so it can't be used across multiple servers unless you opt for a multi-tenant license.
What other advice do I have?
NGINX Plus greatly improved my API management and delivery. I configured multiple routes with load balancing and efficient logging, which helped troubleshoot issues effectively. While the dashboard lacked customization, the product performed well, offering about 80% similarity to NGINX open source with additional modules and support. Its scalability allowed me to upgrade server resources rather than invest in new hardware, saving costs as my traffic increased.
Using load balancing with NGINX, both in the open-source version and NGINX Plus, improved service reliability. While the open-source version required manual reconfiguration if a server went down, NGINX Plus's traffic monitoring automatically detects and removes faulty servers, ensuring seamless traffic management.Â
NGINX Plus's caching mechanism is highly effective in speeding up web content delivery.Â
I would recommend NGINX Plus to those seeking an alternative to hardware-based load balancers. However, it is important to note that NGINX Plus is quite technical, primarily command-line-based with less emphasis on GUI. While support is available, administrators should be comfortable with technical configurations. Compared to GUI-based load balancers, NGINX Plus offers flexibility but requires more technical expertise for setup and management.
Overall, I would rate NGINX Plus as a six out of ten.