Red Hat Enterprise Linux 8 (redhat 8) | Support by SupportedImages

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 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.

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.

I have been using Red Hat Enterprise Linux (RHEL) for the past three years.

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.

Red Hat Enterprise Linux (RHEL) scales to my needs pretty much up-to-date.

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.

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.

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.

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.

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.

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 main use case for Red Hat Enterprise Linux (RHEL)  is for the central monitoring of the operations.

Red Hat Enterprise Linux (RHEL)  helps me solve pain points by enabling faster transactions and more transactions.The feature I like the most about Red Hat Enterprise Linux  (RHEL) is its resilience.A huge amount of transactions benefits my organization because we use this cluster to include the performance of Red Hat Enterprise Linux  (RHEL).Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk.

Red Hat Enterprise Linux (RHEL) could be improved with frequent updates.I think frequent upgrades should be included in the next release of Red Hat Enterprise Linux (RHEL).

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

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) by stating that it is very secure, reliable, and fast.I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) scales effectively with the growing needs of my organization.I have not experienced any issues with Red Hat Enterprise Linux (RHEL).

I would evaluate customer service and technical support for Red Hat Enterprise Linux (RHEL) as good, and we have vendor coordination with them.On a scale of one to ten, I would rate customer service and technical support for Red Hat Enterprise Linux (RHEL) as an eight because it needs the streamlining of things.

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using a platform from IBM initially, which was pushed into containerization.

I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as not complicated and manageable, and that works well.

I manage my Red Hat Enterprise Linux (RHEL) systems with mass provisioning and patching, and I am very satisfied with the management experience.I managed the expansion on Red Hat Enterprise Linux (RHEL) as well.

I have not really seen an ROI with Red Hat Enterprise Linux (RHEL).

My experience with pricing, setup cost, and licensing for Red Hat Enterprise Linux (RHEL) is that pricing is heavy on this.The setup cost and licensing for Red Hat Enterprise Linux (RHEL) involves a perpetual license.

The other solutions I considered before selecting Red Hat Enterprise Linux (RHEL) included open source options.What stood out to me in my evaluation process of Red Hat Enterprise Linux (RHEL) is that the main feature is security on top of the open source, and we are considering the open-source platform to be implemented.

The complexity of Red Hat Enterprise Linux (RHEL) comes from the methodology, which is complex.Security requirements were a consideration in choosing Red Hat Enterprise Linux (RHEL).My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security features is that it is effective when it comes to simplifying risk reduction and maintaining compliance.My upgrade and migration plans for Red Hat Enterprise Linux (RHEL) to stay current include frequent patching and upgrades annually.I assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as good for a few use cases.The factors that led me to consider the change to Red Hat Enterprise Linux (RHEL) were stability and reliability.I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as not complicated and manageable, and that works well.I have no advice to give to other organizations considering Red Hat Enterprise Linux (RHEL). I would rate this product a nine overall.