We performed a comparison between Amazon CloudWatch and Wazuh based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Amazon CloudWatch users liked the solution’s simplicity, intuitive interface, and ability to handle large workloads. Users also praised CloudWatch’s comprehensive monitoring and alerts. Wazuh stands out for its effortless integration, excellent log monitoring capabilities, and ELK-based investigation. Some reviews mentioned that Amazon CloudWatch could improve performance and dashboard visualization through. Others noted that the solution lacked compatibility with some databases. Wazuh needs improvements in event source coverage, threat intelligence integration, and real-time monitoring of Unix systems.
Service and Support: Customers generally have positive opinions about Amazon's customer service. They commended the support team for its availability and timely issue resolution. Wazuh's customer service is generally deemed satisfactory, and many customers noted that they could easily find answers from community forums.
Ease of Deployment: Amazon CloudWatch is generally described as easy to set up. Some users said that Wazuh’s setup is easy and fast, while others perceived it as complicated and said it required a significant amount of time.
Pricing: Amazon CloudWatch offers a flexible pricing structure based on usage and processing without any separate licensing cost. Some users said that scaling up can be costly due to the need for additional storage space. Wazuh is a cost-effective option as it is open-source and completely free to acquire.
ROI: Amazon CloudWatch offers a return on investment by minimizing the need for manual monitoring. Wazuh's MSP program and partnerships offer opportunities to generate revenue from the platform.
"The most valuable feature of Amazon CloudWatch is its ease of use and logs. You do not have to go to each separate system to see the logs, such as Syslog and they are located in one dashboard GUI."
"What I found most valuable in Amazon CloudWatch is that it gives you detailed information, which I found helpful because it can even provide you with data for the past one minute, which is quite granular. That was what helped me most in terms of finding the root causes. Task automation is another valuable feature of Amazon CloudWatch."
"The product helps us collect and store various metrics to set test alarms."
"You can enable alarms and metrics, and it has robust integration with AWS services. You can also trigger events. For example, if the CPU utilization is above 80%, it can launch a new instance for you."
"It's a very simple logging system."
"Setting up this product was easy. I found data analytics as its most valuable feature."
"The initial setup is easy."
"Every time we get an alarm or have an incident, CloudWatch is always there. We use it not only for resources we've spun up in the cloud, but also for some of our on-premises resources."
"It offers built-in modules for file integrity and vulnerability management."
"Wazuh automatically scans the host for CIS benchmarks for the latest updates and vulnerabilities and gives a host score. It provides a percentage of perceived risk due to of non patches or any missing patches on that work."
"I like that the solution is on top of the Kubernetes stack."
"Wazuh is simple to use for PCI compliance."
"Wazuh's logging features integrate seamlessly with AWS cloud-native services. There are also Wazuh agent configurations for different use cases, like vulnerability scanning, host-based intrusion detection, and file integrity monitoring."
"The most valuable feature of Wazuh is the ELK for doing an investigation."
"The configuration assessment and Pile integrity monitoring features are decent."
"Wazuh offers numerous features, such as the ability to define custom rules for detecting malicious activities and remembering behaviors."
"Better reporting is always something needed. That could be an answer to just about anything. But you always want better reporting, better dashboards, things that are just more dynamic and more accessible."
"Improvement of SSSD logs would be beneficial."
"I found several areas for improvement in Amazon CloudWatch. First is that it's tough to track issues and find out where it's going wrong. The process takes longer. For example, if I get an exception error, I read the logs, search, go to AWS Cloud, then to the groups to find the keyword to determine what's wrong. Another area for improvement in Amazon CloudWatch is that it's slow in terms of log streaming. It requires an entire twenty-four hours for scanning, rather than just one hour. This issue can be solved with Elasticsearch streaming with Kibana, but it requires a lot of development effort and integration with Kibana or Splunk, and this also means I need a separate developer and software technical stack to do the indexing and streaming to Kibana. It's a manual effort that you need to do properly, so log streaming should be improved in Amazon CloudWatch. The AWS support person should also have a better understanding of the logs in Amazon CloudWatch. What I'd like added to the solution is a more advanced search function, particularly one that can tell you more information or special information. Right now, the search function is difficult to use because it only gives you limited data. For example, I got an error message saying that the policy wasn't created. I only know the amount the customer paid for the policy, the mobile number, and the customer name, but if I use those details, the information won't show up on the logs. I need to enter more details, so that's the type of fuzzy matching Amazon CloudWatch won't provide. If this type of search functionality is provided, it will be very helpful for businesses and companies that provide professional services to customers, like ours."
"There is room for improvement in the pricing, because they have a premium version, but it's not really a premium version. It's just an enhanced monitoring version, and it can be a bit expensive depending on your usage."
"I do not know whether or not CloudWatch can be integrated with on-prem services."
"CloudWatch doesn’t monitor disk throughput by default."
"I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing."
"The product should provide more features."
"The tool does not provide CTI to monitor darknet."
"One area where Wazuh could use some improvement is in its reporting mechanism, especially for high-level management like CSOs and CEOs."
"A lack of certain features creates limitations."
"Wazuh is missing many things that a typical SIEM should have."
"The computing resources are consuming and do not make sense."
"They need to go towards integrating with more cloud applications and not just OS like Windows and Linux."
"Its configuration process is time-consuming."
"The implementation is very complex."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Wazuh is ranked 3rd in Log Management with 38 reviews. Amazon CloudWatch is rated 8.0, while Wazuh is rated 7.4. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of Wazuh writes "It integrates seamlessly with AWS cloud-native services". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and IBM SevOne Network Performance Management (NPM), whereas Wazuh is most compared with Elastic Security, Security Onion, Splunk Enterprise Security, AlienVault OSSIM and Graylog. See our Amazon CloudWatch vs. Wazuh report.
See our list of best Log Management vendors.
We monitor all Log Management 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.
