AWS WAF vs. Azure Application Gateway

AWS WAF is highly appropriate to interrupt or prevent cyber attacks because when implementing rules, whether they are specific or centralized, so any application that has these vulnerabilities is protected.

Implementing managed rules creates greater security to protect both API and applications. If implemented along with other AWS tools, the security is much better, so if you want to protect applications against more specific attacks, it is ideal to integrate with Amazon CloudFront, which is a great benefit because it warns when thresholds are exceeded or specific attacks occur. AWS WAF is ideal to avoid common web attacks. For more specific attacks and scenarios, I don't recommend this.

Incentivized

The best practice for a cloud environment is to use the tools provided by the cloud provider. That's why for Azure cloud, Azure Application Gateway is the most cost-effective solution that you can use. You can use a single Azure Application Gateway instance for load balancing WAF, URL-based routing, and more.

Incentivized

• AWS WAF has the most developer-friendly API to create firewall rules.
• AWS WAF provides OWASP security controls, which reduces developers' burden (i.e., SQL injection and cross-site scripting).
• AWS WAF has customizable web security rules. The user can even push the rules through the API available, which is the great feature and helped me a lot.
• It protects applications at layer 7 (HTTP) of the OSI model and not just layer 4 (TCP).

Incentivized

• Uploading images by multiple end-users from several applications like web, mobile, etc.
• When there is a high volume of data requests, it helps to queue them based on the type of request. So it's easy to serve and reduce the loading time from the application layer.
• An application gateway is useful when it can identify the type of details the user is requesting.

Incentivized

• The documentation offered is somewhat confusing, so it would be ideal if it were much more direct and precise.
• Your initial configuration may be confusing, so the best option is to use the rule templates provided by AWS.
• Its configuration is not unified with AWS, so it must be done separately and it takes some time.
• The number of rules to be established is somewhat limited.

Incentivized

• More cost-effective pricing plans are welcome for the future, especially for WAF
• Ability to automate the TLS certificate renewal procedure
• Ability to manage non-HTTP traffic

Incentivized

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.

Incentivized

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.

Incentivized

Most of the Application Gateway's features and services can be managed and re-configured via either the Azure Portal GUI or via the Azure Cloud Shell, thus allowing both CLI modes, i.e. Azure CLI (Bash) and Azure Powershell. The v2 version of Application Gateway has significantly improved performance during initial configuration or during re-configuration changes, thus making it much more usable for IT admins, as compared to v1.

Incentivized

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.

Incentivized

I don’t like that it's part of the Microsoft brand. In general, I am not a fan of Microsoft products but Azure gets it right.

Incentivized

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.

Incentivized

HAProxy is an excellent load balancer that can also be used in cloud environments (and we do!), and is relied by hyper-large enterprises globally as well. However, HAProxy is a little bit more rudimentary in feature space, it does the core job well and securely, but doesn't provide any fancy additional features. Also, it takes more effort to deploy HAProxy than simply using an in-built feature in the Azure stack.

Incentivized

• Somewhat costly if specific needs are not there.
• If security is concerned than comparatively is beneficial.
• All those price that spent on AWS WAF in return gets saved in man hours.

Incentivized

• We are using Azure Application Gateway as the load balancing tool for our applications deployed on Azure Kubernetes Services (AKS) clusters.

Incentivized