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

Amazon EKS vs Red Hat OpenShift comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

ROI

Sentiment score
7.7
Amazon EKS enhances ROI with improved security, efficient scaling, cost savings, and optimized resource use through advanced tools.
Sentiment score
7.8
Red Hat OpenShift improves productivity, offers cost savings, enhances system stability, and provides 15% ROI, especially in privacy-focused sectors.
We have cost explorer available, and a bill forecast based on usage allows us to determine whether resources are underutilized or overutilized.
With OpenShift combined with IBM Cloud App integration, I can spin an integration server in a second as compared to traditional methods, which could take days or weeks.
Moving to OpenShift resulted in increased system stability and reduced downtime, which contributed to operational efficiency.
It is always advisable to get the bare minimum that you need, and then add more when necessary.
 

Customer Service

Sentiment score
7.2
Amazon EKS support is praised for responsiveness and effectiveness, though some users experience delays and suggest documentation improvements.
Sentiment score
6.8
Red Hat OpenShift support is mixed, praised for expertise but criticized for slow responses and varying experiences based on subscription.
We have a paid subscription that provides priority support.
Amazon's technical support is quite good, especially for those who purchase support services.
Having to know what questions to ask is essential.
Red Hat's technical support is responsive and effective.
I have been pretty happy in the past with getting support from Red Hat.
Red Hat's technical support is good, and I would rate it a nine out of ten.
 

Scalability Issues

Sentiment score
8.2
Amazon EKS is highly rated for scalability, effectively serving organizations of all sizes with impressive automatic resource adjustments.
Sentiment score
7.5
Red Hat OpenShift offers efficient scalability with automated features, easy deployment, and adaptability, despite cost and infrastructure considerations.
The ability to scale based on requirements by deploying additional containers is a strong point for Kubernetes.
This allows us to scale our applications or APIs as needed, offering reliability through the automation of scaling processes.
It can scale very well according to needs, and it doesn't have any issues with scalability.
The on-demand provisioning of pods and auto-scaling, whether horizontal or vertical, is the best part.
OpenShift's horizontal pod scaling is more effective and efficient than that used in Kubernetes, making it a superior choice for scalability.
Red Hat OpenShift scales excellently, with a rating of ten out of ten.
 

Stability Issues

Sentiment score
8.3
Amazon EKS is stable and reliable, excelling in diverse environments with effective AWS support for configuration challenges.
Sentiment score
7.7
Red Hat OpenShift is praised for stability, reliability, and features like Blue-Green deployment, with minor issues quickly resolved.
Amazon EKS is very stable, and when properly configured, I rate it ten out of ten.
Amazon EKS is stable.
It provides better performance yet requires more resources compared to vanilla Kubernetes.
I've had my cluster running for over four years.
It performs well under load, providing the desired output.
 

Room For Improvement

Amazon EKS requires improvements in user interface, stability, cost management, documentation, and support for third-party plugins.
Red Hat OpenShift needs better documentation, improved usability, and enhancements in security, integration, technical support, and installation processes.
Simplifying these will enable more people, not just those with strong foundational knowledge, to work effectively with these services.
Amazon EKS can be improved by having the maintenance of Kubernetes versions managed better, as everything is handled by the Kubernetes team and possibly a separate team at AWS.
A UI could help generate config files, simplifying the process for developers who are not architects.
Learning OpenShift requires complex infrastructure, needing vCenter integration, more advanced answers, active directory, and more expensive hardware.
Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services.
We should aim to include VMware-like capabilities to be competitive, especially considering cost factors.
 

Setup Cost

Amazon EKS offers flexible pricing but may be costly compared to GCP and Azure, especially for small businesses.
Red Hat OpenShift pricing is high but potentially cost-effective for large enterprises, offering comprehensive support and enterprise capabilities.
The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups.
Now, it stands at six or seven due to optimizing our workload.
Initially, licensing was per CPU, with a memory cap, but the price has doubled, making it difficult to justify for clients with smaller compute needs.
Red Hat can improve on the pricing part by making it more flexible and possibly on the lower side.
The cost of OpenShift is very high, particularly with the OpenShift Plus package, which includes many products and services.
 

Valuable Features

Amazon EKS simplifies Kubernetes with serverless deployments, auto-scaling, robust security, and multi-cloud support for efficient application management.
Red Hat OpenShift is valued for its security, scalability, automation, multi-cloud flexibility, and efficient management interface.
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.
The main benefits that I received from using Amazon EKS are that it is a managed cluster and offers simplicity.
By default, if you just install Amazon EKS, you can deploy your application, but to have it enterprise-ready, you have to configure a number of other things that will boost productivity.
Because it was centrally managed in our company, many metrics that we had to write code for were available out of the box, including utilization, CPU utilization, memory, and similar metrics.
The concept of containers and scaling on demand is a feature I appreciate the most about Red Hat OpenShift.
A valuable feature of Red Hat OpenShift is its ability to handle increased loads by automatically adding nodes.
 

Categories and Ranking

Amazon EKS
Ranking in Container Management
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
52
Ranking in other categories
Container Security (19th)
Red Hat OpenShift
Ranking in Container Management
12th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
62
Ranking in other categories
PaaS Clouds (3rd), Server Virtualization Software (9th), Hybrid Cloud Computing Platforms (6th), Agile and DevOps Services (1st)
 

Mindshare comparison

As of June 2025, in the Container Management category, the mindshare of Amazon EKS is 12.2%, down from 13.5% compared to the previous year. The mindshare of Red Hat OpenShift is 1.8%, up from 1.0% 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.
Pratul Shukla - PeerSpot reviewer
Adopting a flexible and efficient approach with noticeable improvements in operational costs and continued challenges in job management
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The entire company uses Autosys, but we are not able to integrate it effectively. We need intermediate servers to run OC utility commands and initiate the cron job. We have to do a lot of modifications to ensure our batches work properly. With physical or virtual servers, even in AWS, we are able to write and manage multiple jobs. Managing batches in Red Hat OpenShift has been a significant challenge. Integrating third parties is a challenge with Red Hat OpenShift. For example, with Elasticsearch, onboarding itself was difficult, running file beats and dealing with routing issues. It is not straightforward, especially since we have some components in AWS as. AWS has many capabilities that come out of the box and are easier to work with compared to Red Hat OpenShift. Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud.
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
857,688 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%
Financial Services Firm
30%
Manufacturing Company
9%
Computer Software Company
9%
Insurance 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?
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...
How does OpenShift compare with Amazon AWS?
Open Shift makes managing infrastructure easy because of self-healing and automatic scaling. There is also a wonderful dashboard mechanism to alert us in case the application is over-committing or ...
Which would you recommend - Pivotal Cloud Foundry or OpenShift?
Pivotal Cloud Foundry is a cloud-native application platform to simplify app delivery. It is efficient and effective. The best feature is how easy it is to handle external services such as database...
What do you like most about OpenShift?
OpenShift facilitates DevOps practices and improves CI/CD workflows in terms of stability compared to Jenkins.
 

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
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Amazon EKS vs. Red Hat OpenShift and other solutions. Updated: June 2025.
857,688 professionals have used our research since 2012.