AWS Shield vs Cloudflare DDoS comparison

"I am impressed with the product's multiple features like security."

"It is integrated with AWS. So, it gives you a good first step."

"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 a stable solution."

"The blocking feature is very good."

"The best feature is rate limiting. If I'm expecting 500 visits per hour, Cloudflare will limit the requests if I suddenly get 50,000."

"Cloudflare is by far the most effective solution that I have come across."

"Cloudflare is simple to use."

"The solution has different options that can be used to differentiate DDoS attacks."

"This solution is easy to understand and easy to configure."

"Cloudflare DDoS mitigates DDoS attacks."

"The product needs to improve its logs and reports to make it read better."

"The product should give users more flexibility to customize their security policies according to their requirements."

"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 is expensive."

"We end up having to pay extra for features that AWS adds that we don't need."

"The software has automated alerts, but the automated alerts are not available in the mobile app."

"The onboarding process can be improved a little bit."

"The tool should provide on-premise versions. Currently, all versions are cloud-based."

"Our customers no longer use Cloudflare because its service is subpar."

"The initial onboarding was causing us some confusion."

"Our subscription plan for the solution has a limitation of bot signatures."

"Cloudflare DDoS has poor technical support."

"The response time for support must be reduced."

"The cost depends on traffic each month, so on average, it costs us between US$200 and US$300 per month."

"The tool's pricing is good."

"We pay $3000 per month for the solution."

"It depends on your subscription level and the volume that you're spending with AWS. So, it is very relative to the consumption alignment in your subscription level. It is a well-constructed, scalable pricing option, but it is relative to how much you're spending on AWS. Because the more you spend, typically, the more you get off on services like this. I find it to be comparable to other solutions."

"The solution is not that expensive."

"The price tag is no longer $200,000, but rather $300,000 to $400,000. It's twice."

"The pricing of the solution is cheap. The licensing cost is also very low. I rate the cost and pricing a three out of ten."

"The solution's pricing lacks transparency."