Red Hat Enterprise Linux (RHEL) Reviews

Red Hat Enterprise Linux is used within our organization to orchestrate a multitenant, microservice-based architecture. This supports a distributed system of predominantly web-based applications and frontends. A typical deployment involves around 60 to 70 Amazon EC2 instances working in concert.

The primary use cases involve running interconnected applications with requirements such as low latency and high availability, often achieved through redundant, multi-tenant, and load-balanced architectures. These applications may utilize read or write-optimized instances or be memory or processor-optimized, depending on their specific needs. Optimization is achieved through the processor, RAM, and connected protocols. The foundation for these applications is Red Hat Enterprise Linux.

Red Hat Enterprise Linux facilitates seamless workload migration between diverse cloud environments and data centers. In DevOps, workload portability between cloud and data centers is crucial, so we prioritize operating systems supported by multiple cloud providers and available locally. Key considerations include stability, security hardening capabilities, and the ability to obtain government or compliance organization approvals, which are incredibly stringent in sectors like banking and securities exchange. Red Hat Enterprise Linux meets these requirements by providing a secure, reliable, and consistently delivered operating system that facilitates approvals and ensures seamless workload mobility.

Regarding Red Hat Enterprise Linux provisioning and patching, both processes are generally straightforward. Patching can be completed within a few hours. Once the automation pipelines are properly configured, tested, and operational, provisioning can be fully automated. This applies to any operating system, not just Red Hat. Setting up a correct pipeline ensures smooth provisioning regardless of the OS.

Implementing Red Hat Enterprise Linux has resulted in significant resource savings due to its efficient usage of minimal resources. Compared to other operating systems, Red Hat Enterprise Linux requires less RAM and CPU allocation, which translates to cost savings. Additionally, its stability and minimal downtime contribute to operational efficiency.

The Red Hat command line interface is more user-friendly than the Windows command line interface. Red Hat makes it easier to perform tasks like reviewing logs, checking network connectivity, checking DNS, and setting up a proxy. Additionally, searching for specific characters within numerous log files is simpler in a Red Hat Enterprise Linux instance compared to other operating systems.

The implementation and limitations of SELinux should be re-evaluated. Its current configuration presents numerous challenges and restricts certain functionalities, hindering the overall usability of Red Hat Enterprise Linux. Addressing these limitations would significantly enhance the operating system's flexibility and efficiency.

I've been using Red Hat Enterprise Linux for six years.

Red Hat Enterprise Linux is almost perfect in terms of stability. It works consistently with minimal downtime and very few bugs or glitches, deserving a high rating for stability.

There are no issues with scalability when it comes to Red Hat Enterprise Linux. It scales efficiently, fulfilling our needs without difficulty.

My experience contacting Red Hat technical support was positive, with knowledgeable and supportive staff, particularly during early hours. However, I found more detailed knowledge through community interactions on platforms like Stack Overflow.

Before adopting Red Hat Enterprise Linux for production applications, other Linux operating systems like Ubuntu and Windows servers were used for monitoring and testing purposes. Red Hat Enterprise Linux became the choice for critical server applications.

The initial setup of Red Hat Enterprise Linux is straightforward. Once the images and database information are available, the automation process is simple and efficient, taking only a couple of hours to complete.

Using Red Hat Enterprise Linux can yield resource savings of 200 percent to 300 percent compared to Windows Server instances. Its minimal RAM and CPU usage allows for smaller instances, resulting in significant cost reductions.

Red Hat Enterprise Linux is a more cost-effective solution than Windows Servers. Windows Servers base their cost on the number of users and have high licensing fees, while Red Hat Enterprise Linux offers free versions alongside its paid, supported versions. This makes Red Hat Enterprise Linux a good option for startups and organizations with limited budgets. While the free versions may lack direct vendor support, the availability of paid support options and the robust Red Hat Enterprise Linux ecosystem provides flexibility for growing businesses. Additionally, the presence of compatible open-source alternatives further enhances cost-effectiveness and choice. Overall, Red Hat Enterprise Linux presents a compelling advantage in terms of cost compared to other operating systems, especially for nascent organizations.

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

While Red Hat offers free license versions and CentOS provides a similar platform, the official Red Hat documentation may not be the most helpful resource. More valuable support can often be found in community-driven platforms like Stack Overflow, where users share their knowledge and experiences through questions and answers. This user-generated content often proves more practical and supportive than the official Red Hat resources.

Red Hat Enterprise Linux is deployed in a multi-region configuration with three availability zones per region. Data is replicated from region one to region two, which serves as a read-only replica. Traffic is load-balanced across all availability zones within a region, ensuring automatic failover to the remaining zones in case of an outage. Similarly, if an entire region fails, traffic is redirected to the other available region. This setup provides high availability and disaster recovery capabilities. We have a couple of thousand users in our organization.

Red Hat Enterprise Linux requires periodic updates. To manage logs, a retrieval and deletion method is necessary, which can be achieved using built-in features like cron jobs. Red Hat supports these features. Additionally, security patches should be applied as they become available.

I recommend Red Hat Enterprise Linux, particularly for enterprise implementation, due to its lightweight and secure design. Its robust community support and extensive availability of solutions in forums and unofficial resources make it preferable to other operating systems.

The solution is used for on-premises data centers. Multiple private data centers run workloads on VMware Cloud solutions, and Red Hat Enterprise Linux is deployed on critical systems. We use KVM virtualization technology to host various virtual machines on Red Hat Enterprise Linux that run workloads and applications.

Red Hat Enterprise Linux improved our compliance by working with third-party security providers, like CIS Enterprise Internet Security. It's a nonprofit organization that provides many security solutions and benchmarking for each operating system. CIS and Red Hat jointly developed a CIS-approved operating system. They work with various public cloud providers like App Engine, Google, and AWS to provide comprehensive CIS-approved images in Red Hat Enterprise Linux. 

The US federal government has already certified the OS for FIPS compliance. FIPS is the organization that designs cryptography algorithms for federal agencies, and they approved Red Hat Enterprise Linux. 

It takes some time to realize the benefits. Some customers cannot see a direct benefit because the licensing is a bit complex. In a huge enterprise environment, you could see an immediate effect, but a smaller or medium-sized organization may take a while to yield a return on investment.

The most significant advantage is that it is more stable and secure than other operating systems. Years ago, we worked on Windows-based systems with more challenges regarding patch management and vulnerabilities than Unix operating systems. We get more frequent patch releases from the vendor weekly, monthly, and quarterly. It also has strong security features, is OIS and FIPS certified, and has built-in Linux security configurations.

In addition to Linux's built-in security tools, it has Red Hat Enterprise Linux configuration features that provide robust security controls. We also have third-party solutions that provide more in-depth solutions for our cloud and on-premises infrastructure. We have to provide security at each layer of the OSI models. For example, on the application layer, we have to provide web solutions or application gateways, but it provides good security features for the OS layer. 

We use another Red Hat product called Ansible to automate patching tasks and infrastructure deployment. We don't have a large number of servers, so we manage patching and configuration through Ansible. For bigger deployments, they have solutions like Satellite, but we use Ansible. 

We use Image Builder to create a Golden Image for our CICD pipelines. We have a CIS-approved image that integrates their security controls for our automation tools and some of the ones specific to our organization. We added some of the controls from the Red Hat management framework that govern how an image should be created and what controls must be integrated into this base image. 

The web console is useful for people without Linux backgrounds who lack experience working with the command prompt. The web console helps them manage the system better without knowing all the commands.

Red Hat Enterprise Linux licensing is a bit complex. The solution operates on a subscription-based model, which may not provide immediate return on investment for small to medium-sized organizations. It also has a steep learning curve for employees unfamiliar with Linux, and it demands a skilled team or a dedicated service center to operate effectively.

I have used Red Hat Enterprise Linux for about four to six years.

Red Hat Enterprise Linux offers great stability and performance compared to other operating systems. It does not have issues with crashing or substantial downtime.

I rate Red Hat support seven out of 10. We have only opened one or two cases with technical support, but we've had good experiences. They respond immediately based on the SLA level. In the future, we plan to use Red Hat's OpenShift and Kubernetes solutions, so we expect to work with the support team more because we're new to those products. 

Red Hat's Knowledgebase is an excellent support resource. It stays updated about new things coming to our region and provides lots of articles about the products. It's a good starting point for troubleshooting without the need to call the support team. We use the knowledgebase to resolve issues as often as we can, but we contact support if we get stuck and can't find the solution. 

Neutral

We have physical systems running SUSE Linux and Windows, but we're gradually migrating them to Red Hat Enterprise Linux. Some systems are running Solaris, and we haven't decided whether we'll migrate to Red Hat Enterprise Linux or other operating systems.

Our operations team takes care of migrations and installations. We're primarily responsible for business impact assessments and helping the operations team do a POC to determine the effect on the application environment. We consider the licensing and give the operations team approval to do the migrations and install the new operating system. 

The team consists of two or three people. We cannot migrate directly from one system to another. We simulate everything in the POC environment and perform migrations in the development environment using our in-house tools. They will check the source machines and find out what applications are running. It will assess them and look into the destination systems. Using some replication technology, it will do a direct synchronous verification between one storage to the other.

We need some downtime to complete the migration, and most of the data is stored in SAN storage. That is called a long migration. Once the operating systems and associated patches and applications have been migrated, we have to migrate them manually for the storage side.

The subscription-based pricing can be costly, particularly for smaller deployments. The more subscriptions you have, the easier it is to see a return on investment because it helps larger organizations more. It may be considered expensive compared to other solutions like CentOS or Ubuntu, which offer some of the same features without additional costs.

I rate Red Hat Enterprise Linux eight out of 10. I recommend new users get some training on the platform because installations and migrations can be complex. Setting up clusters can be challenging for new users who don't have hands-on Linux experience without vendor assistance. 

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.

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.

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.

I have dealt with Red Hat Enterprise Linux (RHEL) for around 10 years, even when it was not part of IBM.

My opinion of Red Hat Enterprise Linux (RHEL)'s scalability is that it was very easy.

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.

Positive

The initial setup of Red Hat Enterprise Linux (RHEL) is straightforward compared to AIX, which is more convoluted.

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.

I've been using Red Hat Enterprise Linux (RHEL) for four or five years now because I had a business with my cousin. We are Red Hat Partners. Easier integration is important because most customers we work with already have Red Hat. We use Ansible for discovery, primarily for ServiceNow. We also wanted to expand into the field of Maximo asset management. One customer, a big Red Hat partner, uses IBM Maximo, but that didn't work out because I have a business with my cousin and one of his partners parted ways, so I stayed with ServiceNow.

Red Hat Enterprise Linux (RHEL) helps solve pain points related to user account servers and onboarding certain servers. It's easier to use in my opinion and less complicated, especially for Ansible discovery.

Organizations need to know what assets they have because sometimes they have assets on the network and don't know what they are. With the solution, it's easier to discover the assets, what OS is running on them, sometimes location, warranty information, and serial numbers.

Regarding security requirements and considerations in using it in the cloud, I've seen a lot of virtual machines on the network, and no one knows anything about them. As soon as you deploy Ansible, you can know exactly what servers the virtual machine is running on, whether there's a warranty, serial numbers, naming convention, and all that, which makes it easier.

For now, Red Hat Enterprise Linux (RHEL) works fine for me. When I used it in the past, I don't see what I can improve now because it works the way I want it. There aren't any additional features that I think should be included in the future since you have AI now, and I think you are up to date.

I've been using Red Hat Enterprise Linux (RHEL) for four or five years now.

Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risk. When it comes to downtime, there are no worries, for example, when there's an issue or something is down, the response time is solid.

Customer service is great, and there are several certifications and lots of certification options you can get for you and your team. Red Hat Enterprise Linux (RHEL) is also worldwide, and everyone knows it.

Positive

Red Hat Enterprise Linux (RHEL) is easy. Compared to other companies, everything is there and it's easy. When it comes to price, I can say it's cheaper than certain solutions out there in Asia or overseas.

This product is not purchased on the AWS Marketplace; we're helping sell our customers with our ServiceNow migrations, so we don't push or purchase anything from AWS Marketplace. Everything about Red Hat Enterprise Linux (RHEL) is online and it's easy to become a Red Hat partner. It's not hard. My cousin had the business with us and was already a Red Hat partner. It's easy to get the certifications, and they make everything easier. Red Hat Enterprise Linux (RHEL) is what most companies use before selecting it, and it's mostly worldwide use for that. That's what my cousin and I thought when he had the business. I would say the solution is an easier option overall. My overall rating for this product is 5 out of 5.

My use case for Red Hat Enterprise Linux (RHEL) is for dockerization; I use it for Docker or Postman. We use it for microservices, for example, to install JBoss and deploy some applications and pipelines for processes such as CI/CD. A summary of what I do includes microservices for applications such as Tomcat or JBoss, or for microservices in Postman, and installing Jenkins and launching pipelines.

Red Hat Enterprise Linux (RHEL) has helped reduce downtime and lower risks for me. There are rarely crashes or errors.

Image Builder or system roles feature is beneficial because it is a feature that allows you to create small images for what you need. With these images, you can go to a registry or whatever with VMware or KVM, and you can deploy them very quickly and efficiently. I tested it because it's better than having to install another machine all over again and losing much time. With Image Builder, you can create a small image tailored to your necessities. It is a good solution; you have to embrace automation, and the Image Builder helps you automate the creation of servers and images.

I appreciate all the Red Hat products available and the support provided when encountering any issues or needing help. You can open a case, and they answer very quickly. 

The other reason is it is a very strong OS for your needs. For example, I work in a banking system and in a financial system, and all kinds of products that you have—the problems may come from development, not from the server or machine.

In the knowledge base of Red Hat Enterprise Linux (RHEL), I can find everything I need. I don't have to go elsewhere. There are some videos with practical advice, all in one place, and all for free. I'm very happy with this kind of resource and knowledge base.

I find Red Hat Insights very helpful and beneficial. In all IT departments worldwide, I find it important because when I call my colleagues or other companies, this is a very significant feature. Insights gives many opportunities, particularly regarding security, and provides more facilities to improve security in your servers. In my opinion, the most important security feature in Red Hat Enterprise Linux (RHEL) is Red Hat Insights. When you use Red Hat Enterprise Linux (RHEL), you can install an agent in your Linux, and this agent runs on your Linux and gives you all the CVEs or security issues you have. For me, as an administrator, this is very helpful because with minimal clicks, I have the solutions and instructions on how to solve them. You only need to connect to Red Hat, and they provide a deployment, scan your machine, or all machines with Ansible, and give you a summary of your vulnerabilities, and you apply the solutions they provide.

The areas that have room for improvement in Red Hat Enterprise Linux (RHEL) include having more case bases and possibly more forums or places. A community that is not just informal but rather official could be beneficial. Everything else is good.

I would suggest improving compatibility. Sometimes I find that Red Hat is not aligned with the rest of the world. They create their own solutions, such as Docker, Podman, Kubernetes, and OpenShift, which can be better than what others offer. This can be both good and bad, depending on the situation. On the positive side, their innovations can enhance the overall quality of the company’s offerings. On the downside, when you need certain images or components that deviate from industry standards, it can become confusing. I find it difficult to understand why they choose to differentiate themselves from the rest. 

I have been in IT for 24 years, working with Linux and Red Hat Enterprise Linux (RHEL) for about 10 years.

I would rate the stability of Red Hat Enterprise Linux (RHEL) as a nine out of ten.

Red Hat Enterprise Linux (RHEL) is scalable for my business. It is very important, and I cannot imagine working without it.

I would rate the technical support of Red Hat Enterprise Linux (RHEL) as an eight out of ten.

Positive

I have worked with Ubuntu and SUSE, but I prefer Red Hat Enterprise Linux (RHEL) because the support is better than others. All solutions, how the machine or OS works, and all the other products, for example, OpenShift, I appreciate. I feel very comfortable with Red Hat Enterprise Linux (RHEL) because it is a solution based on CentOS and Fedora, and since my early career, I studied and learned in this distribution.

The deployment of Red Hat Enterprise Linux (RHEL) is very easy.

Red Hat Enterprise Linux (RHEL) has saved me about 40% to 50% time.

I would recommend Red Hat Enterprise Linux (RHEL) to other users; it depends on the company size. For medium and bigger companies, it is necessary because all the components needed, such as support and stability, are available. I cannot help much with the pricing because I do not work with licenses; this comes from another department. I discuss with my boss about how many machines or servers we need, and they coordinate with the commercials. I do not have information about whether it is cheaper or expensive, but I hear that they are very comfortable depending on how you deal with them. 

I would rate Red Hat Enterprise Linux (RHEL) an eight out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) include workflow development. We are running the workflow in that.

The features of Red Hat Enterprise Linux (RHEL) that I appreciate the most include OpenShift. These features have benefited my organization through working on on-premise cloud migration. 

Some of the high sensitive data cannot go to the public cloud, so we are trying to use Red Hat Enterprise Linux (RHEL) for the internal migration. We got rid of the VM maintenance and related tasks.

Security requirements were a key consideration in choosing Red Hat Enterprise Linux (RHEL) in the cloud. We are from the financial industry, so customer data is one of our big responsibilities. When it comes to managing Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, we currently work with our middleware team for upgrades, however, the plan is to work with AWS or the Red Hat team for future upgrades.

My assessment of the built-in security features is limited as I'm from the development side. Our upgrade and migration plans to stay current involve recommendations from our vendors.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk. Our restart used to take considerable time initially, but through optimization, it now takes significantly less time. I would assess the knowledge base as good. We received dedicated training this summer from Red Hat Enterprise Linux (RHEL), with trainers coming to our office for two days, which was very beneficial.

The pain points that Red Hat Enterprise Linux (RHEL) helps me solve include the transition from a Microsoft background, where I had a habit of everything with a GUI. I see very few GUI elements in Red Hat Enterprise Linux (RHEL) and many command lines. I'm not proficient in that, which makes me struggle sometimes. Overall, we have the tools, however, there should be drag-and-drop, window-type functionality.

I've used the solution for 11 years. 

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as very good. As a developer, I have never seen any downtime, so it is working perfectly fine from the middleware side.

Red Hat Enterprise Linux (RHEL) scales efficiently with the growing needs of my organization. They consistently release new versions. The scalability has been going well. 

We have expanded usage, and the process was smooth. In the beginning, we had very few applications, and now I can see many applications running on that side. It is definitely expanding.

I would evaluate customer service and technical support as very proactive.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using Microsoft Windows Server. Now our focus is more on this area. The factors that made us want to change include transitioning from Microsoft technology, moving to Pega and Java side. This technology is much more supported on this platform.

The initial deployment was very good. 

I have been involved in Red Hat Enterprise Linux (RHEL) upgrades or migrations, and due to our many internal dependencies, it takes time, however, we successfully completed it.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL) because we have many critical applications running without any issues. There is significant ROI on that.

The other solutions I considered before choosing Red Hat Enterprise Linux (RHEL) include using three or four vendors as a business continuity plan. We have Red Hat Enterprise Linux (RHEL), AWS, Windows and others. We cannot rely on one vendor; we have to work with multiple vendors to maintain business continuity.

The advice I would give to other organizations considering Red Hat Enterprise Linux (RHEL) is that it's a really good tool to use if they have applications in Java, Pega, or IBM workflow or Lombardi. 

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) a nine out of ten.

Our main use cases for Red Hat Enterprise Linux (RHEL) include having servers all around for storage and processing, specifically for compute processing.

The best feature of Red Hat Enterprise Linux (RHEL) that I appreciate is that it provides consistent configuration setups with step-by-step configuration, which is easier. When configuring a server, what previously took at least a 24-hour turnaround time now takes only 30 minutes to one hour.

I am satisfied with the management experience and normally choose Red Hat Enterprise Linux (RHEL) when there is an option between it and other solutions. I have been involved in RHEL upgrades or migrations from many years ago, approximately 14 to 18 years back. Currently, everything is easier as upgrades and patches come as a package.

Regarding built-in security features, maintaining compliance is handled at the architect's level during configuration setups. While the service provider handles access level security, configuration compliances need to be managed by the architect.

The upgrade and migration process in AWS is straightforward - I can easily increase the number of processors through hot migration, which can be done while the system is running without requiring shutdown. RHEL has helped mitigate downtime and lower risk with negligible system interruptions.

Red Hat Enterprise Linux (RHEL) could be improved with more shared storage capabilities. For example, I have multiple RHEL instances, and enhanced storage sharing would be helpful for transferring data between servers.

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

I assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as very stable, with negligible downtime, crashes, or performance issues.

Red Hat Enterprise Linux (RHEL) scales efficiently with the growing needs of my organization as it is one of the managed shared services. When we check the scalability option while configuring, it manages everything automatically without requiring separate actions. I have expanded usage, and the process has been smooth with zero downtime.

I haven't had the opportunity to evaluate customer service and technical support because we address any issues through AWS since it's a managed service.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was not using another solution to address similar needs.

I manage Red Hat Enterprise Linux (RHEL) systems for provisioning and patching through AWS, which handles the patching at the service provider level. Provisioning is easy because I can modify configurations, such as the number of processors and other parameters.

The deployment model for Red Hat Enterprise Linux (RHEL) is cloud. Security requirements were a consideration in choosing RHEL in the cloud, as AWS provides most of the security features.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL) as the prices have been reduced since we implemented a shared environment.

I cannot speak to licensing because we are using managed services from AWS. Regarding pricing, setup cost, and licensing, all costs come from AWS on a pay-as-you-go basis. We get charged when the service is up; otherwise, there is no cost.

Before selecting Red Hat Enterprise Linux (RHEL), I considered something similar to VMware. These were the two options I chose between.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is that it's easy to use and a reliable service. It has been consistently at the top in this industry for ages and has its own strengths. I would recommend it as a first choice.

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) as eight or nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) cover all the tiers from web application to the database.

The feature of Red Hat Enterprise Linux (RHEL) that I prefer most is Insights. I have been using Insights, and it can give me the health of the system, CPU, memory, and everything, allowing me to see everything including security patches, vulnerabilities, and missing patches. 

Red Hat Enterprise Linux (RHEL) helps me solve pain points because it is a stable platform, so I don't have to fix many issues because we're using Ansible to automate everything. Since we have a very stable environment and Red Hat Enterprise Linux (RHEL) is very stable, we don't have much pain. Red Hat Enterprise Linux (RHEL) benefits my company significantly because by using it, we are using a stable platform, and all our environments are working as expected.

It has excellent features in terms of security. Everything is there. I just need to deploy it, and we have the SELinux, OpenSCAP, and many tools that I can use to configure the system to make it more secure. For upgrade or migration plans to stay current, we're using the automated LEAP process for migrating from a lower version to the latest version.

I see that there's a lot of improvement needed, but I can see that Red Hat Enterprise Linux (RHEL) 10 has some of the features that I'm looking for.

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

I have peace of mind, so everything with Red Hat Enterprise Linux (RHEL) is reliable and stable.

Red Hat Enterprise Linux (RHEL) has helped me to mitigate downtime and lower risks because we have everything in place to mitigate any issues since we have a failover on the other side.

Red Hat Enterprise Linux (RHEL) scales effectively; all the needs of our company are being met by Red Hat Enterprise Linux (RHEL).

I have experience with customer service and technical support. The experience with customer service has been pleasant, but some of the features that I am looking for are not met, so they're still working on it. I would rate the customer service an eight out of ten.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) has improved now because of AI. Previously, when I searched for something, it didn't give me everything, but now I am more satisfied.

Positive

My experience with deploying Red Hat Enterprise Linux (RHEL) is smooth. We are using an automated process; we're using VMware VRA and Ansible to customize the environment. Everything is smooth in building Red Hat Enterprise Linux (RHEL) because we have the process from end-to-end, it's very well-defined, so we don't have any problem deploying Red Hat Enterprise Linux (RHEL).

We have a hybrid environment with on-premise or cloud deployment. We use all cloud providers. 

When it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, we're using automation with Ansible Automation Platform, AAP, and everything is going smoothly, and I am satisfied with that experience.

I am looking to make the deployment much easier because there's the Image Builder that I prefer, and in building using the Image Builder, all the packages or repositories that I need are inside that feature. 

The biggest return on investment for me when using Red Hat Enterprise Linux (RHEL) is peace of mind; I don't have to worry about the operating system because it's running smoothly as expected.

Security requirements were a consideration when choosing Red Hat Enterprise Linux (RHEL) because since we're in the government, I'm the one that set up the compliance requirements, and I deployed using the OpenSCAP, but I cannot tell the profiles as it's confidential.

While using Red Hat Enterprise Linux (RHEL), I have not considered other solutions; we are working on moving to OpenShift, which is still Red Hat Enterprise Linux (RHEL).

I would rate Red Hat Enterprise Linux (RHEL) as a nine out of ten; I don't give a ten because it's a perfect score. 

My advice to other companies that are considering Red Hat Enterprise Linux (RHEL) is that it is the best operating system currently, so they can use it in deploying their system, wherever they want to deploy the applications.

We run all of our servers on Red Hat Enterprise Linux (RHEL), specifically RHEL 8, and that's the production OS for all the servers in our farm.

The features of Red Hat Enterprise Linux (RHEL) streamline many things for us. Everything feels streamlined, smooth to use, and easy to operate, making it almost invisible without stressing about issues on the OS level. As essentially a sysadmin level engineer, I really appreciate the package manager. It's simple and easy to use, being the most straightforward part of using Red Hat Enterprise Linux.

I don't know how Red Hat Enterprise Linux (RHEL) can be improved. As a sysadmin level worker, everything I need to do, RHEL has been able to perform for me. I don't have a specific use case where I wish I had additional features, so I can't provide feedback on that. I'm not sure about how Red Hat Enterprise Linux (RHEL) could maximize or enhance any features. I don't really know anything Red Hat specific that's positive or negative that I can speak on. I'm not certain if Red Hat could smooth out the migration process from CentOS to Red Hat Enterprise Linux (RHEL). I think it's more internal stuff that needs to be ironed out rather than Red Hat having issues.

I've been using Red Hat Enterprise Linux (RHEL) for around three to four years now.

There have been no issues with Red Hat Enterprise Linux (RHEL) stability and reliability. We haven't experienced any OS level reliability issues.

The scalability of Red Hat Enterprise Linux (RHEL) has been excellent. Our recent hurdle was getting off of CentOS, but the scalability hasn't been an issue for us. It's been smooth sailing, just requiring the bulk work of migrating thousands of servers.

I haven't engaged with customer support at Red Hat for any help.

Positive

I did not consider another solution before choosing Red Hat Enterprise Linux (RHEL).

I'm not entirely sure at the moment about Red Hat Enterprise Linux (RHEL) upgrade or migration plans for what's ahead of us. We're just looking into the short term right now.

Once our team got comfortable with Red Hat Enterprise Linux (RHEL), we purchased Red Hat Learning on the side. After our team was trained on Red Hat through the Red Hat Learning subscription, the combined learning experience provided by Red Hat delivered many technical skills needed to be a comfortable sysadmin.

Everything has been running smoothly with Red Hat Enterprise Linux (RHEL). I don't have any previous criticisms that RHEL specifically has solved in our use case. I'm not well-versed in Red Hat Enterprise Linux (RHEL) built-in security features, so I can't comment on that aspect. I can't say if it has helped to mitigate downtime or lower risks specifically. Everything's so smooth with Red Hat Enterprise Linux (RHEL) that it's not something we really think about. We worry about other things rather than the OS level. I rate Red Hat Enterprise Linux (RHEL) 10 out of 10. I have not purchased Red Hat Enterprise Linux (RHEL) on the AWS marketplace.

We deploy it. We are a Red Hat partner and have been for 20 years. We help customers with all sorts of day-to-day Linux operations, and Red Hat is one of our partners for Linux.

Red Hat Enterprise Linux (RHEL) is the platform being used for running applications. Customers often have some sort of applications they need to run, and Red Hat Enterprise Linux (RHEL) has been the go-to standard for running applications that need to run on top of Linux for many years.

The feature I appreciate the most about Red Hat Enterprise Linux (RHEL) is its long lifecycle. The long lifecycle helps my company by allowing us to plan ahead; we don't have to redeploy everything every five years or so. It helps to plan ahead.

The support can be better. 

Satellite 5 was great at what it did. Satellite 6 is still a mismatch of different things. It's not really the optimal solution for many things yet. I hope they will release a new version soon that fixes this. I know it's been planned for three or four years, possibly five years.

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

The stability and reliability of Red Hat Enterprise Linux (RHEL) are very good, even according to what my customers say. We have had very few bugs where the actual operating system was to blame for any problems. There might have been one or two bugs that I could name that influenced our Red Hat Enterprise Linux (RHEL) running. It is quite bug-free. It's not perfect, but usually bugs are fixed if you raise a support case.

I don't think I've ever seen downtime caused by Red Hat Enterprise Linux (RHEL). I'm not sure if we have had any less downtime compared to other Linux distributions. We also see a lot of Ubuntu, and I don't see any less downtime on Red Hat than on other community Linux subscriptions.

Our use of Red Hat Enterprise Linux (RHEL) internally is quite limited. We have some customers who run thousands of Red Hat Enterprise Linux (RHEL) instances. It scales perfectly fine.

Their support isn't great, but it's good. It varies significantly depending on who you get hold of. It can be quite hard to get to someone who is actually able to answer the questions. We see instances where we have done all of the debugging ahead, but still are asked questions that we have already answered when we created the support ticket. We have to start all over again and use the first two or three days explaining exactly what we do, even though we have already written it. I have done this and they say, 'Have you done this?' And I respond, 'We have done that. We also wrote it when we created the case.' It can be difficult when the supporters don't always read what you have actually tried ahead of creating the support ticket.

Neutral

We also work with SUSE. The main differences between SUSE and Red Hat Enterprise Linux (RHEL) currently seem to be very political. Red Hat is an American company, and we are based in Europe, so we see that come up frequently.

It's easy to deploy. When it comes to managing the Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, I see one of two things normally. We have many customers who just do cloning, having a golden template which they clone and then create new VMs from that. We also have many customers who use Satellite. Those are the two methods we see at scale.

I have been involved in upgrades or migrations of Red Hat Enterprise Linux (RHEL) for 20 years. The process of migration just works.

Our upgrade or migration plans to stay current involve knowing the lifecycle for a specific version. It's just a matter of planning ahead. The long lifecycle and predetermined lifecycle of Red Hat Enterprise Linux (RHEL) make it easy.

The major cost of maintaining Linux is when you have to do reinstallations and upgrades. Having a long lifecycle really reduces the cost of maintaining an operating system. A long lifecycle is key to having a good return on investment.

I would rate Red Hat Enterprise Linux (RHEL) an eight out of ten.