Overview
Build, deploy and run cloud-native apps with Red Hat OpenShift on Amazon Web Services for regions outside of EMEA.
For regions outside of the EMEA region, Red Hat OpenShift is the leading enterprise application platform for enterprises who want to build, deploy and run cloud-native applications from a hybrid cloud to the edge. It provides full-stack automated operations, brings security to the entire application development process, offers a consistent experience across all environments, and self-service provisioning for developers.
Running Red Hat OpenShift on Amazon Web Services gives you a complete, orchestrated framework you need to build, deploy, run and manage containerized applications in a hybrid cloud environment. It includes an enterprise-grade supported Linux operating system and container runtime, networking, monitoring, container registry, and authorization solutions. These components are tested and integrated to deliver unified operations on a complete platform.
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.
Highlights
- Red Hat OpenShift provides a consistent application platform for the management of existing, modernized, and cloud-native applications that runs on any cloud.
- Red Hat OpenShift includes self-service access to developer tools, a browser-based IDE, a broad selection of coding languages, data and storage services, and full CI/CD services for automating application delivery and supporting a DevOps process.
- Manage applications, virtual machines, and containers from a single control plane. Regardless of where Red Hat OpenShift is installed, the interface remains the same for administrators and developers, allowing you to control clusters and services.
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.326 |
g5.2xlarge | $1.306 |
c6id.2xlarge | $1.306 |
r6a.12xlarge | $7.834 |
z1d.3xlarge | $1.958 |
m5d.xlarge | $0.653 |
x1e.4xlarge | $2.611 |
g3.4xlarge | $2.611 |
r5a.24xlarge | $15.667 |
d2.2xlarge | $1.306 |
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
Integrated pipelines have accelerated continuous deployment and improved incident response
What is our primary use case?
I work with Red Hat OpenShift Container Platform , specifically the Container Platform, OCP. We are using Red Hat OpenShift Container Platform to deploy our application for continuous deployment, to deploy it on this application, and to administrate our application. To see everything, if we have an incident or we have a problem, we go to this platform to check where the problem is, and if we have to fix it or increase resources, we do it in this platform.
I have been working with Red Hat OpenShift Container Platform for less than six months as we are migrating to this platform. We are starting to use it. We have other people that are helping us to administrate it to administrate our application on this platform. I am not the most senior one in this area, but I can share what I have seen and how we use it.
What is most valuable?
The powerful thing about Red Hat OpenShift Container Platform is for deploying how to install our application, how to deploy it, and it is easy to work with this platform to do DevOps or CI/CD. It is easy to do CI/CD with this platform and to add functionality in our application. We can add functionality in our application easily with this platform. We can go quickly from dev testing, integrating, and deploying quickly with this platform.
The integrated CI/CD pipelines of Red Hat OpenShift Container Platform have a time-saving impact on our development process. When we use the CI/CD functionality, the main saving is really important compared to combining many other tools to have the same result. In Red Hat OpenShift Container Platform, you have everything integrated, but in other platforms, you have to set up many tools to have the same output. In Red Hat OpenShift Container Platform, it is ready to set up, or almost set up; you only have to configure it. Time-saving is one of the important things.
What needs improvement?
I have something regarding Red Hat OpenShift Container Platform. It is a little bit complicated to set up Red Hat OpenShift Container Platform on a local server. You have to buy or have many resources, many physical resources to set it up. If they could do something lighter to set up or a light version for a personal computer or something that does not need enormous resources, that would be helpful.
For how long have I used the solution?
I have been working with Red Hat OpenShift Container Platform for less than six months as we are migrating to this platform.
What do I think about the scalability of the solution?
The auto-scaling capabilities of Red Hat OpenShift Container Platform have helped handle workload variations. Scalability is the main argument. You can configure it easily by just modifying one file. You can scale your application as you want, easily. It is really the easy part that is interesting in Red Hat OpenShift Container Platform, to scale.
How are customer service and support?
I rate the customer service as three out of ten.
Which solution did I use previously and why did I switch?
Before Red Hat OpenShift Container Platform, I used something else; it is a tool of IBM called WebSphere. I decided to switch from WebSphere to Red Hat OpenShift Container Platform because IBM stopped the support of WebSphere to let everyone move to Red Hat OpenShift Container Platform.
How was the initial setup?
From my perspective, this configuration process of Red Hat OpenShift Container Platform is straightforward. With the internet, you can handle it.
What about the implementation team?
I participated in a part of the configuration of Red Hat OpenShift Container Platform, not the setup. In Red Hat OpenShift Container Platform, you have two profiles, an administrator and a developer. I belong to the developer part. I participated to configure one part of Red Hat OpenShift Container Platform.
What was our ROI?
I am not really in the financial part to see the benefits of Red Hat OpenShift Container Platform, but we see that we have less spending costs. I think we had to move to this platform because our older platform is not yet supported. We had to move to this platform. Maybe we had to move to this platform more than we did it by choice, more so than searching for financial advantages.
Which other solutions did I evaluate?
Before choosing Red Hat OpenShift Container Platform, I was not the only one evaluating options. The big managers chose to follow the IBM advices.
What other advice do I have?
I am not really in the financial part to see the benefits of Red Hat OpenShift Container Platform, but we see that we have less spending costs. I think we had to move to this platform because our older platform is not yet supported. We had to move to this platform. Maybe we had to move to this platform more than we did it by choice, more so than searching for financial advantages.
I cannot really describe how Red Hat OpenShift Container Platform's policy-based governance has helped my organization in maintaining application security at scale because we have other services that are more focused on security and respecting confidentiality. I think it respects everything to be integrated in a professional area.
Red Hat OpenShift Container Platform's developer-first workflow has contributed to enhancing my team's productivity by helping us to increase our reactivity. When we have problems, we can fix them quickly. I would say the main benefit is having more reactivity to address a bug or problem to fix. My overall rating of Red Hat OpenShift Container Platform is eight out of ten.
Platform has simplified microservice deployments and has improved monitoring and secret management
What is our primary use case?
My main use case for Red Hat OpenShift Container Platform is to manage our banking application, where we manage a number of microservices. We use four to five clusters, and under those clusters, we have 50 plus namespaces, which are projects.
We manage those microservices with Red Hat OpenShift Container Platform by working on end-to-end CI/CD deployment where our task is to monitor the application that we have deployed. We have 50 plus microservices, and daily we deploy those microservices with new images.
What is most valuable?
With the help of Red Hat OpenShift Container Platform, we don't need to use Prometheus and Grafana separately, as Red Hat OpenShift Container Platform's inbuilt feature provides monitoring and logs for a pod and a node. It is also great for project management because it is GUI-based, making it very helpful.
One of the best features Red Hat OpenShift Container Platform offers is that it is GUI-based and enterprise-ready. We can see logs directly and solve issues such as crash loop back errors and image pull back errors if anything happens. We can check events, logs, and we also use it to store secrets.
Red Hat OpenShift Container Platform has positively impacted my organization by allowing us to check logs whenever an error occurs, or a pod is in a pending state or in a crash loop back error. It makes end-to-end deployment very easy, and the secret management, certifications, and everything are very helpful.
After using Red Hat OpenShift Container Platform, I have seen outcomes such as reduced crash loop back errors and image pull back errors. The certificate management is also easy with this, and we can check metrics such as CPU and memory usage.
What needs improvement?
Red Hat OpenShift Container Platform can be improved by adding more features such as viewing things in dashboard mode, which would be helpful. An inbuilt chat AI feature would also be very helpful for managing errors.
Regarding Red Hat OpenShift Container Platform's AI capabilities, I find its governance and security to be strong enough. However, the secrets we store in Red Hat OpenShift Container Platform are base64 encoded and should be encrypted to prevent unauthorized access if someone else is using Red Hat OpenShift Container Platform.
For how long have I used the solution?
I have used Red Hat OpenShift Container Platform for application deployment for a total of four years.
What do I think about the stability of the solution?
Red Hat OpenShift Container Platform is stable in my experience.
What do I think about the scalability of the solution?
The scalability of Red Hat OpenShift Container Platform is good.
How are customer service and support?
Customer support is great.
I would rate the customer support 10 out of 10.
Which solution did I use previously and why did I switch?
Before choosing Red Hat OpenShift Container Platform, we did not evaluate other options because we have Kubernetes , but we chose Red Hat since it is enterprise-based.
What was our ROI?
We can say that we have seen a return on investment from using Red Hat OpenShift Container Platform in terms of time saved, but I am not aware of any money saved. It is definitely time-saving.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that the pricing is not that much due to the pay-as-you-go model of AWS . However, I am not aware of the setup cost as I have only worked on it and have not purchased it personally.
What other advice do I have?
I would rate Red Hat OpenShift Container Platform an eight out of ten.
I rate it an eight because the features that I have mentioned are not in Red Hat OpenShift Container Platform yet, which stops it from being a ten.
My advice to others looking into using Red Hat OpenShift Container Platform is that they must go with it, especially if they lack knowledge on CLI-based systems since it is also GUI-based, making it scalable and reliable.
I have a great experience with Red Hat OpenShift Container Platform.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
OpenShift Simplifies Kubernetes Orchestration
OpenShift Delivers Enterprise-Grade Kubernetes Without the Chaos
Seamless upgrades have protected business operations and support secure, flexible deployments
What is our primary use case?
The primary use cases include troubleshooting issues, installation, implementation, and design.
What is most valuable?
The benefits I have seen from using Red Hat OpenShift Container Platform include that it provides a seamless application business, and the business is never going to be impacted because deployments and upgrades can be completed without impacting the real business. Seamless activity can also be performed on the cluster without impacting the application.
Red Hat OpenShift Container Platform 's policy-based governance has helped my organization maintain application security at scale because ACS is also there, and Red Hat is always maintaining things with hardening methods, always coming with hardened images, and we are frequently upgrading the minor and major versions, so it will be mitigated in that way.
Red Hat OpenShift Container Platform's hybrid and multi-cloud support will help to move applications, and if in the future any other platform wants to move, it is easy for the application to move from one platform to another without major impact.
Red Hat OpenShift Container Platform's auto-scaling capabilities have helped handle workload variations majorly at the HPA level at the pod level, but at the node level, we are not using the cloud mechanism, and that is why we are not enabling the node level.
Red Hat OpenShift Container Platform's developer-first workflow has contributed to enhancing my team's productivity because we have many custom scripts that give us reports of everything, ODR, and health-related things, so based on productivity, we are taking actions on that.
What needs improvement?
Red Hat OpenShift Container Platform needs some improvements, for example, in upgrade time, as normally, an extended upgrade method should be allowed, but sometimes if anyone clicks twice, it tries to upgrade the second level and gets stuck, so that area should be enhanced.
The strictness of the SSD and HDD also should be aligned, because in some environments, we cannot strictly make some rules related to HDD, since Red Hat is strictly making a rule after 4.16 to adopt SSD instead of HDD, which in some environments will not allow, so some workaround should be done on that.
Red Hat OpenShift Container Platform is the best option, but as many companies and the world are mainly looking for security purposes, the clear text format needs to be adopted instead of any third party. Red Hat has to develop its own product, as HashiCorp and CyberArk Conjur exist, but Red Hat needs to protect the clear text format because the secret should not be seen by anyone. Currently, it is a clear text method allowing anyone in the namespace to see the username and password, which should be controlled in that way.
The major improvements needed are related to upgrade time and strict rule-making.
For how long have I used the solution?
I have been using Red Hat OpenShift Container Platform for almost eight years.
Which solution did I use previously and why did I switch?
Before Red Hat OpenShift Container Platform, I also worked with OKD separately and Kubernetes .
How was the initial setup?
The initial setup for Red Hat OpenShift Container Platform is straightforward because I am using extra features like govc from VMware to update the parameters and these kinds of things, so it is easy on that, with no issues.
What other advice do I have?
I feel that the pricing of Red Hat OpenShift Container Platform depends on the salespeople, as they can decide that, with some companies giving a cheap price and others giving a high price for the same things. I would rate this product an 8 out of 10.