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

Amazon EKS vs Red Hat OpenShift Container Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 12, 2025

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.2
Number of Reviews
48
Ranking in other categories
Container Security (13th)
Red Hat OpenShift Container...
Ranking in Container Management
1st
Average Rating
8.4
Reviews Sentiment
7.3
Number of Reviews
49
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Container Management category, the mindshare of Amazon EKS is 13.8%, up from 13.5% compared to the previous year. The mindshare of Red Hat OpenShift Container Platform is 22.6%, up from 20.5% 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.
Vlado Velkovski - PeerSpot reviewer
Provides automation that speeds up our process by 30% and helps us achieve zero downtime
OpenShift has a pretty steep learning curve. It's not an easy tool to use. It's not only OpenShift but Kubernetes itself. The good thing is that Red Hat provides specific targeted training. There are five or six pieces of training where you can get certifications. The licenses for OpenShift are pretty expensive, so they could be cheaper because the competition isn't sleeping, and Red Hat must take that into account. There are a few versions of OpenShift. There is the normal OpenShift and an OpenShift Plus license. Red Hat could think of how to connect those two subscriptions because, with Red Hat Plus, you have one tool called ACM (Advanced Cluster Management), where you can manage multiple clusters from one place. We deployed this functionality by ourselves, but if you don't pay the license for Red Hat OpenShift Plus, you'll lack this functionality. If you have a multi-cloud environment and you have a lot of work to do, it would be a plus if the Red Had OpenShift Plus license came in a bundle with the regular solutions. This ACM tool should be available in the normal subscription, not just the Plus version. There are new versions on an almost weekly basis. I found myself that the upgrading of OpenShift clusters is not a task that will successfully finish every time. It's a simple and quick, but not reliable process. That's why we use multiple clusters. We use v4.10.3, but we want to move to v4.12.X. The upgrade process itself can fail, and we don't have backups of our OpenShift cluster because we have backups of all the Kubernetes manifests on GitHub. We destroy the cluster, bring up a new one quickly, and apply those scripts. The upgrade itself could be more resilient for us as administrators of OpenShift to be sure that it'll succeed and not occasionally fail. They can improve the reliability of their upgrade process. They also have implementations of some Red Hat-verified operators for a lot of products like Elasticsearch. They're good enough for development purposes, but some of the OpenShift operators still lack resilient production-grade configurations. Red Hat says that we have a few hundred operators, but I believe that only half of them are production-grade ready at this moment. They need to work much more on those operators to become more flexible because you can deploy all of them in development mode, but when we go to production grade and want to make specific changes to the operator and configuration, we lack those possibilities.

Quotes from Members

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

Pros

"The solution has very good basic features."
"The stability of the solution is good."
"I can use the autoscaling feature to manage and scale up infrastructure."
"It's the best option for medium or large enterprises."
"We haven't faced any major issues in one and a half years of use."
"EKS provides autoscaling functionality."
"I like the scalability they're currently providing. Integration was very easy. It was a good experience."
"Amazon EKS provides good support."
"The tool's most valuable features include high availability, scalability, and security. Other features like advanced cluster management, advanced cluster security, and Red Hat Quay make it powerful for businesses. It also comes with features like OpenShift Virtualization."
"It is easy to expand."
"I think it's a pretty scalable tool...The solution's technical support has been pretty good."
"Some of the primary features we leverage in the platform have to do with how we manage the cluster configurations, the properties, and the auto-scalability. These are the features that definitely provide value in terms of reducing overhead for the developers."
"Technical support is good; they are fast and reliable."
"I like the Flexibility of the solution."
"It automates rolling out new features, packaging the code, conducting security scans, and deploying to OpenShift."
"The solution is stable. However, it depends on the integrations of the solution on how stable it will be, such as what tools you integrate with."
 

Cons

"I'd like to see the solution add a service catalog."
"Sometimes, we face minor connectivity issues."
"Improvement is needed in reducing the complexity of using EKS."
"The solution could be improved by adding monitoring, filtering, and logging capabilities to its current CloudWatch features."
"The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high."
"I would like to see it a little more stable, more operational, and more convenient to develop."
"Amazon EKS could improve in its pricing model, particularly for medium-sized customers who might find the support costs high."
"I encountered problems with the product’s documentation."
"The initial setup can be hard."
"One area for product improvement is the support limitations within the subscription models, particularly the restricted support hours for lower-tier subscriptions."
"The product could benefit from additional operators and tools integrated with OpenShift."
"In my experience, the issues are not always simply technical. They do stem from technical challenges, but they struggle with the topic of adoption. When you encounter all of the customer pull, there are normally several tiers of your client pop that can adopt either the fundamental features or a little more advanced ones. The majority of the time, the challenge is determining how to drive adoption, how to sell the product to the customer, and how much time they can spend to really utilize those advanced features. If we get into much more detail, but this is from my perspective as the platform engineer and not the end customer, the ability of the end user to be able to debug potential issues with their application That is arguably the most important, let's say, work throughput in my area."
"There should be a simplification of the overall cluster environment. It should require fewer resources. Just to run a simple Hello World app, it requires about seven servers, and that's just crazy. I understand that it is fully redundant, but it's prohibitively expensive to get something simple going."
"Setting up OpenShift isn't easy. I rate it three out of ten for ease of setup. We're deploying it in three phases. They're in the second phase now. The total deployment time will be five months. We expect to complete the deployment this March. There are 13 people on three teams working on this deployment."
"The stability needs improvement."
"It can take 10 to 15 minutes to deploy a microservice. The CI/CD process takes a long time, and if it's because of OCP, that is something that can be changed."
 

Pricing and Cost Advice

"Pricing is dependent upon instance type."
"The solution is pricey. The tool's pricing is monthly."
"Amazon EKS has fair pricing. It's better in terms of pricing than other platforms."
"The product is available at such a huge scale in the market since the resources that are offered under the tool are competitively priced and available at a much cheaper rate compared to other solutions."
"Amazon EKS is expensive."
"The price could be cheaper. I would rate it as seven out of ten."
"I would like a cheaper version of it."
"The solution is more expensive than other competitors and does not require a license."
"The product is expensive."
"We have to pay for the license."
"Its price is a bit high because it's a premium product, but as long as the business is ready to pay for that, it's okay."
"The product pricing is competitive and structured around vCPU subscriptions, aligning with our application requirements."
"We currently have an annual license renewal."
"It depends on who you're talking to. For a large corporation, it is acceptable, other than the significant infrastructure requirements. For a small organization, it is in no way suitable, and we'd go for Amazon's container solution."
"The pricing and licensing are handled on an upper management level, and I'm not involved in that, but I understand the solution to be somewhat pricey."
"I'm not familiar with pricing or financial aspects. In terms of effort versus benefit, it's worth it."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
847,625 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
13%
Manufacturing Company
7%
Insurance Company
6%
Financial Services Firm
22%
Computer Software Company
13%
Government
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups. Offering a free version could help small companies.
What needs improvement with Amazon EKS?
There is room for improvement in making Amazon EKS ( /products/amazon-eks-reviews ) less error-prone when writing on the YAML file. A UI could help generate config files, simplifying the process fo...
Which is better - OpenShift Container Platform or VMware Tanzu Mission Control?
Red Hat Openshift is ideal for organizations using microservices and cloud environments. I like that the platform is auto-scalable, which saves overhead time for developers. I think Openshift can b...
What do you like most about OpenShift Container Platform?
The tool's most valuable features include high availability, scalability, and security. Other features like advanced cluster management, advanced cluster security, and Red Hat Quay make it powerful...
What is your experience regarding pricing and costs for OpenShift Container Platform?
OpenShift pricing varies by region. For example, a simple cluster with three nodes in DAL-10 might cost around $560 to $580 per month, subject to specific configurations like memory and CPU cores.
 

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
Edenor, BMW, Ford, Argentine Ministry of Health
Find out what your peers are saying about Amazon EKS vs. Red Hat OpenShift Container Platform and other solutions. Updated: March 2025.
847,625 professionals have used our research since 2012.