Have you ever heard about WAF before? You may but no, it’s not web application FRAMEWORK I’m going to talk about today. It’s web application FIREWALL. You may have a time when you struggle to deal with many accesses from scrapers or attackers to your web application. These requests look normal but a loaf of requests that keeps coming can behave like DoS attack. It can degrade the performance of your application and moreover, it can worsen user experience too. Actually, we had this sort of challenge to provide a web application Buffett Code which provides valuable information for investment and corporate analysis. Due to the nature of the application providing numbers of investment information, the web application can receive many requests from bots or some machinery programs. We looked for several solutions to protect the application from this kind of scraping behavior. AWS WAF may be a solution easily integrated into your application running in AWS resource.
AWS WAF is a web application firewall to protect your application against scaping or DoS attacks. It can be easily integrated with your application running on AWS. WAF is provided with CloudFront (global) of regional application load balancers.
You can configure WAF based on the following characteristics of the traffic.
The benefit of using WAF is it can automatically detect the characteristics like SQL injection or cross-site scripting because it is troublesome if we need to protect our application against that sort of attacks manually. Let’s see how we can set the blacklist of a user agent which should be blocked.
You can put any user agent header to be blocked by using this feature. AWS WAF provides various kind of utilities to get things done easier.
Transformation enables us to preprocess the header of an incoming request before applying the matching condition.
By using the transformation of
Convert to lowercase, we can simply put blocking user agent in the lower case without caring about the case sensitivity. Of course, you can configure not only HTTP header but also query string, HTTP method, URI.
Another good thing of AWS WAF is dashboard to see how many requests are blocked at a glance.
As AWS WAF automatically keeps logs of blocked request including IP, header and query string so that we can check the configuration of WAF is effective or not. It’s also helpful to detect the time when the abusive request tends to come to our application. We may be able to do auto scaling not to degrade the performance of the application around the time.
So overall we can get a huge benefit by using AWS WAF. Since our application is running behind the application load balancer, it was so easy to integrate with our application. The easiness and flexibility of AWS WAF let us focus on developing the core value of our application.
Unfortunately there is not so many resources to learn AWS WAF technical details. As it is often the case, the official documentation (AWS WAF, AWS Firewall Manager, and AWS Shield Advanced: Developer Guide) is the best one to get started this beneficial framework. It’s free!
Thanks!Written on April 27th, 2019 by Kai Sasaki