Overview
Support applications spanning multiple infrastructures and clouds outside of the EMEA regions.
Red Hat® OpenShift® Platform Plus builds on the capabilities of enterprise Kubernetes platform Red Hat OpenShift with advanced multicluster security features, day-2 management capabilities, integrated data management, and a global container registry to protect, manage, and provide security for applications in a consistent way throughout the software life cycle across clusters. It includes multicluster Kubernetes management, security with DevSecOps capabilities to protect the software supply chain, infrastructure, and workloads; and a central and scalable container registry.
Includes:
Red Hat OpenShift Container Platform: An enterprise Kubernetes container platform with automated operations to manage applications across the hybrid cloud, multi-cloud, and edge deployments. Red Hat Advanced Cluster Management for Kubernetes: Application life-cycle management and policy management across multiple Kubernetes clusters. Red Hat Advanced Cluster Security for Kubernetes: Kubernetes-native security that provides governance, security, and compliance through the entire application life cycle. Red Hat Quay: A scalable, private, and secure central registry to provide enterprise capabilities compared to standard or public registries. Red Hat OpenShift Data Foundation, offers instant access to file, block, and object data services for all workloads and delivers smart functionalities for object data. (Essentials edition is included at no additional cost with OpenShift Platform Plus)
IMPORTANT: This listing is not meant for direct consumption by deploying a single virtual machine. Please follow the instructions in https://access.redhat.com/articles/6675791 and DO NOT create a VM from this offering directly.
Highlights
- Monitor running workloads for security issues or threats with system-level data collection and analysis as well as more than 60 security policies that can be applied and enforced throughout the entire application life cycle.
- Apply consistent operational policies for security, configuration, compliance, and governance to Red Hat OpenShift clusters across on-premise and cloud infrastructures.
- Apply a DevSecOps approach by integrating declarative security into developer tooling and workflows. Use Kubernetes-native controls to mitigate threats and enforce security policies that minimize operational risk to your applications.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
m5.large Recommended | $0.408 |
m6in.12xlarge | $9.797 |
c6id.12xlarge | $9.797 |
g5.12xlarge | $9.797 |
r5dn.xlarge | $0.816 |
c6a.12xlarge | $9.797 |
z1d.xlarge | $0.816 |
m5dn.16xlarge | $13.062 |
r6a.2xlarge | $1.633 |
m5zn.3xlarge | $2.449 |
Vendor refund policy
All fees are non-refundable
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Additional details
Usage instructions
IMPORTANT: This marketplace listing is not meant for direct consumption by deploying a single virtual machine. Please follow the instructions in https://access.redhat.com/articles/6675791 . DO NOT create a Virtual Machine from this offering directly.
RHCOS is supported only as a component of OpenShift Container Platform 9.6 for all OpenShift Container Platform machines. RHCOS is the only supported operating system for OpenShift Container Platform control plane, or master, machines. While RHCOS is the default operating system for all cluster machines, you can create compute machines, which are also known as worker machines, that use RHEL as their operating system. There are two general ways RHCOS is deployed in OpenShift Container Platform 9.6:
- If you install your cluster on infrastructure that the installation program provisions, RHCOS images are downloaded to the target platform during installation. Suitable Ignition config files, which control the RHCOS configuration, are also downloaded and used to deploy the machines.
- If you install your cluster on infrastructure that you manage, you must follow the installation documentation to obtain the RHCOS images, generate Ignition config files, and use the Ignition config files to provision your machines.
- For more information please see the Deploying RHCOS documentation.
Resources
Support
Vendor support
This offering comes with a Red Hat Premium support subscription. To learn more about this support coverage and SLAs, please consult the OpenShift Enterprise Support Policy . To activate Red Hat support for your subscription you must click the link below where you will be redirected to the Red Hat console. Once your support account is activated you will receive a confirmation email from Red Hat. Upon receipt of this email you will have access to all the benefits of Red Hat support including the following: - Access to extensive open-source software repositories in a variety of packaging formats. - Access to the Red Hat community of experts including world-class support engineers, asynchronous support ticketing, knowledgebase articles, and how-to guides. - Operational guidance and automation with advanced analytics and monitoring tools, patching, upgrades, and remediation services.To enable Red Hat Support for this subscription and for all of your Red Hat on AWS Marketplace purchases, follow the instructions at https://aws.amazon.com/marketplace/pp/prodview-fyphbrmils4dg . Get answers quickly by opening a support case with us at
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Modernization has reduced server footprint and is simplifying container-based application work
What is our primary use case?
My main use case for Red Hat OpenShift is that in our organization, we are going into a modernization of our application where we are moving away from our traditional application approach. Now we are moving forward.
A specific example of how I'm using Red Hat OpenShift in my organization is that we have around 18 clusters and for now, we are maintaining around 16 applications in Red Hat OpenShift.
Day-to-day, I'm using Red Hat OpenShift as we are moving into adding applications to containers, using it regularly on troubleshooting issues, whatever the customer encounters.
What is most valuable?
The best feature Red Hat OpenShift offers in my experience is the Service Mesh . The recent update of the Service Mesh is a very good component of Red Hat.
Red Hat OpenShift has positively impacted my organization as the main focus was to reduce the physical servers we have in our warehouse. That helped us a lot in moving into containerization and handling the application.
After moving to Red Hat OpenShift, I noticed we moved around 16 applications, and each application used to use around six to eight servers. So, roughly around 110-150 servers have been reduced right now.
What needs improvement?
Red Hat OpenShift can be improved as I commonly use the CLI console, but I have not explored much on the graphical console. I have been working on the command line mostly and not explored much on the console. I feel like it might be more advanced and useful for newcomers who are not familiar with the command line.
Further needed improvements in Red Hat OpenShift include that getting the providers will be a little bit tricky in the console. When I tried to add searching on providers, that was a little bit tricky.
For how long have I used the solution?
I have been using Red Hat OpenShift for one year.
What do I think about the stability of the solution?
In my experience, Red Hat OpenShift is very stable.
What do I think about the scalability of the solution?
Scalability-wise, Red Hat OpenShift is pretty much good, as it is one click where we can scale any of the applications.
How are customer service and support?
The customer support of Red Hat OpenShift is good as I have reached out to them a couple of times. The customer support was easy. We have a premium membership with the Red Hat team, so it is very convenient and they get back to us as soon as we require. They are also knowledgeable.
Which solution did I use previously and why did I switch?
Previously, we have not used any other solutions before Red Hat OpenShift as we directly moved to it.
How was the initial setup?
Since deploying Red Hat OpenShift, I have seen a return on investment as it saved a lot. Once we deployed, there is very minimalistic time spent on troubleshooting issues. Everything is taken care of by the containers or the new pods we have deployed. Time was the major thing which saved a lot, and in terms of resources, it has reduced resource utilization so the remaining users can focus on other tasks.
What about the implementation team?
Our company has a business relationship with Red Hat as we are a partner.
What was our ROI?
Since deploying Red Hat OpenShift, I have seen a return on investment as it saved a lot. Once we deployed, there is very minimalistic time spent on troubleshooting issues. Everything is taken care of by the containers or the new pods we have deployed. Time was the major thing which saved a lot, and in terms of resources, it has reduced resource utilization so the remaining users can focus on other tasks.
What's my experience with pricing, setup cost, and licensing?
I may provide information about setup costs in another review at a later time.
Which other solutions did I evaluate?
Before choosing Red Hat OpenShift, we did not evaluate other options as this was an organization decision where we did not involve other tools.
What other advice do I have?
I rate Red Hat OpenShift a nine out of ten.
I rated it a nine because it made a lot of work easy for me comparatively to handling servers, where I used to work in monolithic applications. This helped me a lot when I moved to Red Hat OpenShift. Kubernetes was the part where I used to work on and when I moved to Red Hat OpenShift, it gave me a broader way where I can think or explore much on what is not there with Kubernetes . The functions and features all together in one place helped me a lot.
My advice for others looking into using Red Hat OpenShift is that I surely advise going with Red Hat OpenShift, which is a very convenient way to handle their applications and to reduce the cost of servers and whatever resources we spend. Those resources can be utilized much more efficiently with Red Hat OpenShift, and that is the very easiest way.
I have additional thoughts about Red Hat OpenShift in that I appreciate the documentation given by the Red Hat team. That helps us a lot from a learning perspective.
Platform has provided resilient clustered deployments and supports rapid rollback for safe changes
What is our primary use case?
A specific example of how I use Red Hat OpenShift to set up a product for customers is that it starts with determining how much a customer has to spend because when you're looking at clusters where you have actual control over the worker nodes, you have to determine what they are going to be. If you're doing something with an AWS cluster, then you need to work out what it's going to cost them on a monthly cycle.
What is most valuable?
Red Hat OpenShift has positively impacted my organization with its scalability, security, as well as the ability to control it effectively.
What needs improvement?
For how long have I used the solution?
What other advice do I have?
When I'm doing a traditional deployment with Red Hat OpenShift and I want to implement a change, if the change fails, all I need to do is reverse out the build. One click reverses out all the changes after the operational ones are done. This capability to deploy easily, effectively, and with great change management, as well as very granular control over who can do what and what processes can be run, is valuable.
I give Red Hat OpenShift a rating of nine because there are always difficulties in implementation.
Red Hat OpenShift is deployed in my organization across public cloud, private cloud, hybrid cloud, on-premises, as well as UAT. For our public cloud deployment, we use AWS . We purchased Red Hat OpenShift through the AWS Marketplace .
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Hybrid cloud platform has standardized telecom workloads and delivers consistent operations
What is our primary use case?
My main use case for Red Hat OpenShift is serving telco customers. A quick specific example of how I use Red Hat OpenShift for my telco customers involves different applications that reside in containers on those particular container platforms. This workload includes different parts such as AMF and UPF, which are the basic functions that I normally use as applications on Red Hat OpenShift.
How has it helped my organization?
Red Hat OpenShift has positively impacted our organization by adding significantly to our revenues because what we were doing through other vendors shows that with vanilla Kubernetes , there are many features and extra advantages in Red Hat OpenShift. It has had a strong positive impact on our organization by standardizing how we build, deploy, and operate applications across environments. One of the biggest benefits is its operational consistency. It provides a uniform Kubernetes platform across both on-premises and cloud environments. From an availability and reliability perspective, Red Hat OpenShift's built-in lifecycle management and automated upgrades, along with self-healing capabilities, have improved overall system stability.
Currently, I am not equipped with specific outcomes or metrics that demonstrate this positive impact, but it has significantly improved all these parameters.
What is most valuable?
The best features Red Hat OpenShift offers include security, hybrid multi-cloud, and bare metal flexibility. The Operator framework and lifecycle automation are also part of it, along with improved CI/CD and GitOps pipelines, and strong security with compliance features.
In my day-to-day operations, I find lifecycle automation to be the most valuable feature. Additionally, Red Hat OpenShift provides developers with hands-on extra capabilities and experiences.
What needs improvement?
Red Hat OpenShift can be improved by reducing its complexity. We could also have better UX, especially for day two operations. There is always some scope for optimization that we can address.
For how long have I used the solution?
I have been using Red Hat OpenShift for four years.
What do I think about the stability of the solution?
Red Hat OpenShift is stable and offers the most stability among all the competitors and enterprise-level solutions available.
What do I think about the scalability of the solution?
The scalability of Red Hat OpenShift is great, with many options available to scale it according to your requirement or demand. The extent to which you can scale depends on the environment you are deploying it in.
How are customer service and support?
The customer support is great, and we have many channels through which we can approach them.
Which solution did I use previously and why did I switch?
We have previously used VMware and Wind River, and while we still use them for some of our customers, we switched to Red Hat OpenShift because we found the best features there.
What was our ROI?
I do not have any readily available data regarding return on investment metrics, but I can say that we see relevant improvements in money saved, time saved, and fewer employees needed.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing involves a different team that handles all these aspects, so as a SRE, I do not need to worry about these things.
Which other solutions did I evaluate?
Before choosing Red Hat OpenShift, we evaluated other options such as Mesos, but Red Hat OpenShift is more futuristic.
What other advice do I have?
My advice for others looking into using Red Hat OpenShift is that you need to first get hands-on experience with the technology. It is based on vanilla Kubernetes, but they have added additional capabilities for which having basic knowledge is essential. You should go through their portals and lab environments available.
Secure integration has become standard as I run complex platforms with streamlined operations
What is our primary use case?
My main use case for Red Hat OpenShift is to set up the TIBCO platform on OpenShift, run applications on OpenShift using the TIBCO platform's data plane, and also being a platform engineer and a Kubernetes expert, I also tune Red Hat OpenShift to the most secure platform.
A quick specific example of how I use Red Hat OpenShift with the TIBCO platform involves the TIBCO platform's control plane and data plane that runs on Kubernetes . TIBCO is a vendor company which provides a lot of integration and messaging products along with various integration capabilities with almost any technology, and all of this makes it easier when the TIBCO platform runs on a Kubernetes platform. Everything is API-based, AI-ready, and everything works seamlessly on top of a Kubernetes platform.
What is most valuable?
The features of Red Hat OpenShift that I have configured include Red Hat OpenShift Security Context Constraints to cater to environments where everything is locked down and everything is monitored. In today's world, where people are trying to hack into the system, these things are quite important for any infrastructure or platform engineer or also a solution architect. Along with various other features of Red Hat OpenShift, it is quite important for me to design this easily and make it more secure.
The features of Red Hat OpenShift that stand out to me include the router configuration, the DNS integration, and many other small features, especially the UI which is out-of-the-box and the API support behind the scenes. All of this is quite handy and useful for many people who are using Red Hat OpenShift.
Red Hat OpenShift has positively impacted my organization by making many things easier to run securely, especially for a vendor company like TIBCO and their customers to run their application securely along with the TIBCO platform on Red Hat OpenShift.
Red Hat OpenShift offers very comprehensive security standards, everything is designed based on a zero-trust security framework, and I appreciate that about it. Most of the monitoring and observability part has been already taken by Red Hat OpenShift, along with the high availability aspects. Even when I am setting up Red Hat OpenShift on Azure or on-prem, it has various options and it is quite a mature platform compared to setting up my own Kubernetes.
What needs improvement?
There are a couple of sections related to security context constraints which can be improved in Red Hat OpenShift, wherein I am creating multiple Security Context Constraints for the same service account in Kubernetes. That can be improved.
For how long have I used the solution?
I have been using Red Hat OpenShift for almost two years now.
What do I think about the stability of the solution?
Red Hat OpenShift is stable. It creates multiple master nodes as a design, so I have a good experience with it.
What do I think about the scalability of the solution?
I have not tested Red Hat OpenShift's scalability, but I have checked the configuration, and it seems it is quite scalable and configurable.
How are customer service and support?
I have never had to use customer support in my case.
Which solution did I use previously and why did I switch?
I have previously used AKS, and I still use AKS. I did not switch, but for new clusters, I have been using Red Hat OpenShift.
How was the initial setup?
My overall impression is that a lot of time is saved while setting up Red Hat OpenShift Kubernetes. It definitely has a big ROI in terms of maintenance, having to hire many people to set up Kubernetes in a right way.
What about the implementation team?
Not me, but for customers, they purchased Red Hat OpenShift through the AWS Marketplace .
What was our ROI?
My overall impression is that a lot of time is saved while setting up Red Hat OpenShift Kubernetes. It definitely has a big ROI in terms of maintenance, having to hire many people to set up Kubernetes in a right way.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing shows that Red Hat OpenShift comes out as an expensive solution compared to having AKS, GKE , or EKS.
Which other solutions did I evaluate?
I have evaluated AKS, GKE , EKS, and setting up my own Kubernetes platform, especially using Red Hat OpenShift itself.
What other advice do I have?
My advice to others looking into using Red Hat OpenShift is to go into the details and set up Red Hat OpenShift in the right way. I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Cloud migrations have improved security workflows but documentation and support still need work
What is our primary use case?
My main use case for Red Hat OpenShift involves two cases: the first case is about the migration of QRadar and Red Hat OpenShift for the cloud, which relates to the process of antivirus, XDR , and SOAR and SIEM . The second case is the use for the migration in ARO, Microsoft Azure Red Hat OpenShift, for the migration of OpenCTI from on-premise to the cloud.
A quick specific example of how I used Red Hat OpenShift for one of those migrations is the particular process of the migration about the OpenCTI. The OpenCTI migration involved a process where we used Docker for the OpenCTI to function correctly when implemented, which was the main challenge.
I do not have anything else to add about my main use case or the migration processes with Red Hat OpenShift.
What is most valuable?
In my experience, the best feature Red Hat OpenShift offers is that the environment is easy to use. When I say environment needs, I mean that it is easy for the configuration and the management in the different environments. For example, when I use the API key, the configuration and connector, the environment provides easy visibility and allows me to watch the reports for the leadership in the company.
Red Hat OpenShift has positively impacted my organization, and now we use it more in the QRadar SIEM environment. However, in this case, IBM sold QRadar to Palo Alto, and our client changed the SIEM , so Red Hat OpenShift is not functional at this moment for QRadar.
What needs improvement?
Red Hat OpenShift can be improved by addressing any features, performance, or usability issues. In my view, the performance is very good, and the automatization of the new environment and new machine is fantastic because it is easier for my job in the company. My colleagues display information and the Docker functionality is good.
There are two small things I would suggest about the SOAR : the connection for the SOAR to send email and send communication to our colleagues and people in the company.
If I could change or improve one thing about Red Hat OpenShift, it would be to provide more information on the web because the information is limited and I need to explore more. I would change this about Red Hat OpenShift because I have known this all year and need more investigation.
For how long have I used the solution?
I have been using Red Hat OpenShift for about one year, more than one year ago.
What do I think about the stability of the solution?
Red Hat OpenShift is stable.
What do I think about the scalability of the solution?
In my view, Red Hat OpenShift's scalability is good, although I do not know for certain.
How are customer service and support?
The customer support for Red Hat OpenShift is bad because the support does not respond.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before Red Hat OpenShift. However, before it, we used VMware.
How was the initial setup?
Before choosing Red Hat OpenShift, we evaluated other options, specifically VMware.
What was our ROI?
I have seen a return on investment from using Red Hat OpenShift because I save money since I do not need the server in my data center on-premise, and I save money in monthly payments for availability and accessibility in the data center.
What's my experience with pricing, setup cost, and licensing?
I cannot respond to the question about my experience with pricing, setup cost, and licensing because the cost is another area, specifically the area of accounting and finance.
Which other solutions did I evaluate?
Before choosing Red Hat OpenShift, we evaluated other options, specifically VMware.
What other advice do I have?
My advice for others looking into using Red Hat OpenShift is to explore the tools, understand how Red Hat OpenShift migration to the cloud works, and recognize that the response and return on metric is efficient for good operation.
That is all I would like to add about the features of Red Hat OpenShift. I choose seven out of ten because my use is not total. Perhaps it is interesting for the use, but our environment in the company is easier to use with VMware. I rate this product seven out of ten overall.
I do not have any additional thoughts about Red Hat OpenShift.