Overview

Product video
Red Hat OpenShift Service on AWS (ROSA) is a fully-managed and jointly supported Red Hat OpenShift offering that combines the power of Red Hat OpenShift, the industry's most comprehensive enterprise Kubernetes platform, and the AWS public cloud.
Installation, monitoring, management, maintenance, and upgrades are performed by Red Hat site reliability engineers (SRE) covering the complete stack including the control plane, worker nodes and key services. You can also deploy clusters across multiple Availability Zones in supported regions to maximize availability. With all this covered, your ops team would only need to step in when managing user access for your developers who can take advantage of the 150+ AWS cloud-native compute, database, analytics, machine learning, networking, mobile, and other services.
The cluster can be scaled as your business' needs dictate. Choose from memory-optimized, compute-optimized, or general purpose EC2 instance types, with clusters sized to meet your needs. The service can be paid as you go with flexible hourly on-demand billing. You will receive a single bill from AWS for both Red Hat OpenShift & AWS consumption. An annual billing model is available as well; check out the pricing information below to find out what you can save with annual contracts.
Give your team the focus and tools to accelerate the development process with familiar APIs and existing Red Hat OpenShift tools for deployment in AWS, all from the AWS console.
Highlights
- Fully-managed and jointly supported Red Hat OpenShift offering that combines the power of Red Hat OpenShift, the industry's most comprehensive enterprise Kubernetes platform, and the AWS public cloud.
- Scale as your business needs and pay-as-you-go with flexible pricing with an on-demand hourly or annual billing model.
- Jointly operated & supported by Red Hat & AWS with an integrated support experience and 99.95% uptime SLA.
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.xlarge Recommended | $0.171 |
c7a.xlarge | $0.171 |
r8id.metal-96xl | $16.416 |
g5.12xlarge | $2.052 |
c6id.12xlarge | $2.052 |
m6in.12xlarge | $2.052 |
g6.24xlarge | $4.104 |
r5dn.xlarge | $0.171 |
m7a.8xlarge | $1.368 |
i7i.4xlarge | $0.684 |
Vendor refund policy
N/A
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.
Version release notes
Additional details
Resources
Vendor resources
Support
Vendor support
This product is jointly supported by Red Hat and AWS with an integrated support experience and 99.95% uptime SLA. You can either contact AWS support via the Support Center accessible from the AWS console (https://console.aws.amazon.com/support/ ), or you can open a support case via Red Hat's Customer Portal (https://access.redhat.com ) where you will also find self-service support articles and up to date phone contact information.
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.
Similar products

Customer reviews
Training and managing hybrid clusters has become streamlined and supports fast GUI‑driven operations
What is our primary use case?
My main use case for Red Hat OpenShift is training for several products, mainly for container orchestration, and I am currently using OCP. Previously, I trained on different products such as virtualization and Red Hat Enterprise Linux , and I also work with new products such as Red Hat AI OpenShift, which are useful for cluster management at the enterprise level.
When I am using Red Hat OpenShift for training and cluster management, I typically run different kinds of applications that are deployed on containers. People from both the development team and the operations team are involved; the development team focuses on automation and deliverable items, while the operations team mainly manages the administration work, including managing workloads and troubleshooting issues.
In addition to my main use case for Red Hat OpenShift, I also use virtualization, including different on-premises systems such as VMware, and we can migrate the VMs to Red Hat OpenShift for management. We can utilize different clusters in Red Hat OpenShift, as every cluster can be installed on our OCP, allowing us to manage them effectively. Red Hat OpenShift proves to be a good product for managing clusters, especially with its easy-to-use console that overlays Kubernetes , providing easy access to workloads, deployment options, and the ability to delete pods. Red Hat recently integrated the console with cloud capabilities, so we can view metrics, graphs, and events in a graphical user interface, eliminating the need to operate everything through the CLI.
What is most valuable?
The best features Red Hat OpenShift offers include the graphical user interface, which is a significant time-saving feature. There are different roles such as developer and administrator, and we can manage both administrative and developer tasks through the graphical interface that organizes information similarly to how it is executed in the CLI. We can access pod information, metrics, and everything easily, making it accessible even for non-technical users.
This has helped my team significantly by making many tasks easier; for those who are not as familiar with CLI, the graphical user interface is very useful and explanatory. If we need to perform an upgrade or work quickly, we can accomplish these tasks within minutes using the graphical user interface.
Red Hat OpenShift positively impacts my organization by making tasks easier with a consistent emphasis on high availability and reliability while also being cost-effective.
What needs improvement?
One area for improvement in Red Hat OpenShift is during upgrades, as there is currently no option to revert to a previous version if vulnerabilities or issues arise. I believe that providing such an option or the ability to take a previous snapshot would be beneficial.
Regarding needed improvements, I believe I covered most aspects with the graphical interface. The documentation contains a wealth of information, which continues to improve day by day, but I observe that there are still many concepts that could be elaborated on, and it is well-documented overall.
For how long have I used the solution?
I have been using Red Hat OpenShift for eighteen months.
What other advice do I have?
Red Hat OpenShift is deployed in my organization in various environments, including on-premises, public clouds such as Microsoft Azure , and in hybrid configurations with different clusters, such as Red Hat OpenShift for AWS .
My advice for others looking into using Red Hat OpenShift is that it is a new but valuable product, particularly suitable for enterprise-level applications.
I believe Red Hat OpenShift will become a significant player in the market. For those who understand its value, it proves to be very useful. My overall rating for this product is eight point five out of ten.
Enterprise-Ready Kubernetes Made Easy with Built-In CI/CD, Security, and Observability
For me, the biggest advantage is how it simplifies container management while still being enterprise-grade and scalable. Overall, it feels like Kubernetes with all the practical pieces already assembled and ready to use.
So even though it’s powerful, the added complexity and higher resource requirements are the main downsides for me.
The benefit is straightforward: I spend less time dealing with infrastructure headaches and more time focusing on real application development and scaling. Overall, it gives me stability, speed, and governance in one place.
Dev-Topology View, Seamless Integrations, and Best-in-Class Security for Governance
performace wise its on par with its competitors but the support and securiity is what makes it the best tools for governance activities.
OpenShift Simplifies Kubernetes Orchestration
Automation has improved multi-customer operations and delivers resilient, always-on infrastructure
What is our primary use case?
I work for IBM Control, so I work with Red Hat and VMware, both technologies. I am working with OpenShift. I have not worked on Red Hat CloudForms, but I work with OpenShift. I am the integrator. We are creating automation for our customers using OpenShift, and we have implemented Ansible Tower Platform for automating all the system admin tasks.
We create what you call Ansible playbooks, which we execute for automation and deploy across all of our multi-customers within IBM and Control.
What is most valuable?
I find the resilient infrastructure feature of OpenShift very valuable, as it has no downtime at all.
I find OpenShift to be very scalable.
What needs improvement?
The initial setup of OpenShift is difficult; it takes a while to set it up. It is difficult to set up OpenShift because of the infrastructure requirements and the customization required to set up the software.
I would advise others looking into using OpenShift that it is a pretty product, widely accepted by customers, easily scalable, and highly reliable, but it should be more user-friendly. I think it should be more user-friendly because many people request assistance setting it up the first time.
For how long have I used the solution?
I have been working with the solution for three and a half years.
What do I think about the stability of the solution?
OpenShift is stable. I would say the stability of OpenShift is nine out of ten.
What do I think about the scalability of the solution?
I find OpenShift to be very scalable. I would rate the scalability of OpenShift a nine.
How are customer service and support?
I think the technical support from Red Hat is good. I rate the technical support an eight. The reason for the rating of eight for technical support is that problems arise frequently, and they need to fix those issues, as it is open-source software requiring a lot of customizations.
Which solution did I use previously and why did I switch?
We actually buy everything with maintenance; when we buy the software, we buy it with maintenance.
How was the initial setup?
The initial setup of OpenShift is difficult; it takes a while to set it up. It is difficult to set up OpenShift because of the infrastructure requirements and the customization required to set up the software. I would rate the initial setup of OpenShift around five.
The initial setup of that solution took us weeks, but now the deployment is completed within days. It took one to ten days to set up OpenShift.
What about the implementation team?
There are twenty-four to twenty-five people involved in the deployment. I think two to three people are architects, along with all the engineers involved.
What other advice do I have?
I would advise others looking into using OpenShift that it is a pretty product, widely accepted by customers, easily scalable, and highly reliable, but it should be more user-friendly. I think it should be more user-friendly because many people request assistance setting it up the first time. I cannot think of any new features that could be added to make the solution better right now. My overall review rating for this solution is eight out of ten.