Overview
HAProxy Enterprise enables modern application delivery at any scale and in any environment, including on AWS. Fast and efficient load balancing improves application performance and reliability (2 million RPS on a single Arm-based AWS Graviton2 instance). Multi-layered security protects applications against DoS, bots, abuse, and layer 7 application attacks. Observability features enable fast issue resolution, pro-active prevention, and informed capacity planning.
Simple to deploy and administer, with flexible service discovery, RESTful Data Plane API, single sign-on (SSO), zero downtime reloads, automatic dynamic updates of ACL/Map files, SSL/TLS certificate automation (including Let's Encrypt integration and OCSP stapling), device detection and geolocation databases.
HAProxy Enterprise on AWS is compatible with HAProxy Fusion for centralized management, monitoring, and automation, including support for AWS Auto Scaling groups, Route 53, and CloudWatch. This combination simplifies the management and observability of your load balancing and WAF layers at scale.
Highlights
- Load balancing: Fast and reliable, high availability, wide protocol support, choice of algorithms, and complex routing logic.
- Security: Multi-layered defense for apps and APIs with SSL/TLS, bot management and crawler validation, rate limiting, and web application firewall (WAF).
- Observability: Advanced logging, Prometheus integration, SNMP, end-to-end request timing, OpenTracing.
Details
Unlock automation with AI agent solutions

Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Free trial
- ...
Dimension | Cost/hour |
---|---|
c5.xlarge Recommended | $0.35 |
t3.micro AWS Free Tier | $0.35 |
x1.32xlarge | $0.35 |
m5d.24xlarge | $0.35 |
m6idn.large | $0.35 |
inf1.2xlarge | $0.35 |
c3.2xlarge | $0.35 |
d2.4xlarge | $0.35 |
m6in.4xlarge | $0.35 |
x2idn.32xlarge | $0.35 |
Vendor refund policy
We do not refund hourly usage or annual subscription.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) 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.
Additional details
Usage instructions
Launching AMI: Deploy the HAProxy Enterprise AMI using the instance size of your choice. We recommend choosing an instance with at least 2 CPUs and with at least 8 GB RAM. Select the instance size, agree to the subscription terms, and follow the AMI configuration instructions.
Connecting to Instance: Once the AMI has been launched and fully booted (instance is being shown as healthy) you can connect to it using the SSH key pair that you selected while launching the instance.
Use the following command to connect to the instance depending upon the operating system that you selected. Please make note of the instance IP and connect either through private IP (from bastion host) or through public IP (EIP):
Ubuntu: ssh -i <private key> ubuntu@<ec2 IP> Red Hat Enterprise Linux: ssh -i <private key> ec2-user@<ec2 IP>
Starting and Managing the service: The HAProxy Enterprise service will automatically run upon initialization. You can manage the process using systemctl.
To view the process status run systemctl status hapee-3.0-lb
Quick Start Guide: https://www.haproxy.com/amazon-quickstart-guide/Â Complete Documentation: https://www.haproxy.com/documentation/hapee/Â
Resources
Support
Vendor support
9am - 6pm | Critical Issue Target Response Time: 8 hrs | Email and Web | Prompt Maintenance and Updates. We are available at contact@haproxy.com if you require 24x7 support, significantly shorter SLAs, and consultative support. 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 SSL handling and load distribution have reduced downtime and improved operational efficiency
What is our primary use case?
My main use case for HAProxy is for my project, which focuses on full high availability. I use HAProxy for load balancing between my two apps while connecting to Keepalived. HAProxy is very helpful for myself and my team, utilized primarily for load balancing as it is powerful for that purpose.
What is most valuable?
The best feature that HAProxy offers is load balancing, as the ability to balance both transport TCP and application HTTP or HTTPS layers gives much flexibility. SSL termination is also essential, handling SSL efficiently as HAProxy supports dynamic certificate storage. Moreover, health check functionality is significant, as HAProxy constantly checks backend servers to ensure they are healthy and pulls them out of rotation if not, preventing server traffic issues.
One of the biggest wins with HAProxy has been SSL termination, as before using HAProxy, I had to install and renew SSL certificates on each backend server individually, which was time-consuming and error-prone. By moving all SSL termination to the load balancer, I now manage certificates in a single place, and I can also utilize Let's Encrypt with HAProxy's built-in ACME support, making renewal automatic. For example, we had a small cluster of app servers for a client project where each server served the same domain. Originally, every server had its own cert, leading to issues when scaling up or replacing instances, but after offloading SSL to HAProxy, the backend servers only need to communicate via plain HTTP, while HAProxy handles all the TLS handshakes.
What needs improvement?
HAProxy is already a robust solution, but there are a few areas for potential improvement, especially regarding configuration complexity. The configuration syntax is powerful yet can become overwhelming for newcomers; a more beginner-friendly interface or a native GUI without relying on third-party tools would ease the onboarding process. Built-in observability could be enhanced; while HAProxy features great logging and stats, utilizing Grafana , Prometheus, or external tools for in-depth insights is still necessary. Native service discovery could be improved; although dynamic scaling works, it generally requires DNS or runtime API scripting. More features in the Community Edition would be beneficial, as the Enterprise version contains advanced security, WAF , and bot protection that would be advantageous for smaller teams if included in the community build.
Another area that could see improvement is documentation and onboarding resources. HAProxy's documentation is very detailed but can feel dense for newcomers, and finding practical, step-by-step examples often requires sifting through mailing lists, GitHub issues, or blog posts. More modernized guide tutorials and real-world playbooks would simplify getting started for beginners, so enhancing technical improvements to make HAProxy more approachable through better docs and a stronger community ecosystem would significantly assist in broader adoption.
Additionally, an important area for improvement is tighter integration with cloud ecosystems, particularly AWS . Native AWS service discovery would be advantageous; currently, one usually relies on DNS or external scripts to register new EC2 instances in HAProxy, but direct hooks into AWS Auto Scaling Groups, ECS, or EKS would facilitate automatic joining and leaving of instances without added glue code. Furthermore, direct integration with AWS Certificate Manager or Secrets Manager could reduce manual steps surrounding SSL, TLS, and backend credentials management. Enhancing cloud-native integration, especially with AWS services, could significantly strengthen HAProxy's plug-and-play appeal in cloud environments.
For how long have I used the solution?
I have been using HAProxy for maybe two or three months, as I just explored HAProxy and the configuration.
What do I think about the stability of the solution?
In my experience, HAProxy is remarkably stable; we haven't encountered crashes or unexpected downtime. Once running, it simply continues to operate without issues, and any downtime we've faced was linked only to planned upgrades or configuration changes, not the software itself. This reliability serves as a key reason for our choice, providing us with confidence even when faced with heavy traffic.
What do I think about the scalability of the solution?
From my experience, HAProxy's scalability is excellent; as our traffic expands, it handles load increases effortlessly.
How are customer service and support?
Our interaction has primarily been with community resources rather than the official support team. Since we are utilizing the open-source edition, community forums, mailing lists, and GitHub have been invaluable, with typically someone having encountered the same problems we faced. We haven't needed to submit a ticket to HAProxy Technologies' support team, but based on feedback I've seen, they are responsive and knowledgeable. For now, the combination of the open-source community and documentation has sufficed in resolving our issues, so I would rate community support as strong, but if guaranteed SLAs or direct assistance are required, then enterprise support would be the go-to option.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before adopting HAProxy, we relied on NGINX as our primary reverse proxy and load balancer. NGINX served our basic use cases adequately, but we faced challenges as our traffic increased. The first challenge was flexibility; HAProxy offered more advanced load-balancing algorithms and health checks than we configured in NGINX. Next, dynamic configuration was a concern, as reloading config in NGINX led to occasional connection drops. HAProxy's hitless reloads and runtime API represented a notable improvement. Lastly, in heavy traffic tests, HAProxy demonstrated superior performance when handling concurrent connections, yielding lower latency and higher throughput in our setup. The shift wasn't due to any deficiencies in NGINX—it's still a solid option—but HAProxy simply aligned better with our scaling and reliability requirements as our infrastructure evolved.
How was the initial setup?
Since adopting HAProxy, we've seen some remarkable improvements backed by numbers, particularly in downtime reduction. Before using HAProxy, we experienced small outages almost monthly due to backend servers going offline during cert renewals, but after centralizing load balancing and SSL management in HAProxy, those incidents have dropped to near zero with our uptime becoming consistent. Our average response time during peak load dropped by about 20 percent with connection pooling and Keepalived.
What was our ROI?
We've definitely seen a clear return on investment from using HAProxy, even while sticking with the open-source edition. Time savings have been significant; previously, SSL cert renewals across multiple servers took a couple of hours each quarter. With centralized SSL termination and automated renewals now in place, that time requirement has dropped to nearly zero hours, translating to dozens of hours saved per year. Operational efficiency has improved; we no longer have staff consistently monitoring backend servers during deployment or scaling events, as HAProxy's health checks and hitless reloads allow us to push changes with minimal manual intervention. This has freed up our operations team for higher-value work. Lastly, improved uptime stands out, with our uptime statistics rising from around 98% to consistently above 99.900, meaning reduced SLA penalties while keeping our clients happier.
What's my experience with pricing, setup cost, and licensing?
Our experience with pricing, setup costs, and licensing has been quite straightforward. Since we use the open-source edition, there are no licensing fees, with the main cost being the infrastructure running on EC2Â instances in AWS, which helps maintain low expenses. Regarding the setup cost, the primary investment centers on time and expertise; while HAProxy is incredibly powerful, the initial setup requires a bit of a learning curve. However, once the configuration templates are established, adding new applications or backends becomes easy. We haven't opted for HAProxy Enterprise yet, so there are no licensing complexities. In summary, using the open-source version incurs low financial costs but requires an upfront effort to set up, resulting in an overall cost-effective experience.
Which other solutions did I evaluate?
We evaluated a few other options before deciding on HAProxy. The primary alternatives were AWS ELB and Application Load Balancer; while they are convenient and integrated, they are also less flexible and their costs add up when compared to operating HAProxy on our own instances.
What other advice do I have?
My advice for others considering HAProxy is to not be dissuaded by its learning curve; it's wise to start with a simple load-balancing setup and gradually incorporate advanced features such as ACLs, SSL termination, or rate limiting as confidence grows. Additionally, leveraging community resources and example configurations can save substantial time. Furthermore, if you're managing mission-critical workloads, it may be worthwhile to contemplate whether HAProxy Enterprise could provide the additional support and features desired. My guidance is to initially keep things simple, rely on documentation or the community, and expand into the more powerful features once the foundational stability is established. I rate HAProxy 9 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Used for load balancing, but its dashboard and reporting could be improved
What is most valuable?
We use the solution for load balancing.
What needs improvement?
The solution's implementation and troubleshooting are not easy. The solution's dashboards and reports could be improved.
For how long have I used the solution?
I have been using HAProxy for 12 years.
What do I think about the stability of the solution?
We didn’t face any issues with the solution’s stability.
I rate the solution’s stability an eight out of ten.
What do I think about the scalability of the solution?
HAProxy is a very good solution for small and medium sized businesses.
I rate the solution’s scalability an eight out of ten.
How are customer service and support?
Since HAProxy is an open-source product, we did not receive support. However, there are some sites where we can receive support, and that support is not good.
How would you rate customer service and support?
Neutral
How was the initial setup?
The solution’s initial setup is not easy.
What's my experience with pricing, setup cost, and licensing?
HAProxy is an open-source solution.
Which other solutions did I evaluate?
F5 is HAProxy's main competitor in the market. If its implementation, dashboard, and reporting are improved, HAProxy could be better than F5.
What other advice do I have?
If your team knows the product well, integrating HAProxy with IT workflow is easy. Otherwise, it is not easy. I would recommend the solution to other users.
Overall, I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Useful for for small and quick load-balancing tasks
What is our primary use case?
I use the tool mostly for small and quick load-balancing tasks. Additionally, I integrate it with Docker because the integration is quite fine.
What is most valuable?
What I like best about the product is its simplicity and speed. When you need to set up a load balancer quickly, HAProxy offers options like sticky sessions and round-robin. It's also fast to configure, including adding SSL for security. While it may have fewer options than other solutions like F5, HAProxy gets the job done for basic load-balancing tasks.Â
The reliability features of HAProxy were particularly useful in a scenario where I needed to test load balancing between two Tomcats. Since these domains were inaccessible, I set up a third Docker with HAProxy, which had access to the Tomcat domains. I then configured HAProxy to handle the load balancing. This setup allowed the client to interact with HAProxy.Â
The solution's integration with other elements is easy.Â
What needs improvement?
Improving the documentation with multiple examples and scenarios would be beneficial. Most users encounter similar situations, so having a variety of scenarios readily available on the tool's website would be helpful. For instance, if I were part of the HAProxy team, I'd create a webpage with different scenarios and provide files for each scenario. This way, users wouldn't have to start from scratch every time.Â
For how long have I used the solution?
I have been using the product for six years.Â
What do I think about the stability of the solution?
I rate the tool's stability a nine out of ten.Â
What do I think about the scalability of the solution?
I've only deployed a single instance and focused on monitoring it.Â
How are customer service and support?
I haven't had direct experience with their technical support team. Whenever I encounter issues, I usually turn to Stack Overflow. I've found that other users often have similar problems, and I can usually find solutions there.
What's my experience with pricing, setup cost, and licensing?
The tool is open-source.Â
What other advice do I have?
I rate the overall product an eight out of ten. It is good and famous.Â
Which deployment model are you using for this solution?
Helps distribute the server load but has only the basic features
What is our primary use case?
The solution is used for high availability. We use it for the backend to distribute the load.
How has it helped my organization?
We needed a simple proxy system that is open source. HAProxy was the most used tool for any issues that we ran into. We did not want to use something that was not used much so that we could fix the issues that came up.
What is most valuable?
The solution is effective in managing our traffic. The integrations work fine. It's a load balancer. There's no need for complex integration. We hit it, and it balances the load in the servers that we assigned to it.
What needs improvement?
The product has the basic foundations of any load-balancing product. It is simple and basic. The product does not have any new technologies.
For how long have I used the solution?
I have been using the solution for a few years.
What do I think about the stability of the solution?
The tool seems very stable. I have not heard of the infrastructure team having any issues with it.
What do I think about the scalability of the solution?
The tool is scalable. We have everything we need.
What's my experience with pricing, setup cost, and licensing?
The product is open source.
What other advice do I have?
There are better tools, but the product does the job well. All my colleagues know the tool and have used it. I recommend the product to others. Companies that have complex environments must not choose HAProxy. Overall, I rate the solution a seven out of ten.
Offers good integration capabilities but needs to improve the monitoring part
What is our primary use case?
I use the solution in my company for TCP streams. I have not used the product for web servers like Apache and NGINX. I have used the product for SMTP and SMPP protocols. I also used the tool for email services and POP3 servers. HAProxy handles the area where traffic has to be forwarded from one port to another very well.
What needs improvement?
HAProxy is very weak in the logging and monitoring part and requires improvement.
In the future, the tool should have additional modules for different purposes.
For how long have I used the solution?
I have experience with HAProxy.
What do I think about the stability of the solution?
HAProxy's TCP load balancer is excellent and super stable.
What do I think about the scalability of the solution?
I have not had the opportunity to use this scalability feature of the product, but I know that it depends on the machine or the hardware on which the tool is loaded. I would say that it is a scalable product since it is a software-based solution.
I can speak about the services being used on the product since there is no user interaction required with HAProxy. I can say that my company uses more than 50 services on HAProxy.
Which solution did I use previously and why did I switch?
I use DNS Made Easy.
How was the initial setup?
If a Linux user who is fairly good with Linux products takes care of HAProxy's installation part, it can be done easily.
It is possible to deploy the product within one to three hours with a fair amount of knowledge.
The product's deployment process is straightforward, as it can be easily managed with the help of HAProxy's document, which is available on its website. Users should be familiar with some Linux commands.
The solution is deployed on the cloud and on-premises models.
HAProxy is similar to engine NGINX, especially if you have a small company since you need only one or two people to take care of the deployment process. If you have a big enterprise, five to ten people are required to take care of the deployment phase.
What was our ROI?
HAProxy is preferable when the company wants a load balancer to manage the traffic and doesn't want to spend on a high-end load balancer. The product helps save costs for the company.
What's my experience with pricing, setup cost, and licensing?
I use the open-source version of the product. I don't have experience with the licensed version of the solution.
What other advice do I have?
I have used load balancing on the TCP layer. I have not used the product for areas like HTTP and HTTPS. I have not used the product for web or API applications. I have only used the product for the TCP part.
HAProxy improved our company's applications' availability. I had a use case in my company where we had to connect to one of my voice servers from a back-end proxy for which I had used HAProxy. HAProxy helped me when I had to distribute the traffic between all the voice servers from a single application in my company.
HAProxy's most valuable feature for network traffic management stems from the functionalities attached to the area revolving around TCP load balancers since it has helped me achieve excellent results.
To those who plan to use the product, I would say that they need to consider including the HTTP proxy part product, similar to the offerings made by NGINX. The product's potential users can introduce a lot of modules, which can help HAProxy when compared with NGINX.
I did not face any challenges with the integration capabilities of the product. My organizational objectives were achievable with HAProxy.
Considering the tool's TCP part, I rate the overall tool a seven out of ten.