
Overview
Kubernetes is an open-source platform for scaling containerized workloads across a fleet of machines. It can intelligently schedule work only onto hosts that have the CPU and memory resources needed to run a given container. The challenge is that containers within a Kubernetes cluster typically communicate over a private overlay network. How should you expose services within the cluster to external clients? The answer is to bring the power of HAProxy to Kubernetes. The HAProxy Ingress Controller is the most efficient way to route traffic into a Kubernetes cluster.
Highlights
- Simplify your infrastructure by routing ingress traffic using one IP address and port. Requests are routed to the correct pod based on the Host header and request path
- Balance traffic among pods using any of HAProxy's load-balancing algorithms including round-robin, least connections, URL hash and random.
- Secure your cluster with built-in SSL termination, rate limiting, and IP whitelisting
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/month |
|---|---|---|
hap_ic_instance | One instance of HAProxy Enterprise Ingress Controller | $366.00 |
Vendor refund policy
We do not refund monthly or annual subscription.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Deploy Helm v1.47.1
- Amazon EKS
- Amazon EKS Anywhere
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Changelog from kubernetes-ingress-1.47.1: https://github.com/haproxytech/helm-charts/compare/kubernetes-ingress-1.45.0...kubernetes-ingress-1.47.4
Additional details
Usage instructions
Please, refer to the official documentation available at https://www.haproxy.com/documentation/kubernetes-ingress/enterprise/
Support
Vendor support
9am - 6pm | Critical Issue Target Response Time: 8 hrs | Email, Phone and Web | Prompt Maintenance and Updates | 24x7 support, significantly shorter SLAs, and consultative support available contact@haproxy.com Please activate your support license at https://www.haproxy.com/amazon-support-activation or contact us at contact@haproxy.com
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
Centralized monitoring has improved efficiency and provides faster responses to application issues
What is our primary use case?
My main use case for HAProxy is to load balance my applications and for Layer 4 of the OSI model.
I use HAProxy on GitLab to make commits on SSGador parts, and I have some Zabbix and Wazuh agents to monitor my applications.
What is most valuable?
The best feature HAProxy offers in my experience is its TCP functionality, as I don't use it for HTTPS because I use Traefik for that purpose. I use only the TCP protocol with HAProxy and not the HTTPS protocol.
HAProxy has positively impacted my organization because all of my applications are now centralized in one point, so I can manage it from my load balancer machine. I'm using a virtual machine on AWS , and it's very useful because I can now determine if one agent on Wazuh or Zabbix is out of range. This allows for better control and quicker responses to issues if the system goes down for an extended period, improving efficiency.
What needs improvement?
For the limited use that I have of HAProxy, I don't have any points to improve. I think I need more time with this tool, or perhaps I simply don't have areas that need to get better. I don't have additional thoughts about needed improvements, even if it's something small or just an idea for the future.
For how long have I used the solution?
I have been working in my current field for about eight months.
What was our ROI?
In terms of specific outcomes, I have seen approximately twenty dollars in cost savings because I was planning to use a load balancer from AWS . HAProxy is really useful and faster because I can see if the system or the agent on Wazuh or Zabbix goes down, which is truly helpful.
What other advice do I have?
The output of HAProxy is good, with a lot of information. It's a really good work tool. I don't have much to discuss about the output other than that it provides excellent information, allowing me to centralize all of the components that I have. It's really important because I can manage my applications more efficiently.
My advice to others looking into using HAProxy is to look at the documentation, which is really good, and to search for some use cases because they may find more benefits and improve their use of the tool better than I have now. I really recommend HAProxy to another IT business partner to use it. It's a really good tool, and if you use it well, you will gain a lot of benefits from it. I gave HAProxy a rating of ten out of ten.