We performed a comparison between AWS Shield and Cloudflare based on real PeerSpot user reviews.
Find out in this report how the two Distributed Denial of Service (DDOS) Protection solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We have integrated the tool with Active Directory. The most important feature is that it's transparent and doesn't degrade the performance of our solution. Additionally, it's easy to configure, which is crucial for us. It's easy to use and set up and stops attacks on our servers. We haven't encountered any attack problems because the solution stops them in real-time. AWS Shield specifically focuses on defending against denial-of-service attacks, making it a great solution for that type of threat."
"It is integrated with AWS. So, it gives you a good first step."
"The product has a good mechanism to analyze trends and trigger events."
"The solution's ease of use is the most valuable feature."
"I am impressed with the product's multiple features like security."
"DDoS attacks target unprotected machines. Cloudflare detects and stops these attacks using internal systems. It identifies incoming DDoS attacks, issuing challenges or blocking them immediately."
"When using services like Heroku, Cloudflare is very useful for CNAME flattening. I also use it for their end-to-end SSL with TLS authentication on nginx for securing servers."
"It is easier to configure and develop documentation to see how we have configured firewalls."
"The simplicity of the overall dashboard makes it a great product for a user like me who has less understanding of the internet than a developer or other more technical people. It gives me peace of mind. I also love the easy customization of the Page Rules."
"The most valuable feature of Cloudflare is the GUI. You are able to control the solution very well through the interface. There is a lot of functionality that is embedded in the service."
"The solution offers the flexibility to control configuration rules."
"Easier http to https redirect using page rules"
"The web application firewall brought us good security and a view of the accesses/blocks of the entire domain and subdomain that were accessed both by region (country) and IPs."
"The product needs to improve its logs and reports to make it read better."
"The product is expensive."
"We end up having to pay extra for features that AWS adds that we don't need."
"The management of it is a bit hard. If you don't engineer it on the front side, it is hard to go back in and change it. It could be improved in terms of architecture requirements and then ongoing support requirements as a secondary component to it. People tend to set up things like this, and they just expect it to work without the care and feeding that needs to go back into it either from an application team or a network environment team."
"The product should give users more flexibility to customize their security policies according to their requirements."
"It would be beneficial for us if Cloudflare could offer a scrubbing solution. This would involve taking a snapshot of my website and keeping it live during a DDoS attack, ensuring uninterrupted service for our users. DDoS attacks are typically short in duration, and having Cloudflare maintain the site's availability from its secure network would enhance the overall user experience. I would appreciate it if Cloudflare could consider implementing this feature. Many organizations already utilize similar capabilities in their CDN platforms, where a static snapshot of the web page is displayed during DDoS attacks. In terms of features, Cloudflare needs to enhance its resilience and stay more focused on adopting new technologies. For instance, solutions like F5 XC Box, Access Solution, and Distributed Cloud Solution have impressive features, and Cloudflare should strive to match and exceed those capabilities. There's a need for improvement in areas like AI-based DDoS attacks and Layer 7 WAF features. Cloudflare should prioritize enhancements in areas such as behavioral DDoS and protection against SQL injection attacks, considering the prevalent trend of public exposure to the internet for business reasons. Overall, Cloudflare needs to invest more in advancing its feature set."
"Cloudflare's console should be made more user-friendly."
"Even if I wanted to, I wouldn't be able to buy Cloudflare in my country."
"If they improve on the placement of their data centers, it would be better. I'm living in a remote area. I would like to connect to them without any kind of lag."
"The product support needs to be accessible from more places, a wider area of coverage."
"The reporting can definitely be improved to offer a lot more explanation on something that may have happened or has actually happened."
"The product needs to improve its automation."
"The solution could work at being less expensive. It costs a lot to use it."
AWS Shield is ranked 6th in Distributed Denial of Service (DDOS) Protection with 5 reviews while Cloudflare is ranked 1st in Distributed Denial of Service (DDOS) Protection with 57 reviews. AWS Shield is rated 8.6, while Cloudflare is rated 8.4. The top reviewer of AWS Shield writes "The solution automatically scales according to traffic, only takes minutes to deploy, and is maintenance-free". On the other hand, the top reviewer of Cloudflare writes "It's easy to set up because you point the DNS to it, and it's working in under 15 minutes". AWS Shield is most compared with Cloudflare DDoS, Azure DDoS Protection, Akamai App and API Protector, Prolexic and Imperva DDoS, whereas Cloudflare is most compared with Akamai, Azure Front Door, Imperva DDoS, Microsoft Azure Application Gateway and Arbor DDoS. See our AWS Shield vs. Cloudflare report.
See our list of best Distributed Denial of Service (DDOS) Protection vendors.
We monitor all Distributed Denial of Service (DDOS) Protection reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.