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
Reliability has supported AI gateway routing and currently secures LLM traffic with flexible policies
What is our primary use case?
I am currently working with NGINX Ingress Controller but in a different perspective than before. We haven't used App Protect anymore, but as an implementer, we use it as a front end for an AI gateway to do some mapping for certain information before sending the LLM request to the AI gateway.
NGINX Ingress Controller itself is a reverse proxy, so we manipulate some requests. We utilize NGINX Ingress Controller to manipulate some requests prior to the AI gateway.
My use case has changed because nowadays the main focus for use cases are for AI and AI security that mainly focuses on LLM security.
What is most valuable?
A third-party solution would be better for that. NGINX Ingress Controller is a software, so its capability of working is fitting inside the organization, not facing the internet. The one that faces the internet is something else, for example, the firewall or Big-IP, so normally we do the whitelisting at those levels, not the NGINX Ingress Controller layer.
Most customers are satisfied with the reverse proxy capability, but the main issue is that the Ingress NGINX , the one that is most widely used, will be deprecated this month. I think that is the main concern from the customer side, but normally NGINX Ingress Controller just works well and is reliable.
From my experience, I think the main benefit NGINX Ingress Controller provides to the end user is the reliability of NGINX Ingress Controller itself. The customer can rely on this service that it will work well, and there will be no problem or issue that they need to concern.
What needs improvement?
In my opinion, NGINX Ingress Controller can make better improvements for ingress control, and I think they are already the leader in the Ingress and Gateway API. The Gateway API has the capability to separate the gateway responsible for the FQDN and certificate management. They separate this part within the gateway, and another part is the HTTP route which will load balance to the backend service. F5 has this kind of deployment for many years before the announcement of the Gateway API itself.
Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller.
For how long have I used the solution?
I have been working with NGINX Ingress Controller for approximately seven years.
How was the initial setup?
I think the initial setup process for NGINX Ingress Controller is simple.
What other advice do I have?
I would like to see some AI capabilities, in-built AI capabilities in NGINX Ingress Controller to help with the load balancing.
Normally, customers just use the normal load balancer, and that is fine. The advanced features we try to introduce include many advanced features, for example, a blue-green deployment, load balancing to service based on header values, and many things, including JWT, but normally customers just use the basic load balancer. Most customers use TLS termination. Most customers use it, and they terminate the certificate at NGINX Ingress Controller level. NGINX Ingress Controller can do whitelisting, but they usually use a different product. For example, a Big-IP to do whitelisting instead of NGINX Ingress Controller.
We have some projects integrating NGINX Ingress Controller with Prometheus including Grafana . The integration is working well, and there is no problem about that.
Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller. I am totally satisfied with NGINX Ingress Controller if we talk about the functionality part.
I think the price is acceptable, but the issue is not about the price. The issue is about the commonness. Load balancing and Ingress is some kind of generic use case, so there are no exciting features, such as an AI feature or something of that nature.
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.