Red Hat Enterprise Linux (RHEL) for AWS

I use Red Hat Enterprise Linux (RHEL) , and we have a couple of customers using OpenShift, the Kubernetes  platform based on Red Hat, and also Red Hat Virtualization. My first contact with the Linux platform was with Red Hat.

The best features of Red Hat Enterprise Linux (RHEL)  are its stability and the RPM, Red Hat Package Manager, which is perfect. They also deliver Satellite, a platform for updates. It is a very robust, excellent platform.

For me, and for every Linux distribution, the most important security feature in Red Hat Enterprise Linux  (RHEL) is SELinux. Security is often misunderstood by others. SELinux is very important because it provides security for the kernel. Many people disable SELinux, but it is the most important and most misunderstood feature. People do not understand it. The updates and SELinux are very important to me. SELinux is very good, but it is complex, and I have seen many administrators disable it because instead of helping them, it causes trouble. For example, securing my NGINX  configuration is a pain. It is a very good security option, but I would say it is excellent only if one is an expert.

Red Hat Enterprise Linux  (RHEL) documentation is very good and very complete. Regardless of my opinion about the IBM acquisition, the documentation is excellent.

IBM committed two major mistakes with Red Hat. The first was destroying the CentOS  project, which was a fork of Red Hat. The second was limiting the use of free options and restricting hardware to support Red Hat on just some limited hardware. One can use the system for free, but the statement is not entirely true because it is limited to a couple of virtual processors and I do not remember if it was 24 or 16 GB of RAM. If one goes beyond that configuration, one has to pay, and IBM is IBM. Many companies were in trouble because from one day to the next, IBM said they would no longer support CentOS  and told them to move to another distribution. People had to migrate, and for that reason, there are Rocky Linux , AlmaLinux , and other Linux distributions that are trying to rise and taking advantage of that situation. Red Hat Enterprise Linux (RHEL) is just for corporate companies with money to waste on licensing.

Red Hat Enterprise Linux (RHEL) is very expensive. In the case of our customers, the couple of customers with OpenShift, they have enough money to license Red Hat. They bundle Red Hat with virtualization and OpenShift packages. However, it is not suitable for an SMB company. It is not payable or affordable. For me, it is very expensive.

I use Red Hat Enterprise Linux (RHEL) a lot, though I do not remember the exact frequency.

I have worked with Red Hat support, and it is very good because they have very good engineers. In Latin America, during my time, the support in Spanish was mostly provided by engineers from Argentina. In Colombia, I have worked with a couple of engineers from Colombia, and they were very good. I have not worked with support in English for Red Hat, only in Spanish with those engineers.

My first Red Hat Enterprise Linux (RHEL) certification, Red Hat Certified Engineer, was for version 6, which was approximately 12 to 15 years ago.

I have tried Red Hat Enterprise Linux (RHEL) Image Builder and System Roles, and it is pretty good.

I would rate the support at an eight out of ten. My overall rating for this product is ten out of ten.

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.

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.