We performed a comparison between Amazon EKS and Komodor based on real PeerSpot user reviews.Find out in this report how the two Container Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"It's a faster solution to adopt on native applications."
"The tool works well with the nodes in AWS. It's scalability is also good in terms of architecture."
"It is a scalable solution."
"It has valuable monitoring and insights features."
"The product helps us to configure the new environment."
"I like the scalability they're currently providing. Integration was very easy. It was a good experience."
"I like its auto-scale feature very much."
"It's the best option for medium or large enterprises."
"The service overview is definitely the most valuable feature. With it, I can see all the services and see if they're healthy or not without having to go specifically into each workflow individually. It has been immensely helpful for us whenever we've had network issues or other such issues. We've been able to use Komodor and see at a glance where there might be potential issues."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"The event timeline has been super helpful, enabling us to overlay node events in the same timeline as deployment events... That helps an engineer very quickly troubleshoot without having to do too much digging."
"The most valuable aspect is the speed with which I can narrow down what's going on. Usually, I look at the overview of events and then the timeline of an event and the status of the logs to quickly check what's happening or what has happened."
"The product’s pricing needs improvement."
"The overall stability of the product should be improved to prevent any loss of data."
"I am not impressed with the tool's Amazon console. It also needs to add security features."
"The tool's setup is complex."
"The management of the nodes in Amazon EKS should be improved."
"The solution could be improved by adding monitoring, filtering, and logging capabilities to its current CloudWatch features."
"Amazon EKS provides very minimum information during the upgrade of the node group."
"I would like to see the user interface improved because it is hard to find and not straightforward."
"I hope that the cost analytics and resource usage allocation areas will see further development. For example, where we can now see if the pods are over- or under-provisioned, I wouldn't mind higher-level development."
"One thing we don't have visibility into, which I would love to have, is metrics, such as user logins and usage. It's really hard to know what people are doing when I don't have any metrics on that directly."
"I would like to see improvements in how the product is installed. We've already communicated these things directly to Komodor. One feature we would like to see is for Komodor to be highly available on the clusters. Currently, it's only able to run in one instance within the cluster."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"Komodor's visibility could be improved."
Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.
EKS is the best place to run Kubernetes for several reasons. First, you can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design. Second, EKS is deeply integrated with services such as Amazon CloudWatch, Auto Scaling Groups, AWS Identity and Access Management (IAM), and Amazon Virtual Private Cloud (VPC), providing you a seamless experience to monitor, scale, and load-balance your applications. Third, EKS integrates with AWS App Mesh and provides a Kubernetes native experience to consume service mesh features and bring rich observability, traffic controls and security features to applications. Additionally, EKS provides a scalable and highly-available control plane that runs across multiple availability zones to eliminate a single point of failure.
EKS runs upstream Kubernetes and is certified Kubernetes conformant so you can leverage all benefits of open source tooling from the community. You can also easily migrate any standard Kubernetes application to EKS without needing to refactor your code.
Komodor is the missing piece in your DevOps toolchain - offering one unified platform from which you can gain a deep understanding of all of your system events and changes. We integrate with all of your tools, monitor changes and alerts and organize information on a clear digestible dashboard and provide you with the right context at the right time.
Amazon EKS is ranked 3rd in Container Management with 30 reviews while Komodor is ranked 11th in Container Management with 5 reviews. Amazon EKS is rated 8.4, while Komodor is rated 8.8. The top reviewer of Amazon EKS writes "An intelligent solution that automatically upscales or downscales to set thresholds". On the other hand, the top reviewer of Komodor writes "Provides extensive visibility into our nodes and has been incredibly useful in freeing up our DevOps staff for other projects". Amazon EKS is most compared with OpenShift Container Platform, VMware Tanzu Mission Control, Kubernetes and Rancher Labs, whereas Komodor is most compared with Kubernetes and Portainer. See our Amazon EKS vs. Komodor report.
See our list of best Container Management vendors.
We monitor all Container 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.