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."
"The solution's ease of use is the most valuable feature."
"The product has a good mechanism to analyze trends and trigger events."
"It is integrated with AWS. So, it gives you a good first step."
"I am impressed with the product's multiple features like security."
"The DDoS protection is the most valuable aspect of the solution."
"Cloudflare is a security SaaS provider that provides security and protects us from any application layer attack."
"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."
"We're using dynamic components to build flexible pages to create and manage Git merge requests for code and reviews."
"The most valuable feature is the web application firewall."
"Centralized, full-featured DNS."
"There are key things that are used for our enterprise customers, such as Lambda and DNS."
"Smaller businesses have seen great ROI due to the low investment and strong performance."
"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."
"We end up having to pay extra for features that AWS adds that we don't need."
"The product needs to improve its logs and reports to make it read better."
"The product is expensive."
"For the free and Pro plans, Cloudflare could use a simple bot to provide information to users. This would improve support, especially for less advanced users who utilize the free components."
"One area of improvement is in the Access Rules. Hypothetically, if we wanted to block or challenge traffic outside of the United States, the only way to currently do that (as far as I know) is to enter every single country outside of the United States. That could be a labor intensive job. A solution could be to enable users to create a rule where traffic is only allowed within a certain country."
"The product support needs to be accessible from more places, a wider area of coverage."
"Cloudflare's console should be made more user-friendly."
"It should confirm audit findings of the assigned area with auditees to ensure that the audit conclusions are based on an accurate understanding of the issues."
"We're facing challenges due to an upgrade in the machine learning model. The problem arises from some users abusing the APIs, resulting in an influx of suspicious traffic. Cloudflare's learning model mistakenly identifies this traffic as human. Consequently, it assigns it a higher trust score, akin to legitimate human traffic, causing complications in our architecture. Previously, such traffic would have been categorized as suspicious, enabling us to apply appropriate blocking rules. However, we encounter difficulties distinguishing between genuine and suspicious traffic with the new categorization. Despite these challenges, overall, Cloudflare remains the preferred solution compared to Azure, AWS CloudFront, and Google Cloud Armor."
"The pricing could be improved."
"The product needs to improve its automation."
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.