We use Red Hat Enterprise Linux (RHEL) as the operating system on our systems. Everything is built on it.

Red Hat Enterprise Linux for SAP with HA and Update Services 9.2
Amazon Web Services | v20250520Linux/Unix, Red Hat Enterprise Linux 9.2 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
RHEL provides a comprehensive set of software with excellent performance and world-class support.
- Mark review as helpful
Built-in security features streamline compliance and vulnerability management
What is our primary use case?
What is most valuable?
Red Hat Enterprise Linux (RHEL) helps us solve pain points. It keeps us easily compliant from my perspective with security compliance and streamlines everything in a multi-system environment.
The OpenSCAP vulnerability scanner is what I appreciate most about RHEL. We benefit from that tool specifically due to the fact that RHEL is under the recommended operating system mandate. Through that, they have their security requirements, and RHEL's OpenSCAP vulnerability scanner is a really good automatic scanner to scan for cybersecurity vulnerabilities in our system. The way it produces reports is really nice and it's better than the old vulnerability scanner that our system used.
My assessment of RHEL's built-in security features for simplifying risk reduction and maintaining compliance centers around OpenSCAP. It's better than any other tool I've seen. I've seen two or three other ones. It is really streamlined and nice. It feels professional when using the product.
When it comes to managing our Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, our software team handles it efficiently. We maintain a close connection with our Red Hat account managers and representatives who are extremely helpful with any Linux or Red Hat level issues.
RHEL and the Linux architecture system are easier to work with for our program maintenance and updates. Given our 30-year-old product, making current updates would be almost impossible on Solaris. The maintenance and updates for today's requirements can really only be executed with a Linux architecture, making it essential for our operations.
What needs improvement?
One of our current issues is that Red Hat Enterprise Linux (RHEL) 10 discontinued support for X11 and started support for Wayland. All of our machines run on X11 window manager, which creates a huge issue in our transition. Red Hat is working with us on this matter.
There's a high barrier to entry for getting into Ansible and automating things on a system level from my perspective. When we tried it last week, we found it challenging to automate things using Ansible.
For how long have I used the solution?
I have been at my company for two years now. The entire time has been heavily involved with using Red Hat Enterprise Linux (RHEL).
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) has been able to scale to meet the needs of my company and its growth. I credit that to the Linux architecture that can scale to our requirements. We have a unique configuration. That said, my company primarily runs on Linux, and it has scaled very effectively.
How are customer service and support?
The customer service is amazing. The accessibility of the support team and their responsiveness is consistently impressive.
I would rate the customer service and technical support as nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We were previously on Solaris before switching our in-house systems to Red Hat Enterprise Linux (RHEL) 7. We actually skipped RHEL 8 and are transitioning from RHEL 7 to RHEL 9. We are not yet on RHEL 10.
How was the initial setup?
We have had issues with deploying Red Hat Enterprise Linux. I'm actually really focused in on one of our current issues where Red Hat Enterprise Linux 10 discontinued support for X11. All of our machines run on X11 Window Manager. And that's a huge issue that we're transitioning. It totally breaks everything we have, and we're working with Red Hat to figure that out. It's nice they're working with us. Yeah. However, it is a big problem during our transition.
What was our ROI?
Regarding the security features and vulnerability scanner with Red Hat Enterprise Linux (RHEL), we have not yet seen a return on investment as we haven't proposed it to the organization. We are currently working on scanning and fixing vulnerabilities. We are confident the the organization will be pleased with our improved compliance using the RHEL scanner, which should lead to a return on investment.
What's my experience with pricing, setup cost, and licensing?
I don't have much insight into the pricing, setup costs, and licensing. I know we are licensed and have maintained a good relationship with our account manager.
Which other solutions did I evaluate?
While using Red Hat Enterprise Linux (RHEL) as our operating system, we do consider other solutions for specific features. We have alternatives available for various tools, however, we prefer to default to Red Hat since it's the organization-wide preferred operating system. In the past two years, we have been increasingly transitioning to RHEL tools.
What other advice do I have?
On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) a nine.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Review of RHEL
Streamlined use leads to significant time savings and reliability over years
What is our primary use case?
My main use cases for Red Hat Enterprise Linux (RHEL) are everything from research computing to hosting websites. We've run a gamut of different things with RHEL.
I used to use it a lot for a healthcare company and healthcare software. Now predominantly, it's research that is very statistically intensive. So anything where we have to do data computations, data rates, we need to synthesize data, aggregating it from instruments all over the world or within the lab itself. We take all of that, and we also use it to produce applications for people, whether it's just interacting with it via a website or an actual homegrown application where they can go through, search, look at the data, and do their own data manipulation.
What is most valuable?
My favorite feature of Red Hat Enterprise Linux (RHEL) is the ease of use; it is streamlined, making it very intuitive to do things.
The ease of use of Red Hat Enterprise Linux (RHEL) reduces time for my company. It reduces the time to do things, allowing us to do very complex tasks in a very short period, since it is very straightforward and makes it easier to get things done.
It has been around for so long, and it's such a standardized platform that the knowledge base from the employee perspective is usually pretty high compared to other enterprise Linux distributions. Therefore, the overall time savings with RHEL is huge.
Our upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) involve adhering to a rule: once a version reaches end-of-life, we do not enter the extended life cycle. We plan that out ahead, ensuring that all of our systems get migrated and updated about a year before the end of life of any version. Some systems get migrated to the latest version while others remain and just get updated to whatever is current. It depends on the application and its external dependencies, but it's just a solid plan we follow.
Red Hat Enterprise Linux (RHEL) has helped us mitigate downtime and lower risks, as we've utilized virtual machines and process load balancing to minimize issues. While we've had downtime with any systems, there tends to be a lot less with RHEL. We have had some systems running just for fun for three years without any downtime, which reflects their stability. I would say that RHEL has reduced risks by at least 80% compared to open-source distributions based on experiences in recent years.
What needs improvement?
To improve Red Hat Enterprise Linux (RHEL), the biggest thing is the availability of some tools that unfortunately have to be paid for. While I understand that you have to pay for resources, it would be nice to have a centralized location where you can easily find those tools.
For how long have I used the solution?
I have been using Red Hat Enterprise Linux (RHEL) for close to 20 years.
What do I think about the stability of the solution?
Regarding the stability and reliability of Red Hat Enterprise Linux (RHEL), we have systems that we've kept running for years without any downtime, so I have never had a problem with stability or reliability.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) has scaled right along with our growing company needs; the only exceptions to that are with supercomputers, but that's a whole different animal.
How are customer service and support?
My experience with customer service and support from Red Hat Enterprise Linux (RHEL) has been good so far. I haven't needed to use it often, which goes back to its reliability. Whenever I've had issues reaching out, they've responded quickly with appropriate information.
Which solution did I use previously and why did I switch?
We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others, however, we keep going back to RHEL due to its reliability and available resources.
How was the initial setup?
The deployment experience with Red Hat Enterprise Linux (RHEL) has been very easy; we've been doing it for years. The automation that they've built over the years to do the deployments just makes it easier and easier every year, transitioning from kickstarts to using things OpenShift. I'm excited to see how this Image Builder works with that, too, so it has continuously improved.
What was our ROI?
The biggest return on investment for me from using Red Hat Enterprise Linux (RHEL) is just overall time saved.
Which other solutions did I evaluate?
We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others. We keep going back to RHEL due to its reliability and available resources.
What other advice do I have?
I would rate Red Hat Enterprise Linux (RHEL) overall at least a solid ten out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
I use it daily, I convinced my buisness to use it and recommend it constantly.
Red Hat Enterprise Linux Rocks!
Consistently reliable platform mitigates downtime and lowers risks
What is our primary use case?
My main use cases for Red Hat Enterprise Linux (RHEL) are mostly as our platform, control plane, and for VMs.
How has it helped my organization?
Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risks. Anyone coming from security will tell you that more patches in a timely manner will save you a lot of time.
What is most valuable?
What I appreciate the most about Red Hat Enterprise Linux (RHEL) is the DNF feature. DNF benefits our company since it's my personal preference; that package manager makes sense to me. I've also used it longer than other ones, which contributes to my familiarity.
Package managers in general are a core component of our operations, keeping our platform clean and running smoothly, and it's essential.
Insights is nice since I get information on my background and security matters, and it's been helpful to have it there as well.
What needs improvement?
Red Hat Enterprise Linux (RHEL) can be improved regarding security-side integrations that can be tightened with the releasing of images compliant with CIS controls or DISA STIGs, so they're built in and not an extra step.
To make Red Hat Enterprise Linux (RHEL) a ten out of ten, the best Linux OS solution in the market, the only immediate change that comes to mind is security-related; releasing images available at different security levels would be helpful. If something is locked down to DISA STIG Level two or whatever environment, having that as a baked image to pull down and deploy would save a lot of time for many companies since building that pipeline is difficult and time-consuming.
There's also a limited number of those they'll have to deal with for Red Hat, so it's a lot of work. If they're doing those images for each level for STIG and then CIS, there will be a finite number to go through, and if anyone else needs to tailor them beyond that, then that's on them. It should be pretty small changes; it's kind of locked in.
For how long have I used the solution?
I've been using Red Hat Enterprise Linux (RHEL) for seven months.
What do I think about the stability of the solution?
My thoughts on the stability and reliability of the Red Hat Enterprise Linux (RHEL) platform are that it has been excellent. When I consider reliability problems we have had and how much relates to RHEL, most of the issues aren't Red Hat-related; something else fails, and the Red Hat side has been consistently reliable.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) scales with the growing needs of my company very effectively. My specific team is not on a huge scale right now, however, it's growing quickly, and we haven't had any issues with RHEL so far.
How are customer service and support?
My experience with customer service and technical support for Red Hat Enterprise Linux (RHEL) so far has been really good. I haven't encountered just a create-ticket-get-a-response type of interaction yet since we still have a consultancy going on for different pieces identity management and AAP. That remains to be seen in terms of what it will be when we don't have somebody readily available. So far, the response times and helpful responses have been good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I've used other solutions. The main difference between Red Hat Enterprise Linux (RHEL) and the other Linux solutions we use is a level of comfort. I sleep better knowing I have official support and can call someone, or there's probably a consultant or somebody on Red Hat's side ready to help me figure things out. If I'm running a Debian system, I'm really relying on the community, which can take time, and if I'm running something at work on that, then that can hurt.
Regarding usability, I've gravitated towards RPM-based Linux systems in general as I find them more intuitive.
How was the initial setup?
The deployment is super straightforward. We do some environmental stuff, and that gets a little bit trickier based on the core running on top of it.
What about the implementation team?
What was our ROI?
From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the number of things tied together in a somewhat neat package. There's something to be said for setting up Satellite or the other pieces of the infrastructure, AAP, or whatever it is I'm going to be using, however, all the tie-ins are there, and once I've done some initial footwork, having those things work in tandem and reliably with support on hand when they don't is really helpful.
Which other solutions did I evaluate?
We consider different solutions while using Red Hat Enterprise Linux (RHEL). Actually, we use a few different Linux OS solutions. There's some Canonical in our environment through VMs, and there are tools particularly suited for deploying on bare metal that we use. So, we have a bit of a mixed environment within Linux.
What other advice do I have?
My upgrade or migration plans to stay current depend on where it's at or the platform team; our stuff is going to be separate, and I'm unsure exactly what the cadence is for release and into the patching cycle. That'll be a pretty quick turnaround. We have situations where it needs to stay on older systems since the team using it needs that to prove out or test whatever they're working on.
On a scale from one to ten, I rate Red Hat Enterprise Linux (RHEL) a nine out of ten.