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
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.
Platform has transformed our cloud into a secure, unified home for diverse modern applications
What is our primary use case?
I have been using Red Hat OpenShift for more than six years.
I implement Red Hat OpenShift for our customers as we are a service provider, and we implement it in our cloud. We provide it as a service for our customers, and we deploy some of the applications that we have implemented in our company and for my personal use.
I deployed and developed an audit application which runs all the compliance requirements for a company, including multiple platforms and multiple standards such as ISO and others, and NCA for Saudi Arabia, and any other standard can work on it. This is one example. I also created a personal application for a t-shirt integrated with AI where we can create an image and print it on a shirt and ship it to the customer. I implemented another application for waste management, which was totally developed and deployed by myself for my personal use and the waste management for one of our customers. Additionally, I had another application deployed for one of our customers, where my role was to deploy Red Hat OpenShift and to make sure their application is deployed and available. This is for bill invoicing and financial operations. For one of the hospitals, our customer, I deployed the application for monitoring diabetes patients. My role there was to deploy it and to make the application available, providing all the requirements, ingress, configuration, storage, and other things. These are examples of what I have done.
Red Hat OpenShift by default is secure, more than native Kubernetes , as it has a limitation for the run as. The container by default does not run as root; this is one of the examples. The integration with ACS allows centralized policy deployment and enforcement, alongside great observability and monitoring. Red Hat OpenShift is actually enterprise-grade Kubernetes with all the accessories and main features.
What is most valuable?
One of the best features of Red Hat OpenShift is that it has the catalog, the application catalog, and the operator hub, which allows us to deploy things easily and straightforward without going into a lot of hassles. This is one of the main things, in addition to having integration with ACM and ACS, where we can have the ability to manage multiple clusters and to secure them, deploy them, manage them, run GitOps and day-two operations, as well as upgrades and other functionality which is made easy using these tools. Red Hat OpenShift also provides virtualization capabilities, and I am currently working with Zain to make a project where we will convert F5 appliances to virtual machines and to manage them through Red Hat virtualization, OVE. Red Hat OpenShift is a unique platform because it provides the features for both worlds, containerization, and VMs at the same time, requiring you to learn one skillset in order to manage all of this at the same time.
In the beginning, our cloud depended only on virtual machines, so I introduced this to our management to start to work with microservices and with containerization. This was adapted in our cloud, providing us the capability to sell more of these features and to reduce the hardware requirement by about thirty percent, following the trends of using containerization for all modern applications. In addition, it reduced the time to develop and to deploy a new application; all we need is using Jenkins for CI/CD. Once we commit any code, it gets triggered, and it will implement the new container in a very flexible and easy way, within seconds. This decreased the time to market and increased agility, allowing us to capture new opportunities very fast.
What needs improvement?
There is perhaps one thing about the deployment of Red Hat OpenShift. Currently, there are two new ways to deploy Red Hat OpenShift, which are easier with assisted deployment and agent-based deployment. However, previously it needed a lot of requirements on the infrastructure side if we are using UPI, user-provided infrastructure. If the deployment of Red Hat OpenShift itself can be easier and more flexible, it would be great.
For how long have I used the solution?
I have been using Red Hat OpenShift for more than six years.
What do I think about the stability of the solution?
Red Hat OpenShift is stable.
It is great. Red Hat OpenShift can scale to thousands of nodes, allowing multiple clusters to be managed in different geolocations and managed by centralized advanced cluster management, ACM.
What do I think about the scalability of the solution?
Regarding scalability, Red Hat OpenShift has a lot of scalability capability, including about two thousand machines in one cluster and multiple cluster management, centralized management through ACM and ACS, which provides a very secure way to manage centrally all the features and to enforce policies.
In the beginning, our cloud depended only on virtual machines, so I introduced this to our management to start to work with microservices and with containerization. This was adapted in our cloud, providing us the capability to sell more of these features and to reduce the hardware requirement by about thirty percent, following the trends of using containerization for all modern applications.
How are customer service and support?
The response time for customer support is excellent, and they go deep and can resolve things easily.
The documentation and support that we get from Red Hat are very sufficient, and this differentiates between enterprise-grade Kubernetes and native Kubernetes or perhaps Kubernetes from other vendors.
Which solution did I use previously and why did I switch?
We used native Kubernetes before Red Hat OpenShift, actually, deploying it through kubeadm. The issue with Kubernetes is that it is just the engine; Red Hat has all the requirements to give you a complete solution. Red Hat OpenShift provides the complete ecosystem, all the integrations, and the tools which I mentioned before, which are already integrated and easy to be used. You do not need to grab open-source solutions for storage or other things, and you do not have to do a lot of customization, needing to comply with each version. Red Hat OpenShift is tested and vetted, making things easier to be deployed, supported, and managed, and it is more trustworthy.
How was the initial setup?
There is perhaps one thing about the deployment of Red Hat OpenShift. Currently, there are two new ways to deploy Red Hat OpenShift, which are easier with assisted deployment and agent-based deployment.
What about the implementation team?
We are a partner with Red Hat; we sell their services and licenses, and we do the implementation ourselves.
What was our ROI?
We did not measure our return on investment in a very accurate way, but as I mentioned, we could decrease the time needed to deploy any application, enabling us to capture new opportunities faster, go to market faster, and maintain the availability and security of all our applications.
What's my experience with pricing, setup cost, and licensing?
We work with Red Hat or our distributor in Saudi Arabia. We send our requirements as part of the RFP describing what we need, and we get the pricing from our distributor. There is an easy way to price the subscription of the support per CPU, per VM, so it is easy to be priced, but we depend on an official quote usually from our distributor.
Which other solutions did I evaluate?
Red Hat OpenShift by default is secure, more than native Kubernetes, as it has a limitation for the run as. The container by default does not run as root; this is one of the examples. The integration with ACS allows centralized policy deployment and enforcement, alongside great observability and monitoring. Red Hat OpenShift is actually enterprise-grade Kubernetes with all the accessories and main features.
What other advice do I have?
Our go-to-market and our deployment for any application, the time is reduced perhaps by eight times. It is very fast because you have consistency for all deployed containers; it is not like a virtual machine where you have to deploy individually for each virtual machine or you have to copy code here and there. It takes seconds because the containers spin out very fast; they are very lightweight. The things that we used to do in days, now take a couple of minutes to be done. So, that is approximately the number—mostly it is reduced by eight.
We are providing our cloud to our customers, so we are a service provider. We deploy Red Hat OpenShift in our cloud and host customers' applications through it. Some of our customers prefer Red Hat OpenShift on Azure or on AWS , so we deploy it there when needed, but our main deliverable is through our cloud.
We have our own cloud provided by our company, making us a local cloud provider. We are not a hyper integrator, nor a hyper-scaler. We provide it through our cloud and deployed a couple of customers on Azure ; this is what I recall.
I would advise others looking into using Red Hat OpenShift to take the step and to go fast into it because it will save them a lot of money and provide them with all the features, flexibility, security, and others. I give this product a rating of ten out of ten.
Private AI agents have been deployed securely and integrate smoothly with observability tools
What is our primary use case?
I'm changing to AI, so I'm implementing platforms for agents, specifically for artificial intelligence and agentic platforms.
It is to deploy agents in a sovereign and private tenant. Basically, when customers don't like to share their information with any cloud provider, they prefer to keep the information local. So they deploy their own private cloud, and most of them are using Red Hat OpenShift .
What is most valuable?
I find support for Kubernetes and security are the most useful features in Red Hat OpenShift .
What I appreciate from Red Hat OpenShift is the capacity to provide an integrated and secure environment that is more or less better than creating the environment from scratch or based on standard Kubernetes . Red Hat OpenShift provides a lot of features that help us to operate the platform in a very professional and efficient way, instead of using low-level tools provided with the open-source capacities. For us, it is a very practical environment in which we can quickly develop features—not using directly AI capacities from Red Hat OpenShift, but our own capacities, in a very integrated way.
The main benefits Red Hat OpenShift provides for me as a final user include the capacity to integrate third-party tools and also the integration between observability, security, and monitoring capacities.
What needs improvement?
Red Hat OpenShift is very expensive. I am starting to evaluate the capacities specifically related to artificial intelligence. The suite also integrates a lot of open source, which is more or less aligned with my strategy that always tries to use open source. However, as far as I know, it's not so flexible using the components by themselves, but I don't really have firsthand experience. That's what I've been told by the people working with them. It's not so flexible, but you win in integration and lose a little in the capacity of flexibility or making your platform more flexible.
For how long have I used the solution?
I've been working with Red Hat OpenShift for maybe one year.
What do I think about the stability of the solution?
I rate the stability of Red Hat OpenShift as quite robust. I'm satisfied with it.
What do I think about the scalability of the solution?
From one to ten, I would rate the ability to scale as nine.
How are customer service and support?
I would also rate the technical support from Red Hat as nine.
Which solution did I use previously and why did I switch?
I no longer use VMware and Tanzu data solutions because I changed my profile and my department.
How was the initial setup?
For us, the initial setup for Red Hat OpenShift is complex. It's complex, but also powerful.
What about the implementation team?
In my case, I directly work with Red Hat for purchasing the license.
What was our ROI?
Overall, I would give Red Hat OpenShift a final mark of nine.
Which other solutions did I evaluate?
As a competitor to Red Hat OpenShift, I think Rancher may be a possibility, but it's very, very far from what Red Hat OpenShift provides. I don't really know any other commercial distribution of Kubernetes. The alternative would be to create the cluster by yourself, using the components or the open-source components, but it would be really, really complicated. Also, alternatives in cloud exist, using the Kubernetes services from cloud providers like Fargate or AKS. But I would rather prefer to create Red Hat OpenShift on top of the cloud instead of using it. It's more expensive, obviously, but we have good experiences.
What other advice do I have?
In terms of functionality, I'm working with Red Hat OpenShift in terms of infrastructure and monitoring, so in these capacities, we are very satisfied.
I can recommend it to other users. Overall, I would give Red Hat OpenShift a final mark of nine.