Overview

Product video
NGINX Ingress Controller is a best-in-class traffic management solution for cloud-native apps in Kubernetes and containerized environments in Amazon EKS. Get your free 30-day trial today!
In a CNCF survey, nearly two-thirds of respondents reported using the NGINX Ingress Controller (more than all other controllers combined) and NGINX Ingress Controller has been downloaded more than 10 million times on DockerHub. Combining the speed and performance of NGINX with the trust and security behind the power of F5, NGINX Ingress Controller is synonymous with high-performing, scalable, and secure modern apps in production.
This is the official implementation of NGINX Ingress Controller (based on NGINX Plus) from NGINX. It is high-performance, production-ready, and suitable for long-term deployment. We focus on providing stability across releases, with features that can be deployed at enterprise scale. Included in this subscription is NGINX's award-winning support.
Highlights
- Advanced app-centric configuration: Use role-based access control and self-service to set up security guardrails, so your teams can manage their apps securely and with agility. Enable multi-tenancy, reusability, simpler configs, and more.
- Visibility and performance monitoring: Pinpoint undesirable behaviors and performance bottlenecks to simplify troubleshooting and make fixes faster.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/unit/hour |
|---|---|---|
Hours | Container Hours | $0.53 |
Vendor refund policy
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
EKSDelivery
- Amazon EKS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Additional details
Usage instructions
This container requires Kubernetes and can be deployed to EKS. Review the installation instructions https://docs.nginx.com/nginx-ingress-controller/installation/ and utilize the deployment resources available https://github.com/nginxinc/kubernetes-ingress/tree/v3.7.2/deployments Use this image instead of building your own.
Support
Vendor support
To engage our support team, please first activate your account at http://www.myf5.com , where you'll be able to register and open a support case. For info on MyF5 support, please see our complete help article at
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
Smart traffic control has improved reliability and has protected critical APIs under heavy load
What is our primary use case?
My main use case for NGINX Ingress Controller is as a smart traffic controller, with the built-in firewalls, DoS protections for our APIs, and better reliability under load.
Whenever we need to manage traffic, we have contact with our tenants, so we create the hostname with their name and define a pod for them, allowing NGINX Ingress Controller to automatically scale the software and increase the number of pods when the number of users for this hostname increases, ensuring we don't lose traffic and the whole site doesn't go down.
Additionally, we can use advanced traffic and routing management, plus monitoring tools with their APIs. Whenever a site goes down or any error occurs, we receive instant error notifications through the API, which is really helpful.
What is most valuable?
In my experience, the best features NGINX Ingress Controller offers are its integration systems, which easily connect with other NGINX API gateways, risk limiting, JWT validations, and other NGINX products.
The integration with other analytics products enhances our team's capabilities as we use NGINX App Protect with NGINX Ingress Controller to protect the whole site using firewalls from denial of service, while the JWT validation helps protect our site from unauthorized access.
NGINX Ingress Controller has positively impacted our organization by saving us a lot of time. Previously, we used the NGINX open source ingress that lacked support and reliability, so when we switched to the official controller, it saved us time, reduced our downtime, and allowed for safe releases.
What needs improvement?
One improvement I see for NGINX Ingress Controller is that the obvious downside is the cost, as you pay for the license on top of AWS infrastructure and the pricing is not cheap. However, compared with the cost of development time, downtime, or buying multiple tools, it is often justified, so cost awareness is still necessary.
I would like to see a more visual management UX and even stronger AWS native integration patterns.
For how long have I used the solution?
I have been using NGINX Ingress Controller for about one year.
What do I think about the stability of the solution?
NGINX Ingress Controller is quite stable in my experience.
What do I think about the scalability of the solution?
NGINX Ingress Controller's scalability is quite reliable and very easy to scale, as it mostly operates intelligently on its own without needing manual scalability.
How are customer service and support?
Customer support is very great and is one of the good points about NGINX Ingress Controller. I would rate customer support a ten because they are very helpful.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used Traefik, which was very cheap, but it was not as powerful as NGINX Ingress Controller, so we switched.
What was our ROI?
I have seen a return on investment as mentioned. We saved about ten to fifteen engineering hours per month and a single outage annually.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was good. The pricing was expensive at first, but throughout the journey, it became feasible.
Which other solutions did I evaluate?
Before choosing NGINX Ingress Controller, we evaluated other options such as Amazon ALB Controller, Kong's ingress controller, and HAProxy , among others.
What other advice do I have?
My advice for others looking into using NGINX Ingress Controller is that if you have a large number of users and need auto-scaling, you should definitely go with NGINX Ingress Controller, but if you are just starting out and are new, I would not recommend this.
NGINX Ingress Controller is quite good. Its integration is really helpful, and customer support is also good as they usually connect us to the developer when needed, making it easy to get things done. I give this product a rating of nine 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?
Nginx Ingress controller
It provides variety of solution to meet the modern requirements
#1 solution for Kubernetes management
It is the best controller available in the market for traffic management.
The best part about this controller is that it is very easy to use as well as to implement.
It is also very useful to integrate with various other solutions. In case of any issues or concerns that we face as a customer we get the best customer support possible and instant support.
We have been using it on a daily basis and from time to time it also provides high realiability and sustainability.
I cannot think of any major issues of failures that you observed over the years and it has been a very stable solution.
There are no major drawbacks or points to dislike about this solution.
The cost of the controller is a little higher but it is worth the money.
The best part about this controller is that it is very efficient for kubernetes traffic management and helps our kubernetes systems load balancing as well as efficient working.
It is very easy to use implement and integrate with various other solutions.
The best part about this controller is that it increases the stability sustainability robustness and reliability in kubernetes environments.