The main use cases for Red Hat Enterprise Linux (RHEL) at the bank involve internal applications, as we do a lot of internal applications not exposed to clients.
Red Hat Enterprise Linux for SAP with HA and Update Services 9.0
Amazon Web ServicesExternal reviews
1,117 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Powerful Scripting and Automation Capabilities
What do you like best about the product?
ability to write and run scripts, schedule automatic scripts (cron) and run command line unix commands
What do you dislike about the product?
slight variation with user management and changes/settings
What problems is the product solving and how is that benefiting you?
server communications/server session/login & file transfers
Hybrid cloud platform has simplified internal banking apps while supporting regulated environments
What is our primary use case?
What is most valuable?
From my perspective, the best features of Red Hat Enterprise Linux (RHEL) lie in its ease of use, especially compared to AIX, which has a lot of functionalities requiring extensive learning. It was easy for me to shift from AIX to Red Hat Enterprise Linux (RHEL).
Red Hat Enterprise Linux (RHEL) helps manage our hybrid cloud environment, but being a bank, we are highly regulated internally, so there is limited direct involvement with the cloud environment in Royal Bank cloud, which is Azure.
What needs improvement?
One area I see for improvement in Red Hat Enterprise Linux (RHEL) is in the documentation. I encountered some scarcity when looking for information regarding structure, commands, and administrative tasks.
For how long have I used the solution?
I have dealt with Red Hat Enterprise Linux (RHEL) for around 10 years, even when it was not part of IBM.
What do I think about the scalability of the solution?
My opinion of Red Hat Enterprise Linux (RHEL)'s scalability is that it was very easy.
How are customer service and support?
I would rate Red Hat's customer service or technical support as a 10, as my experience with all IBM products, including Red Hat Enterprise Linux (RHEL), has been very satisfactory all the time.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of Red Hat Enterprise Linux (RHEL) is straightforward compared to AIX, which is more convoluted.
What other advice do I have?
I have experience with platforms like Linux, and I am also working deeply with MongoDB and Node.js, tools that I use constantly every single day.
I am familiar with Red Hat Enterprise Linux (RHEL), and here in RBC, we are a big IBM shop, currently using JBoss and Red Hat Enterprise Linux (RHEL) as part of our environment.
Red Hat Enterprise Linux (RHEL) is used for both cloud-based solutions and on-premises.
From a business value perspective, the business folks do not notice much difference between Red Hat Enterprise Linux (RHEL) and other distributions, as long as their application functions well, they are satisfied.
We utilize two cloud providers for Red Hat Enterprise Linux (RHEL) solutions, mainly Azure and also Amazon. I cannot answer how Red Hat Enterprise Linux (RHEL) was purchased, but I know we have it on both Amazon and Azure.
I would rate Red Hat Enterprise Linux (RHEL) a nine, as I find it satisfactory in various aspects.
Scalable, Secure, and Globally Reachable
What do you like best about the product?
I appreciate the scalability of Red Hat Enterprise Linux across our environment, which allows us a global reach.
What do you dislike about the product?
I find some elements of complexity and skills gap a bit challenging. It would be helpful if there was free training available for everyone.
What problems is the product solving and how is that benefiting you?
I use Red Hat Enterprise Linux for database hosting. It solves our security and resilience issues and offers scalability that provides us with global reach.
Redhat Enterprise Linux has all the bells and whistles one could ask for.
What do you like best about the product?
We use RHEL for it's Enterprise-Grade stability, security and Long Term Support (10+ years).
What do you dislike about the product?
Dislikes for RHEL often center on it's cost, steeper learning curve for desktop/newusers, reliance on specific repos (EPEL), slower desktop performance and community friction.
What problems is the product solving and how is that benefiting you?
RHEL solves core enterprise IT problems by providing a stable, secure, and scalable foundation for hybrid cloud infrastructure, addressing challenges like security threats, operational complexity and skills gaps.
RHEL - Reliable, Secure, and Automation-Ready - Highly Recommended
What do you like best about the product?
I use Red Hat Enterprise Linux for its stable and secure environments, which are vital for automation and CI/CD workflows. I really like how robust the system is, especially during updates and long-running workloads. Built-in tools like SELinux, yum/dnf, and systemd make management smooth, and it integrates well with automation tools like Ansible. SELinux provides strong security by controlling access and enforcing policies. Yum/dnf makes package management seamless and keeps systems up to date. Systemd simplifies service management and the system boot process. Together, all these make Red Hat Enterprise Linux secure, reliable, and easy to maintain.
What do you dislike about the product?
Sometimes the subscription cost could be higher for smaller teams, and occasional updates or patches can introduce compatibility issues. The learning curve for some advanced features like SELinux can also be steep for new users.
What problems is the product solving and how is that benefiting you?
I use Red Hat Enterprise Linux for stable, secure environments. It provides a predictable, secure setup, simplifies patching, package management, and troubleshooting, saving time in QA and DevOps workflows.
Stable, Secure, Yet Pricey with Setup Challenges
What do you like best about the product?
I find Red Hat Enterprise Linux very useful because of its support, long-term support, and stability, which are some of the biggest advantages of using this environment. The support measures like forums, and regular bug fixes help me stay updated with the security standards. I also appreciate its enterprise-grade security, which is often used in high-level industries, and this exposure helps me become familiar with the system.
What do you dislike about the product?
I think the price limits could be improved. Even though it is updated, the newer standards are adopted very slowly and there should be an update every few years to adopt new standards. Also, installing drivers is a multi-step command line process which requires enabling the EPL deposit, installing the tools, and other things. It would be better if it were more of a one-click process because the additional drivers in the UI are secondary here. The partitioning aspect during setup was difficult; the manual tool is complex, which can be challenging for beginners due to the required planning and navigation.
What problems is the product solving and how is that benefiting you?
Red Hat Enterprise Linux helped me tackle the problem of unreliability in server hosting for my AIML projects.
Good Overall, But Room for Improvement
What do you like best about the product?
RHEL provides consistent performance, predictable updates, and long-term support, which makes it ideal for production workloads. The built-in SELinux policies, lifecycle management, and seamless integration with tools like Ansible make system administration much easier and far more secure.
What do you dislike about the product?
What I dislike about Red Hat Enterprise Linux is that some features and repositories require a subscription to access, which can increase costs for smaller teams. Additionally, certain advanced configurations can be complex for beginners, especially when dealing with SELinux or dependency issues.
What problems is the product solving and how is that benefiting you?
Red Hat Enterprise Linux helps us solve the need for a stable, secure, and predictable operating system for production workloads. Its strong SELinux security, consistent patching, and long-term support reduce downtime and vulnerabilities. This gives us a reliable environment to run critical applications with confidence and ensures compliance with enterprise security standards.
Enterprise platform has supported secure consulting services and complex data center operations
What is our primary use case?
My principal focus in using Red Hat Enterprise Linux (RHEL) currently is as an integrator in Linux, where I have many services in consulting, deployment, installation, and troubleshooting in Linux. I have a recovery system, deployment clusters, databases, and work in any environment in data centers. At this moment, I am a senior consultant in the data center in open source.
What is most valuable?
The best features of Red Hat Enterprise Linux (RHEL) depend on the client because the client can decide to use RHEL, not me. The principal thing is the support for the clients because many clients are corporate and have a need for enterprise support. It's the principal focus and is different from using Ubuntu or Debian or any other Linux.
Other good things about Red Hat Enterprise Linux (RHEL) include the focus on system patching, upgrades, and security. The security advisories and authorization are very strong in Red Hat, and that is the principal focus—security.
I manage Red Hat Enterprise Linux (RHEL) by provisioning patching, new deployments, automation, and anything else needed.
I am satisfied with the management experience of Red Hat Enterprise Linux (RHEL) and find it satisfactory for this purpose.
What needs improvement?
I would rate customer service or tech support with Red Hat Enterprise Linux (RHEL) a seven, no more.
I give it a seven because of the time it takes for responding to problems; it takes too long.
For management, it is medium; it is not easy, it is a medium level.
I see a medium ROI with Red Hat Enterprise Linux (RHEL) because it has a high price. OpenShift may provide better ROI, but OpenShift is very high.
The initial setup of Red Hat Enterprise Linux (RHEL) is complex.
On a scale of one to ten, I rate it a five—medium complex.
A very expensive time is needed for deploying clouds with Red Hat Enterprise Linux (RHEL).
It takes a lot of time.
In many cases, Red Hat Enterprise Linux (RHEL) does not help me save time because the principal problem is that in AWS, Red Hat Linux is not the natural Linux for deployment; the default deployment in Amazon is Amazon Linux, not Red Hat Linux.
In many cases, it does not depend on direct Red Hat support for saving time.
My thoughts on the knowledge base with Red Hat Enterprise Linux (RHEL) are that it is good but it does not have it all because I have the medium and plus; it needs more knowledge base.
For how long have I used the solution?
I have been using this for 20 years.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) has high scalability; it is high for horizontal scalability in any environment, and there are many solutions for scalability.
How are customer service and support?
I would rate customer service or tech support with Red Hat Enterprise Linux (RHEL) a seven, no more.
I give it a seven because of the time it takes for responding to problems; it takes too long.
How was the initial setup?
The initial setup of Red Hat Enterprise Linux (RHEL) is complex.
On a scale of one to ten, I rate it a five—medium complex.
What was our ROI?
I see a medium ROI with Red Hat Enterprise Linux (RHEL) because it has a high price. OpenShift may provide better ROI, but OpenShift is very high.
Red Hat Enterprise Linux (RHEL) is less expensive than OpenShift, which is very expensive.
What other advice do I have?
I am a reseller and a partner with Red Hat.
I am involved with Red Hat.
I use Red Hat Enterprise Linux (RHEL) for my labs, so I am a reseller, partner, and user. I would rate this review overall as an eight.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Improved cloud backups and security have transformed how our team builds and manages servers
What is our primary use case?
Red Hat Enterprise Linux (RHEL) is used primarily to build AWS servers. A specific example of how RHEL is used to build AWS servers involves purchasing licenses from third-party vendors like REL and also from AWS. Once an AMI is obtained from the Marketplace, the AMI is customized by injecting all organization standards.
After internal tools have been built on the AMI, that AMI is used to build AWS servers.
How has it helped my organization?
Red Hat Enterprise Linux (RHEL) has positively impacted the organization by helping track everything, such as how many users have access to the server, which is easy to monitor. RHEL also offers better options for downloading repositories easily, and the ability to stripe the EBS volumes has allowed for pulling more IOPS and throughput.
The impact on the team and organization has been significant, as it has helped improve application performance and backup performance. Since AWS backend is used for backups, RHEL striping has proven very useful.
By using RHEL striping, throughput and IOPS have increased, which reduced the backup completion time from fifteen to sixteen hours to just fifteen to sixteen minutes. The main reason is the backend and the striping implemented for EC2 instances.
What is most valuable?
Red Hat Enterprise Linux (RHEL) offers several valuable features, including being secure and standard, and making whatever commands are executed easier to manage. When security and standardization are considered, no other person can access those RHEL servers.
Another good aspect is that whatever is downloaded comes from the repository, and every command is tracked, including the person who entered the command. Tracking on RHEL AMIs and OS standardization is very effective.
Red Hat Enterprise Linux (RHEL) helps mitigate downtime and lower risks by using the Pacemaker role for high availability. The primary and secondary systems are managed by the Pacemaker role, which helps reduce downtime for applications.
What needs improvement?
Red Hat Enterprise Linux (RHEL) could be improved by including a better app stream module experience or simply phasing out modules in favor of straightforward version repos. Red Hat could also integrate more common tools directly or integrate EPEL more seamlessly. Additionally, enabling AI-based operational tuning for kernel parameters, file system parameters, and network stack optimization could enhance the experience.
Regarding needed improvements, simplifying the subscription and licensing would help reduce complexity in subscription management. Clear visibility of consumption and unused subscriptions and compliance is also important.
For how long have I used the solution?
Seven years of experience have been accumulated in the current field.
What do I think about the stability of the solution?
Red Hat Enterprise Linux (RHEL) is stable.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) offers great scalability and supports very large memory.
How are customer service and support?
The customer support received is good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Red Hat Enterprise Linux (RHEL) has been the only solution used, and no switch from any other solution has occurred.
In comparing the business value of RHEL to other Linux distributions, no other Linux distributions have been used; only Red Hat Enterprise Linux (RHEL) has been utilized.
How was the initial setup?
Red Hat Enterprise Linux (RHEL) systems are managed with a dedicated cloud support team that handles provisioning and monthly patching. Additionally, focus is placed on security hardening and optimizing it with cloud-init, instance tuning, and subscription activation.
What about the implementation team?
Image Builder has been used, but the AMIs are not built personally. A dedicated support team handles the building of the AMIs.
What was our ROI?
A return on investment has been seen, as it has saved a tremendous amount of time.
Red Hat Enterprise Linux (RHEL) helps save time; for example, the Pacemaker role facilitates faster task completion, and it optimizes backup processes.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, setup cost, and licensing, the pricing is good; however, licensing is a bit confusing.
What other advice do I have?
My advice for others looking into using Red Hat Enterprise Linux (RHEL) is to be aware that subscriptions can be challenging to manage. When a server reboots, the subscription goes to open, which can lead to others consuming the subscription, creating a challenge regarding the subscription and licensing part.
Security requirements were a significant consideration in choosing RHEL in the cloud because it is not open source and is highly secure.
Red Hat Enterprise Linux (RHEL) is assessed as having a better knowledge base offered through its tuning capabilities. By better tuning, the documentation is referred to, which helps in day-to-day work.
Red Hat Enterprise Linux (RHEL) entitlement management can be confusing, as converting systems between subscription modes is not straightforward.
I would rate this review a nine out of ten.
Has strengthened security through granular access control and supported smooth workload upgrades
What is our primary use case?
My main use cases for Red Hat Enterprise Linux (RHEL) are primarily our websites and applications that run on top of Red Hat Enterprise Linux (RHEL) operating system platform.
What is most valuable?
What I appreciate most about Red Hat Enterprise Linux (RHEL) is the SELinux policy that has been introduced; I believe that is truly good security, although it was difficult initially to become accustomed to it. In the modern world, you don't want every user to have accessible permissions. It gives you a granular level of control over each and every file and directory, just as ACLs used to provide in the past. By using SELinux policy, you can actually secure these accesses and establish a strong security posture.
The main business problem that Red Hat Enterprise Linux (RHEL) helped us solve is automation of tasks and scalability of the business. Red Hat Enterprise Linux (RHEL) has helped reduce downtime because in modern infrastructure, you do not face out of memory issues. Red Hat Enterprise Linux (RHEL) has affected the downtime by reducing it to a minimal level; the reboots are very speedy.
What needs improvement?
I think the support for Red Hat Enterprise Linux (RHEL) can be much better; when it comes to something such as SUSE Linux, I feel those providers are doing a much better job in terms of support than what Red Hat provides. One area where Red Hat Enterprise Linux (RHEL) stability could be improved is with Ksplice; Ksplice is used for online patching. The problem I have seen with it is that it applies patches at the user level, but not at the kernel level. That was a problem in terms of our security architecture because it doesn't recognize that the patch has been installed. I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.
For how long have I used the solution?
I have been using Red Hat Enterprise Linux (RHEL) for the past three years.
What do I think about the stability of the solution?
My assessment of Red Hat Enterprise Linux (RHEL)'s stability and reliability once it is deployed in production and maintained is that it's straightforward, but there's a huge functionality and learning curve. We started using it and actually understood the reason why Red Hat has implemented it and the level of granularity in terms of security posture that it provides. We understood that it's doing a really good job.
I assess the stability, availability, and reliability of Red Hat Enterprise Linux (RHEL) as pretty stable and very reliable.
Red Hat Enterprise Linux (RHEL) has crashed or failed here and there, but there were some settings that needed to be changed. We make sure that we match those parameters.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux (RHEL) scales to my needs pretty much up-to-date.
How are customer service and support?
The support from a competitor I've used is Oracle. My experience with Oracle support is that Oracle on-premises support, what it provides with Oracle Enterprise Linux, performs very well, and many of our customers believe that something from Oracle is more secure. When they compare Oracle with Red Hat, it has a much better support system and a much more secure posture than what we get.
I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.
How would you rate customer service and support?
Neutral
How was the initial setup?
My experience with the deployment of Red Hat Enterprise Linux (RHEL) has been smooth because back then we were on-premises and all our information used to be on-premises, rather than run them completely as we do now.
Which other solutions did I evaluate?
I have evaluated a couple of operating systems including Ubuntu, Oracle Linux, SUSE, and then came to Red Hat Enterprise Linux (RHEL) because Red Hat is considered the pioneer.
I have considered replacing Red Hat Enterprise Linux (RHEL) with another solution; specifically Oracle Linux.
If I were to switch, I would consider factors such as security and support.
What other advice do I have?
We are currently considering using the Ansible Automation Platform for configuration and patching; we are using a manual approach and a little bit of Ansible here and there, but not fully deployed an Ansible Automation Platform or command line approach. But today I had the experience in the lab with the Ansible Automation Platform. That looks truly promising. I hope to get a chance to do a proof of concept and show my company that this is the product we can use in the future.
I have used the in-place upgrades to migrate machines to a newer release of Red Hat Enterprise Linux (RHEL); I used LEAP which has been designed to upgrade Linux 7 to Linux 8, and it was smooth. I think that was truly good work, especially because it supports you in situations where you do patching.
The upgrade process for Red Hat Enterprise Linux (RHEL) is straightforward and we didn't have any problems.
We are planning on upgrading from Red Hat Enterprise Linux (RHEL) 6 and 7 to 8, though we do have some legacy applications that would not support it. However, other systems which are web servers or Apache, we are trying to upgrade them.
I haven't found any limitations in Red Hat Enterprise Linux (RHEL)'s security.
My assessment of the documentation offered by Red Hat Enterprise Linux (RHEL) is that Red Hat's documentation is top notch. You cannot compare that with SUSE.
My specific goals that led me to choose Red Hat Enterprise Linux (RHEL) include the security posture.
Current, I am using the standard lifecycle support add-on for Red Hat Enterprise Linux (RHEL); I think we are still sticking with the standard and haven't upgraded yet.
The advice I would give to a team considering Red Hat Enterprise Linux (RHEL) is that one of the new features that it has is promising, and everybody promises great things with new features. My overall rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.
showing 1 - 10