Try our new research platform with insights from 80,000+ expert users

Amazon EKS vs Komodor comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 13, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon EKS
Ranking in Container Management
2nd
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
53
Ranking in other categories
Container Security (19th)
Komodor
Ranking in Container Management
13th
Average Rating
8.8
Reviews Sentiment
9.0
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Container Management category, the mindshare of Amazon EKS is 11.8%, down from 13.8% compared to the previous year. The mindshare of Komodor is 4.3%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Rock Wang - PeerSpot reviewer
Managing complex environments effortlessly while focusing on growth
The most beneficial aspect of Amazon EKS is that it helps manage the Kubernetes master node, so I don't need to maintain the master node, including tasks like upgrading. This allows me to focus on business code. If using services like Fargate, I only need to maintain my workload, simply uploading code that will be deployed to the Kubernetes cluster. This is especially beneficial for startup companies that lack the technical resources to manage the Kubernetes cluster. Furthermore, Amazon EKS allows me to utilize Kubernetes cluster-level expansion. If there’s insufficient resource on a machine, the cluster can automatically expand to add new nodes.
Jacek Kisynski - PeerSpot reviewer
Makes it easier for our development team to "own" Kubernetes, saving our SRE team time
There's nothing in particular that is wrong with Komodor. It's hard to say that there's something we would really like to see improved. 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. I would like to see if we're utilizing nodes in the cluster, if pod allocation is optimal, how much idling we have, and whether we scale up and down efficiently. I would like to see them help us optimize costs further. Because, as our company grows and our clusters get busier and busier, any inefficiency is a lot of money wasted. That's definitely high on our wish list: anything that helps us track wasted resources. I am looking forward to using AI-powered troubleshooting workflow that Komodor unrolled recently.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's the best option for medium or large enterprises."
"AWS EKS provides flexibility and scalability compared to on-premises Kubernetes."
"EKS has security features that you can't find in competing solutions."
"Amazon EKS is very scalable."
"We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon."
"Through Amazon EKS, we can have the blue-green deployment very easily."
"The most valuable feature is the cluster engine."
"The most valuable features of Amazon EKS are its scalability features."
"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 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."
"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"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."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
 

Cons

"I would like to see it a little more stable, more operational, and more convenient to develop."
"The documentation part of the product is an area of concern that needs to be made easier from an improvement perspective."
"There is room for improvement in making Amazon EKS less error-prone when writing on the YAML file."
"The solution should include a popup for clusters so that all relevant information is visible at the bottom of a page."
"Amazon EKS should improve its integration."
"Sometimes, we face minor connectivity issues."
"The initial setup for Amazon EKS is not straightforward. Kubernetes is not an easy technology because there are many technologies in the cluster."
"There is room for improvement in the interface of Amazon EKS."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"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."
"Komodor's visibility could be improved."
"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 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."
 

Pricing and Cost Advice

"The solution is quite costly and developers will start exploring other solutions or moving their workloads to other clouds if costs aren't reduced."
"Pricing is dependent upon instance type."
"Amazon EKS is not a cheap solution."
"I would like a cheaper version of it."
"I rate Amazon EKS’s pricing a nine out of ten."
"The price can be a problem for small-sized businesses."
"Amazon EKS’s pricing is ok compared to its competitors."
"Amazon EKS is very cost-effective."
"We pay according to the number of resources we have; if we are a small start-up, we have fewer resources and thus pay less."
"As far as I can recall, the licensing cost was fair."
"The licensing model is fine. It is per node, which is good, but the pricing is high. Currently, I am fine with it, but I am a little concerned about the pricing as we scale. So, it is on the higher end. On a scale of one to ten, where ten is the most expensive, Komodor is a seven."
"Other options pop up, but Komodor's pricing works well for our use case. It's fair, and we appreciate it. A lot of other vendors price their solutions in a way that would cost us disproportionately more money than they should. Komodor's pricing is reasonable in the way they calculate usage and value."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
859,687 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
11%
Manufacturing Company
7%
Insurance Company
7%
Computer Software Company
18%
Wellness & Fitness Company
11%
Comms Service Provider
10%
Media Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Amazon EKS?
The product's most valuable features are scalability, observability, and performance.
What is your experience regarding pricing and costs for Amazon EKS?
We are making a significant effort to transform our usage of Amazon EKS, which was previously rated as eight or nine in terms of cost. Now, it stands at six or seven due to optimizing our workload.
What needs improvement with Amazon EKS?
I am not the right person to ask what could be improved in Amazon EKS to make this tool better for the next release. A continuation of the managed pieces would be beneficial because there is no int...
What do you like most about Komodor?
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...
What needs improvement with Komodor?
There's nothing in particular that is wrong with Komodor. It's hard to say that there's something we would really like to see improved. I hope that the cost analytics and resource usage allocation ...
What is your primary use case for Komodor?
We are an HR analytics company, and we do a lot of data processing. Our customers send us their HR-related data, and we process it so that we can run analytics on it. We process it on Kubernetes cl...
 

Also Known As

Amazon Elastic Kubernetes Service
No data available
 

Overview

 

Sample Customers

GoDaddy, Pearson, FICO, Intuit, Verizon, Honeywell, Logicworks, RetailMeNot, LogMeIn, Conde Nast, mercari, Trainline, Axway
Information Not Available
Find out what your peers are saying about Amazon EKS vs. Komodor and other solutions. Updated: June 2025.
859,687 professionals have used our research since 2012.