Red Hat Enterprise Linux (RHEL) Reviews

I use Red Hat Enterprise Linux to control my Docker systems and build and run containers on them. I also use it for a tokenization project I'm working on.

Red Hat Enterprise Linux (RHEL) has improved the availability and security of our systems. The knowledge base, Wiki forums, and other resources are very helpful in simplifying my daily operations. We realized the benefits immediately after deployment. 

The most valuable features of Red Hat Enterprise Linux are the availability, file system performance, and overall system availability. The kernel is more secure than my previous operating systems, such as Windows.  Red Hat's knowledge base is helpful. I consult it several times in my daily work. I can ask questions on the forums and get help in my daily operations.

Using Red Hat Enterprise Linux's image builder is easy. I can use GitAI to pull any image I want to build on my system and reach into it using Red Hat. I use Convert2RHEL to publish my work on tokenization. I'm publishing more than 70 prints on my system daily, and saving this file. It's easy to use.

There are performance issues with the response time when accessing the console, but I'm unsure if that's Red Hat Enterprise Linux's fault or if it's due to the lack of CPU or memory on our machines. The enterprise interface could be improved. I can only use the keyboard to transfer files from one system to another. I want to use my mouse on the interface, not just scroll up and down. I would also like my logs archived as an RAR and sent to me. 

I have been using Red Hat Enterprise Linux for more than five years.

Stability is critical to us. Red Hat Enterprise Linux ensures our machine's availability and reduces the need for frequent restarts.

I have not contacted customer or technical support myself. Our infrastructure team handles any contacts with Red Hat support.

Positive

I have used Ubuntu before. Red Hat has a more robust knowledge base, and finding solutions to any problem is easier.

The infrastructure team handled the initial setup. I'm a software engineer working on my applications. The infrastructure team builds the machine, and I only use it. It was relatively easy, depending on the complexity of the deployment configuration. After deployment, we have maintenance on our machine if there are new patches to deploy. I have three machines, and each one is identical, with the same containers, so I don't need to do maintenance on our machines more than once monthly. 

It is important to use the knowledge base and familiarize oneself with key commands to gain more about Linux and ease its usage.

I'm using the Red Hat Platform with Open Stack and an RHEL product for storage. The use case is performance IOPS for Ceph Storage, which depends on a bare-metal RHEL server. 

For my security customer, we get greater than 90 percent uptime. RHEL helped us achieve security certification. It helped my end-user pass their security assessment. RHEL's built-in security features scan the third-party layer in the OpenStack and RHEL platform to assess the SSH and firewall security or patch updates from the RHEL platform and reset OpenStack. Security is the number one priority for my end user. They want to prevent hacker access from the outside. 

RHEL supports the hybrid cloud strategy. The goal of using a bare metal server has been to improve availability and database performance. The OpenStack platform uses network capability to improve database performance.

RHEL improves database and application performance for my end users. The application can collect regional and national data for my end user, a strategic customer in Indonesia.

I am confident in the managed services RHEL provides in terms of the OpenStack, Ceph Storage, and OpenShift container-based products. If there are any problems with the RHEL platform, Open Stack, Ceph Storage, etc., I can raise the issue to RHEL global support. 

For the past twenty or thirty years, Red Hat has reengineered its product from bare-metal on-prem to the cloud environment. Migrating an RHEL system from bare metal to cloud is somewhat difficult. They could add a fast boot. 

We deployed one side of RHEL in 2023, and we'll deploy the other side in 2025.

When I deploy RHEL for the first time, I try to learn about the performance and tune the performance. 

Scalability isn't an issue. Our customers haven't reported any performance problems from scaling up.

I rate Red Hat support eight out of 10. I have used Red Hat support since 2023. They escalate the ticket based on severity, and if they can't resolve the issue within the maintenance window, they will pass me to another engineer. 

Positive

We previously worked with Oracle Linux. My customer has two divisions. The network decision is focused on accounting database performance, while the IT division uses Oracle Linux. On the network side, the customer uses RHEL products like OpenStack, Ceph Storage, and OpenShift. 

My end user wanted to upgrade from RHEL OpenStack 16.1 to the latest 17.1.3 in April 2024. We also upgraded Ceph Storage and OpenShift. Now, my customer wants a testbed before upgrading to the RHEL version in live production. If there are problems, we open a ticket with global support and or two people will join our remote call. We have it deployed in Jakarta and plan to deploy it to Bandung.

I rate Red Hat Enterprise Linux eight out of 10. I recommend all the Red Hat products, including OpenShift and Ceph Storage. OpenShift Container is a mature product for RHEL portal customers.

The main use case is generating golden images. All the deployments of operating systems and virtual machines on the servers are based on the golden image. The developers and providers can run all the applications on top of those.

Whenever we need to remediate any vulnerabilities, patches are available. These patches are not only for current exploits but also for back-porting for bug fixes and security fixes. These patches are available from the most recent versions to the specific version that we are using.

Red Hat Enterprise Linux has enabled us to centralize development. We have a golden image of the operating system. That golden image sets the standard for all the security policies that we are applying to it. For example, the partition scheme and the best practices that we apply to the golden image are the starting point for all the developers to start working with all the applications and also executing appliances or applications from providers.

We are using Red Hat Enterprise Linux with Podman for containerization projects. Red Hat offers what is called UBI or Universal Base Image. That image is already configured to be secure and have good performance. To start working with containers, we just have to pull UBI as a base for our images and start working on those. It has impacted our containerization project because instead of using Docker, we can use Podman. There is a common container image that is used by the majority of the customers, but I forgot the name of that one. Instead of using that, which is like a very minimal image, we are using UBI because it is already secure. It has the majority of the benefits of our Red Hat Enterprise Linux image but in a container image.

There is portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. That is a very good option to have because you do not have to worry about the underlying system. You just have to worry about your application and have the application running on top of your image based on UBI. It is going to be so easy to have the application running either on a machine with Podman or have the same application running just on top of OpenShift. It is so easy to move a container-based application that can be executed on top of Red Hat Enterprise Linux with Podman or on top of OpenShift. 

Security, packages, and updates are valuable. There is also the possibility to do unattended installations. This way you can define how you want the installation to behave and be configured whenever you do the deployment.

One of the best features is having a tool called OSCAP, which is a tool that is going to allow us to apply security profiles to the golden image. This way, all the security features or policies can be applied in real time. This way, we can follow all the policies that are defined by our security teams.

There are not a lot of areas to improve because the majority of the time, Red Hat is constantly improving it. The only area would be in regards to being capable of running on other architectures like ARM. They are about to release a new version that is available to be executed on ARM architecture.

We have been using Red Hat Enterprise Linux for about a year.

It is very stable.

It is scalable. We have plans to increase its usage.

It used to be better. It is still good as long as you can get in touch with a level 3 support engineer. If you have a trained engineer who helps you with what you need and who understands how to ask for specific details of what you need, you should be good. But, unfortunately, if you start with a simple detail of what you are experiencing and what kind of help you need, you will receive the same response. For example, you are pointed to a knowledge base article, and that is it. The support engineer is supposed to help you with your issue or request, but unfortunately, that is not happening anymore. It used to, but I understand.

We are looking for a support engineer to go all the way. The only way for you to contact support is via the support case system or page. After that, you interact through the ticket or email. You do not have a chance to have a call. If we have escalated a case, it is usually better if you have a person for a proper understanding and proper advice on what you have to do and how to resolve the issue. It could be that you need a new product, subscription, or service, but you do not know that.

Neutral

When I got into the company, they were already using Red Hat Enterprise Linux, but back in the day, I used to have HP-UX. That was a very ancient system. It was Unix-based. It was a proprietary solution. HP-UX was a platform licensed based on the old Unix code that was tightly integrated into hardware built only by Hewlett-Packard. You could not run HP-UX in any other place. You could only run it on hardware created by Hewlett-Packard. The intention with that was to run only on the Itanium architecture, whereas Red Hat Enterprise Linux can run on x86 architecture. It is also open-source.

We have it on-premises. It is in different locations. We are following a strategy to publish the images of the operating system. This way, multiple teams can grab the images and have their own procedures to deploy within each separate environment. We have multiple teams working on developments and they need a base image to start working on all the development stuff. Because they are all independent teams, they have access to a single source of image. This way, they can start working on further customizations and whatever they need.

We implement it in-house.

The ROI is in terms of the time that I have to invest in doing customizations, applying security policies, and fixing the supply to the system, wherever I need those.

The reason for going for Red Hat Enterprise Linux is to improve the time to market. It is so easy to just generate a new image. We can configure it with all the security features and all the libraries and packages we need. We can also configure it with the ones requested by developers. We can do all of that. It is so much easier than what we can do with Windows, for example.

It is very straightforward. We do not have to think much about having to get all the subscriptions related to the Red Hat Enterprise Linux fleet that we have because all the subscriptions came in pairs of CPUs or even for an entire bare-metal server. That way you can partition your bare-metal server into multiple virtual machines, and then you are covered. As long as your bare-metal server is covered, you can roll out any number of virtual machines on top of it. It is very easy to get subscriptions for your bare-metal server, and you can utilize whatever you want.

We evaluated operating systems or Linux distributions created by the community or run by the community only. We evaluated them mainly because of costs.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that they would not have the same team supporting all the operations and all the critical features and patches that they receive with Red Hat Enterprise Linux. They can go with one of the clones, but unfortunately, at the end of the day, the clones are going to deviate from Red Hat Enterprise Linux. With Red Hat Enterprise Linux, you can also create support cases to receive back-ported bug fixes and security fixes, and you get very cool features such as Insights, Satellite, or system roles provided along with Ansible. 

We are currently not using Red Hat Insights but that is an awesome tool.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten. It is an enterprise Linux distribution. It was one of the first distributions to focus on the enterprise. There are others, but Red Hat is the main contributor to the Linux ecosystem. Because of that, it is so stable. It has proper support. It also provides the Linux ecosystem with new features and enhancements.

I use the solution to manage Atlassian applications. In our company, we initially deployed Atlassian applications on Red Hat Enterprise Linux (RHEL). For most of the products my company uses, we create Red Hat Enterprise Linux (RHEL)-based servers because we have Red Hat Satellite, so we just bring them up and make them supportive for us.

The most valuable benefit of the product for my organization revolves around standardization, which is why we have all the same types of machines and operating systems. It makes it very easy and familiar across the board. The tool is also very reliable.

My company does have a hybrid cloud environment. Running Red Hat Enterprise Linux (RHEL) as the foundation for the hybrid cloud deployment strangely impacted our operations. I think that when my company moved off from the tool's on-premises version for certain applications, we had to leave Red Hat Enterprise Linux (RHEL). Everything in my company is based on whatever AWS provides, specifically when Linux is on AWS, and I guess it negatively affected my company.

Red Hat Enterprise Linux (RHEL) has helped my company centralize developments because we know what we are going to use in the product, and so we don't have to make any decisions. Owing to the aforementioned area, I would say it offers a good standard.

In terms of the tool's built-in security features when it comes to risk reduction, business continuity, and maintaining compliance, I would say it is very easy to patch, which helps our company to keep it up to date and avoid all downfalls.

Speaking about the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that we don't tend to move that much with applications. The tool has helped to weave a path for an upgrade while creating a new application server, after which one can transfer it over. Considering the aforementioned details, the tool is portable. In short, whenever I try to use the product's portability feature, it does work.

The most valuable feature of the solution is that the upgrade in the patching area is really easy.

I have been using Red Hat Enterprise Linux (RHEL) for ten years.

It is a stable solution.

It is a scalable solution since it is easy to make changes in the tool.

If the product is deployed on an on-premises model, it will be deployed on Red Hat Enterprise Linux (RHEL) system.

I haven't had a reason to use the support services of the product for a long time. I rate the technical support a ten out of ten.

Positive

In the past, my company used CentOS for a while. There were some other products which were also used in my company. My company started to use Red Hat Enterprise Linux (RHEL) as it provided standardization, and we required something nice and uniform in nature.

The product was already up and running when I joined the organization.

The solution is deployed on an on-premises model. If my company opts to have the product deployed on cloud, then we would opt for the cloud services offered by AWS.

I am sure my company did not seek help from many integrators, resellers, or consultants to deploy the product.

The biggest ROI I experienced using the product stemmed from the fact that it was really fast to deploy right from the beginning when we were building our company's new systems. The product works fine.

I would recommend Red Hat Enterprise Linux (RHEL)to a colleague who is looking at open-source cloud-based operating systems for Linux since it offers Red Hat Satellite, so everything is just so encapsulated and there in the tool.

I can't speak of whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape since I don't know the cost.

I rate the tool a ten out of ten.

When we are looking for Linux servers or developers need Linux, we have standardized around Red Hat Enterprise Linux. We do not use Ubuntu or any random flavors of the day. If it is a Linux deployment, it is Red Hat.

It helps with standardization. If someone comes to us and requests a Linux server, we have one product offering. We have a couple of different flavors of it, but people know what they are getting from us. The consistency, reproducibility, and standardization of it have been fantastic.

We are using Red Hat Enterprise Linux on-prem and on the cloud. We have it in Azure, VMware, and on-prem. We have it on bare metal. It is all over the place. Our operations are simpler, more efficient, and easier to handle. Our Linux team now supports one OS rather than a whole bunch of flavors that everyone has brought in. It has just made things more efficient and simplified.

Red Hat Enterprise Linux has enabled us to centralize development. Those developers are now developing on Red Hat Enterprise Linux. Previously, we had people who were developing on Ubuntu and trying to push Ubuntu to production, but we did not necessarily support it. Red Hat Enterprise Linux gave us a clear path to production. Our developers also get an easier experience. They know which OS to use and what they are using from day to day. There is less confusion for developers.

We are using Red Hat Enterprise Linux for containerization projects. It has helped with simplification. We do not have to create too many of our own custom container definitions and do our own thing. We use minimal images and whatever is provided is supported under our subscription. It simplifies things and puts guidelines around things.

Red Hat Enterprise Linux's built-in security features are good when it comes to risk reduction, business continuity, and maintaining compliance. We use Red Hat Satellite to manage our Linux. That makes it all very simple. There is a feature called OpenSCAP. We use it for security scanning. All the features that they provide on top of the base OS make it very easy to manage.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. We know we can rely on that middle layer. We can start with the container and then build on top of that. Having a solid and standard foundation makes it all easy to do.

The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them.

It is constantly improving. It is important to continue to improve. That is another reason I like it. They are using newer kernels, which gives us access to newer hardware. They are already doing that. I cannot pretend to tell them what to do better. They can just keep on doing what they are doing.

Personally, I have been using it for about 12 years. I have only been with my company for about four months, but I know they also have been using it for years.

It is stable.

It is scalable. They define scalability. I am a basic user. I just deploy more VMs if I need to. It is easy to do. Its scalability is great.

They are great. I would rate them a ten out of ten. A big selling point is that when you submit a support ticket, you know you are reaching out to experts. That is great, and that is one of the primary reasons we went with Red Hat.

Positive

In my company, they were using AWX for automation, and we moved them to AAP. For Linux, I was a part of a project to migrate some of the other operating systems over to Red Hat Enterprise Linux. I am on the tail end of the move or standardization to Red Hat Enterprise Linux.

There were a lot of Ubuntu operating systems in the environment, but they had challenges standardizing around it. There were different versions. There was also CentOS, but it was old CentOS. They are naturally moving that to Red Hat Enterprise Linux.

The support and the standardization around it were the main reasons for going for Red Hat Enterprise Linux. CentOS is more of a community thing now, whereas we can call Red Hat and they help us with everything. The support and the enterprise features we needed pointed at Red Hat Enterprise Linux rather than CentOS. It is a better choice for production.

We deploy them from AAP and then we deploy them into VMware. We deploy them into Azure, which is our main provider. We do that all orchestrated through Ansible and Satellite.

We have outsourced support. TCS is a general contractor, but for Red Hat deployments, we generally go with Red Hat Consulting. We just finished a consulting engagement with them for that. I know they have used them in the past prior to me being here. We generally just use Red Hat Consulting.

We have standardization. I know what I am walking into every day. I know there is support behind it. There is the support of Red Hat and the community behind it. I feel confident using Red Hat Enterprise Linux. I might use other Linux operating systems at home, but a lot of the time, there is no documentation for them. There might be three guys in a forum from ten years ago who may have talked about my problem. With Red Hat Enterprise Linux, when I am going to work, I know what I am walking into. I can feel safe and assured using something industry standard that works, and I can get help with it very easily. It makes life a lot easier.

Our total cost of ownership across our enterprise landscape has gone up because we were using a lot of mixed and free open-source solutions. However, there was an extra cost of operations and extra cost of hiring for specialized skills and things like that. With the Red Hat portfolio, I feel that we spend more on subscriptions, and we save in terms of efficiency and operations. I feel that we spent some money to save money on the backend, and I hope that is how it ended up.

I do node counts for the Red Hat Enterprise Linux system. I am gathering data for our decision-makers about how many nodes we need and how many things we need. Once or twice a year, they ask us to true up and find out how many nodes we are using and what the actual consumption is. I then report that, and then the account team usually works on the money part of it. I just work on the count.

We use Red Hat Insights a little bit. I am more of an Ansible guy, and we use Red Hat Insights for our licensing and a few other things. We have not been using Red Hat Insights as much as we wanted to. I know that on the Linux side, they are using it a lot for license count, monitoring, and other things.

I feel we are underutilizing Red Hat Insights. Our account executive has shown how it works and where it is, but we have not committed to it yet. That is coming soon. As we gain more Red Hat products and standardize more, we will have to rely on a single pane like that, so we will be using it more. I know that Red Hat Insights provides vulnerability alerts and targeted guidance, but we are not utilizing it right now.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to go for whatever they find to be the best. My standard for an enterprise solution is Red Hat Enterprise Linux. It works very well, but they have to make sure that it fits their use case. Fortunately, Red Hat Enterprise Linux fits most use cases. They might end up there, but if there are licensing or cost restrictions, there are other free options, such as CentOS. The ecosystem of Red Hat Enterprise Linux is healthy, so I would recommend it, but if they want to use something else, they need to come up with all the standards around that.

I would rate Red Hat Enterprise Linux a ten out of ten. It is my preferred enterprise operating system. Everywhere I go, they are using it. It has been great. There are no complaints.

We are currently using Red Hat Enterprise Linux's versions 6, 7, and 8. We run the OS both on-prem and in the cloud.

We use Red Hat Enterprise Linux for web applications, containers, Kubernetes, and simple scripting servers. The scripting servers are used to run scripts on run drops and so on. However, the biggest use cases are containers and web app workloads.

The cloud providers are AWS and Alibaba.

Red Hat helps our organization avoid cloud vendor lock-in because we can run Kubernetes and a few different workloads directly on Red Hat across different cloud providers. Since Red Hat is an operating system, we can migrate our workloads to any cloud provider that supports Red Hat.

Avoiding vendor lock-in and being able to move workflows between cloud providers has saved us hundreds of thousands of dollars per year.

Red Hat Enterprise Linux is easy to recover, especially from a backup. I believe this is because of its resilience. If I use an instance, I can go to my backups and restore it without much trouble. I was going to compare it to Windows for a moment, where there might be some additional steps required to clean things up after recovery. However, I haven't had many issues where I needed to do any cleanup afterward.

It is easy to move workloads between the cloud and our data center using Red Hat Enterprise Linux. The ease of migration depends on the cloud provider and what they allow us to do. However, for the most part, replication-based migration between cloud providers or on-premises works well. 

Linux is good for hardening the operating system. Logical volumes allow us to dynamically expand volumes, which is valuable from an operational perspective. This is especially true in cloud environments, where we pay for every kilobyte of storage. By using logical volumes, we can expand the disk on demand without downtime, which can help us keep costs down.

The price has room for improvement.

I have been using Red Hat Enterprise Linux for three years, but I have known about the OS since version four.

Red Hat Enterprise Linux is definitely resilient and easy to recover, especially when compared to Windows. I enjoyed working with Red Hat Enterprise Linux more than Microsoft Windows, especially because of its resilience.

Red Hat Enterprise Linux's scalability is easy to manage. We can simply spin up more instances as needed, and then turn them off when we no longer need them. This means that Red Hat Enterprise Linux's scalability is not as much of an issue with the cloud provider.

We have around 2,500 instances of Red Hat Enterprise Linux in our environment.

Red Hat support is generally good, but it can sometimes take a little longer than we would like to get a response, especially when the issue is through a web-based chat.

Positive

The on-premises deployments are subscription based, and the cloud instances are from the providers which are AWS and Alibaba.

We can always ask for Red Hat Enterprise Linux to be less expensive but when we compare it to other options, there are savings in the long run.

Red Hat Enterprise Linux was our first choice because of its enterprise support. That was the key factor. We do also run other Linux distributions, but Red Hat Enterprise Linux is our primary choice because of the enterprise support. 

The big difference between Red Hat Enterprise Linux and other Linux-based operating systems is the support. There isn't much difference other than the syntax, where the command is "at, get" versus Red Hat using YUM or DNF for installation. So outside of that, the support is the main difference.

I give Red Hat Enterprise Linux a nine out of ten. No solution is perfect, but Red Hat Enterprise Linux is very close.

Our engineering team probably used the image-building tool. I am on the operations side, so I do not see that part of the process. I take the images that are already built and deploy them.

I think it's just a workflow issue. We need to improve our own workflows to be able to manage them better. Red Hat support is already good when we encounter something we're unfamiliar with. So, we need to get Enterprise CoreOS from Red Hat for those cases. I think as we encounter more of our own workloads, we'll need to improve our workflows even further.

I am utilizing Red Hat Enterprise Linux for automated workloads.

Having prior experience with Ansible and its automation capabilities, I sought a centralized platform with a graphical interface. Red Hat Ansible Automation Platform seemed like the ideal solution, especially since I was already familiar with Red Hat Enterprise Linux. This familiarity made it a natural progression to explore containerization within the RHEL environment.

Red Hat Enterprise Linux helps to centralize development.

Choosing Red Hat Enterprise Linux for our container environment provides a more secure and reliable platform for our applications.

I appreciate the robust security features in Red Hat Enterprise Linux, such as including security benchmarks like CIS security hardenings. These benchmarks offer a significant improvement over previous Red Hat Enterprise Linux versions and provide numerous valuable security enhancements.

The most crucial factor is arguably the availability of fast, reliable, and effective support, as this prevents isolation when managing Linux systems and significantly mitigates risk.

Open integration is beneficial because it enables the use of various benchmarks to strengthen Red Hat Enterprise Linux.

Integrating Ansible Automation offers benefits, while Red Hat Enterprise Linux provides robust security features, including benchmarks for security hardening.

I would like a more straightforward process for extending file systems without the need to write all the names of logical volumes, to simplify administration and automation.

I have been using Red Hat Enterprise Linux for about ten years.

Early versions of Red Hat Enterprise Linux had several issues, but up from RHEL 7 I have found it very stable.

The support is accessible and responsive. I have engaged with them almost every day for two weeks and opened many cases, receiving assistance with my challenges and issues.

Positive

The Red Hat Enterprise Linux subscriptions are quite expensive.

Red Hat Enterprise Linux is considered an industry standard.

I would rate Red Hat Enterprise Linux nine out of ten.

I recommend considering Red Hat Enterprise Linux if the budget allows, as it is widely used in the industry and offers superior software support.

Red Hat Enterprise Linux is a versatile operating system for many workloads, including databases, web applications, and infrastructure. It is a reliable and adaptable platform suitable for various computing needs.

When I started my current job 14 years ago, we used many different Linux distributions, which created management challenges. However, when we began deploying a hardened version of Linux, Red Hat Enterprise Linux was the best option due to its robust support, familiarity with our team, and overall suitability for our needs, making it an easy choice.

Red Hat Enterprise Linux has performed well for our business critical applications.

It offers robust built-in security features that surpass those found in Windows. Its highly customizable environment allows for easy system hardening, eliminating the need for additional purchases as all necessary security components are integrated within the operating system. 

Red Hat Enterprise Linux enhances security and reduces risk. In a mixed environment with Windows, securing Windows systems is significantly more challenging and achieving a truly secure state is nearly impossible, whereas Red Hat Enterprise Linux offers robust security features that mitigate these concerns.

It contributes to risk reduction through its strong security features. With a mixed environment of Linux and Windows, making Windows secure is challenging, whereas RHEL does not have such issues. Furthermore, automation with RHEL reduces manual labor, allowing us to automate almost everything, which saves work.

The portfolio helps reduce our total cost of ownership by significantly decreasing employee work hours. Automation through ready-made images eliminates manual labor, allowing us to automate almost everything and ensure consistent accuracy, ultimately saving time and resources.

Red Hat Enterprise Linux's built-in security features are very good. Compared to other systems like Windows, it's on another level. With SE Linux and the customizable nature of Linux, creating a tightly-hardened environment is easy. Additionally, the knowledge bases and white papers provided by Red Hat support are very helpful.

While there are no specific features I would like added to the next version, there is always room for improvement.

The licensing cost of Red Hat Enterprise Linux is high and could be improved.

I have been using Red Hat Enterprise Linux since 1998.

Red Hat Enterprise Linux performs admirably, earning a nine-point five out of 10. While minor issues exist, they are not significant enough to substantially detract from its effectiveness.

The Red Hat support works well, though I haven't used it extensively. I appreciate the knowledge bases and articles provided by them. Consultancy services have been used, but not much of the support services itself.

Positive

At my current job, we started with a lot of different distros. Managing them was chaotic. When we began using hardened versions of Linux, Red Hat was selected because it was the best option for us. We have a support system in place and Red Hat Enterprise Linux is familiar to our team, making it the easy pick.

Red Hat Enterprise Linux licensing is expensive.

I would rate Red Hat Enterprise Linux nine out of ten.

We will soon be using Red Hat Enterprise Linux for containerization projects.

For servers, Red Hat Enterprise Linux is the recommended choice due to its robust features, including comprehensive updates, ease of management, and excellent compatibility with tools like Ansible. While other distributions may be suitable for workstations, Red Hat Enterprise Linux excels in server environments with its stability and long-term support.