Likelihood to Recommend
Most suited if you have a very strong presence in AWS. It is natively available as an add on service. You can also track the costs overtime based on usage. There is still a lot of improvement on the features and the user interface that can be implemented over time
Read full review
Azure CDN has at hand an infinity of applications and tools to implement in your system and have better control of your data in a clean and secure platform on the web, we recommend this program since the percentage of solutions provided by this program is very high and find a way to make each user's job easier.
Read full review Pros 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. Read full review I found the CDN very easy to setup and configure within the Azure Portal. Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm. Read full review Cons 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. CLI tool to test in offline mode if possible. Read full review Tough learning curve--you have to be comfortable with the Azure Cloud logic and UI to use it easily Special or uncommon use cases' pricing can be hard to forecast/follow Can be expensive for simple use cases Read full review Usability
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.
Read full review Support Rating
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.
Read full review
Great support from the team whenever we're stuck. Very proactive in resolving issues and also making changes as per the requirements of the organization.
Read full review Alternatives Considered
Unlike these other AWS tools, WAF provides real-time traffic control, rules that can be customized according to the needs of the user, and is based on an implementation in the cloud which avoids the use of memory on computers as well as an account with a very affordable cost for any user or company
Read full review
More user friendly and it’s so easy to learn, the prices may be close to each other, but the service is excellent.
Read full review Return on Investment The overall security of the web application increased effectively after deploying AWS WAF No negative impacts were seen in the business The developers were more confident in the overall security model of the web application being developed and it was easy to integrate WAF into the existing system as the application was also using AWS platform Read full review Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances. Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers. Read full review ScreenShots