Amazon Web Services offers AWS WAF (web application firewall) to protect web applications from malicious behavior that might impede the applications functioning and performance, with customizable rules to prevent known harmful behaviors and an API for creating and deploying web security rules.
$0.60
per 1 million requests
Kemp LoadMaster
Score 8.0 out of 10
N/A
LoadMaster from Kemp Technologies in New York is an application delivery controller.
Well Suited: 1. To prevent DDOS attacks: AWS WAF has a lot of managed rules to prevent DDOS attacks based on traffic origination from a particular IP or IP reputation etc. 2. To rate-limit requests: Well it sounds familiar like preventing DDOS attacks, but it can also be used to rate-limit requests originating from the same IP address. We have used this feature so that we can test multiple failure scenarios for our application. 3. To prevent Data crawling: The BOT control feature allows us to prevent BOTs from crawling data on our websites. Not Suited: 1. To integrate applications outside of AWS Cloud: As I mentioned in my previous comments, this type of integration requires a custom implementation of another AWS resource.
Loadmaster is very powerful and flexible load balancer. Variety of options allows to create a complex network of rules and routes. During our website rollout Loadmaster allowed us to run multiple generations of the website simultaneously and seamlessly by doing the content switching on the fly. Powerful API allows easy integration into any development lifecycle.
Protect any application against the most common attacks.
Provides better visibility of web traffic.
It allows us to control the traffic in different ways in which it is enabled or blocked through the implementation of security rules developed personally according to our needs.
It is able to block common attacks such as SQL code injection.
It allows defining specific rules for applications, thus increasing web security as they are developed.
Where the LoadBalancer excels is the multiple levels at which you can load balance servers. We currently use layer 7 LB, but others are available as well.
I particularly like the ability for the LB to know when servers are down, and if all are offline then you can create a redirect to a static HTML page or some other destination that is more informative.
The ease in which a service can be created and deployed using already pre-canned templates makes it a very convenient setup process.
AWS WAF is a bit costly if used for single applications.
they should provide attack-wise protection, like if my certain type of application is vulnerable to DDOS then I should be able to buy WAF, especially for that attack.
We have been using AWS WAF for the past 3 years in front of our websites. We find it useful in preventing data crawling, DDOS attacks, etc on our websites, and hence we are going to use it in the future as well. AWS WAF is one of the best Firewalls in business.
The product is highly scalable. It is easy to configure the rules and thereby helps us to mitigate many vulnerabilities. The interface and programming of the firewall provisions were easy to setup. Amazon clearly spent a lot of time figuring this out and perfecting it. It allows users to do customized configurations based on their needs. It provides protection against a number of security issues like XSS, SQL injection, etc. I would definitely recommend this for protecting your infra as you scale, since this basically protects and filters all requests hitting your application server.
Kemp makes it very easy to setup, configure and manage the LoadMaster without needing a lot of help from their engineers. The interface is very easy to understand and intuitive to use. We like how it is not complicated - I can easily have one of my techs login and they can figure out how to setup/configure virtual services for load balancing without needing a manual or tech support.
If you're intending to use AWS WAF, I would say that you absolutely should sign up for support. AWS Support is excellent and they can help you in a really good way to solve your issues.
Support has been easy to deal with; I have only need[ed] to contact them a few times during setup. Once its been in place and operational, we have not need[ed] to mess with the system [which] is a huge advantage. I like system[s] that do not break and require constant attention in a production environment.
Easy of use. Setup and configuration is fairly quick. There are the usual advantages of it being a cloud solution where you can buy into the solution, configure it and set it up and get it up and running. If you are already a subscriber to AWS, having a native service has its advantages.
We chose Kemp LoadMaster because it is 1/10 the price of the competition and MUCH easier to deploy and configure and WORKS. We have had ZERO issues with the product since installation. Their engineers and their sales team have both reached out post-install to check in and see if everything is working as expected.
Implementing this AWS service has been really favorable because when creating custom rules we give more specific protection to our applications against vulnerabilities that cause them to be consuming other resources or running with errors.
It allows us to control the traffic of our business applications, which is really favorable, given that in this way we can decide that you can access them and not.
It is extremely advantageous that we can establish rules in a centralized way since it saves time, as well as it allows us to protect several applications at the same time by reusing the rules established above.
It allows you to save time and money because we only pay for what is used.
We used Kemp LoadMaster for many projects. For a lot of customers, load balancers were too expensive or too complicated before we introduced Kemp products.
It's not a overly complicated product, so we were able to train many engineers on it and have them get a certification.
