
Overview
Built on the Red Hat Enterprise Linux operating system (OS), Red Hat Enterprise Linux for SAP expands existing capabilities so you can get the most out of SAP's powerful analytics and data management portfolio. Red Hat Enterprise Linux High Availability (HA) provides all the necessary packages for configuring pacemaker based cluster that provides reliability and availability for critical production services. Extended Update Support (E4S) provides support on specific minor releases for 4 years from General Availability. Red Hat Insights can now be deployed for users with existing, cloud marketplace-purchased Red Hat Enterprise Linux (RHEL) system managed by Red Hat Update Infrastructure (RHUI).
Highlights
- High Availability solutions for S/4HANA, SAP HANA, and SAP Business Applications and 4 years Extended Update Support (E4S) from General Availability
- SAP specific technical components to support S/4HANA, SAP HANA, and SAP Business Apps
- Red Hat Enterprise Linux for SAP with HA and Update Services' cost is 0.10 $/hour for a small Instance type (.06 in infrastructure costs and .04 in software cost). and 0.225 $/hour for a large instance type (.13 in infrastructure costs and 0.095 in software cost). For information about reserved instance pricing, refer to to this URL: https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/
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 |
|---|---|
m7i.large Recommended | $0.016 |
t3.micro | $0.016 |
i4i.12xlarge | $0.02 |
r4.16xlarge | $0.00 |
r5n.4xlarge | $0.087 |
m7i.24xlarge | $0.00 |
r7a.32xlarge | $0.00 |
m4.large | $0.016 |
r5a.12xlarge | $0.02 |
r5b.24xlarge | $0.00 |
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
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
Latest Updates
Additional details
Usage instructions
To connect to the operating system, use SSH and the username ec2-user. All application controls are available via the command line by typing "commands /help".
Resources
Support
Vendor support
Getting Started
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
Years of cluster work have become smoother as I provision nodes and manage servers with confidence
What is our primary use case?
I am a RHCE certified and RHCSA certified professional. I use Red Hat Enterprise Linux (RHEL) to deploy the OS for node provisioning across any make of clusters. I work with the HPC cluster team and receive clusters on RHEL-based systems. Over the last seven years, I have been working with RHEL 7, RHEL 8, RHEL 9, and currently RHEL 10. I primarily work with HPC clusters.
Since creating HPC clusters is not part of my responsibilities, I focus mainly on installation, node provisioning, password management, SSH proxies, and NGINX and web server configuration.
What is most valuable?
There are several valuable features I appreciate. I can obtain any versions, software, or RPM packages easily through the subscription manager or without it. Red Hat Enterprise Linux (RHEL) is very hands-on for me and runs smoothly. It even runs on just 1 GB of RAM, which is excellent for my needs. The installation process is very easy compared to other distributions. Since I work with clusters, this simplicity is invaluable.
When comparing the installation process of Red Hat Enterprise Linux (RHEL) to other distributions, I find that a non-technical person can easily follow the prompts. The installation guides are clear and documented step-by-step. For example, the first prompt asks for language, keyboard, and installation preferences, and each step is straightforward. In contrast, Ubuntu and other distributions require creating disks and involve more complex UI elements that are not as user-friendly. Red Hat Enterprise Linux (RHEL) has a clean interface that allows even non-technical people to install the OS easily.
I have only studied from the direct books provided by Red Hat for RHCSA and RHCE certification, and every detail is available in their documentation and website. I appreciate the clean and detailed information provided in their resources.
What needs improvement?
I encounter pain points when trying to add patches for certain versions I need for RHEL purposes. While creating HPC clusters on RHEL 9, I sometimes need EPEL repositories for RHEL 7 or 8. Adding patches from these repositories is very painful because Red Hat Enterprise Linux (RHEL) 9 does not easily support these older package versions. This is a recurring problem I always face.
For how long have I used the solution?
I have been using Red Hat Enterprise Linux (RHEL) since I started my career, which is 6.7 years.
What do I think about the stability of the solution?
I have not experienced stability issues. I have used multiple OEMs including HP, Dell, Exatron, and NVIDIA servers. I always prefer recommending Red Hat Enterprise Linux (RHEL) to my customers because it is very stable. I have only experienced one server crash in all my years, and that was due to an OEM issue, not Red Hat Enterprise Linux (RHEL) itself. I have never encountered data problems or server crashes from Red Hat Enterprise Linux (RHEL).
What do I think about the scalability of the solution?
Scalability is not an issue. I can easily add more nodes to clusters. The installation is very fast, which allows me to scale quickly. I use Ansible and PXE servers to facilitate this process, and I can scale to many servers very quickly with Red Hat Enterprise Linux (RHEL).
How are customer service and support?
When I was working for a customer and faced an issue while installing a package, I requested Red Hat support and they helped me resolve it.
I have raised requests in the morning around 11:00 AM and received responses within one to two hours. They ask for logs and version information, and then provide a response within approximately 30 minutes. I give Red Hat support a nine out of 10 rating. I would give a full 10 if they could push their support to be slightly faster. When someone is on-site conducting installations and encounters an issue, that person needs to wait at least one or two hours for a response. Red Hat could improve by responding a bit more quickly.
How would you rate customer service and support?
Positive
What's my experience with pricing, setup cost, and licensing?
Regarding the pricing of Red Hat Enterprise Linux (RHEL) subscription, I believe the pricing is fair. The support that Red Hat provides is very good. Whenever I encounter issues, Red Hat always provides fast resolution. The pricing is justified given the quality of support offered.
Which other solutions did I evaluate?
I have used Ubuntu as an alternative distribution. However, I always choose Red Hat Enterprise Linux (RHEL) over every other distribution. I started my career learning from Red Hat Enterprise Linux (RHEL), which is the main reason I prefer it. Additionally, Ubuntu and other distributions have many dependencies that require adding different packages and configurations. When troubleshooting on Red Hat Enterprise Linux (RHEL), I find solutions easily. With Ubuntu, troubleshooting requires digging much deeper.
What other advice do I have?
I have been working with Red Hat Enterprise Linux (RHEL) for approximately seven years.
Regarding updates and maintenance, I only need maintenance time when upgrading the OS. When upgrading the kernel version or transitioning from RHEL 8 to RHEL 9, I only need to install the RPMs and reboot the server once. Maintenance primarily involves patching and the subsequent reboot requirement.
Every time a cluster issue occurs, Red Hat never requests high downtime or suggests data loss scenarios. They maintain very low risk and require very low downtime.