We use Red Hat Enterprise Linux in the enterprise for production environments. We mostly use it on bare metal servers, which are dedicated. In terms of deployment, we use the on-premises version of Red Hat Enterprise Linux.
Red Hat Enterprise Linux for SAP with HA and Update Services 9.2
Amazon Web ServicesExternal reviews
External reviews are not included in the AWS star rating for the product.
Red hat in daily life
Essential
Talk about RHEL
Technologist
Security
Support
The product is very powerful
Incredible
RHEL user experience
Redhat Enterprise Linux for platform engineering
Red Hat Enterprise Linux for platform engineering
A great experience with Red Hat
We have better security and management, but it's not easy to see deployed security features
What is our primary use case?
How has it helped my organization?
Red Hat Enterprise Linux has given us better insights and allowed us to manage the environment more effectively. In terms of overall performance improvements, it has provided us with increased visibility into security, which has been helpful for our cybersecurity team.
Its built-in security features seem pretty sufficient for our purposes, but we have other teams that manage the security and build aspects. I am more involved in the maintenance of it, but in terms of the built-in security features, I find it sufficient. The security team also takes care of the compliance aspect.
I mainly use the Red Hat database for vulnerabilities. It is pretty good for determining whether or not a vulnerability has been resolved.
We use Red Hat Satellite for patching. I like Red Hat Satellite for patching and keeping us secure.
We have used Red Hat Enterprise Linux in hybrid environments. It seems to work fairly well. For hybrid environments, it is probably one of the easier ones to deploy because it allows us to scale.
We were able to realize the benefits of Red Hat Enterprise Linux immediately after the deployment.
What is most valuable?
In terms of the organization and structure, the support is on point. The reporting and other things are very standardized. It does not leave much room for error when working in production environments.
What needs improvement?
When we first deploy Red Hat Enterprise Linux, it is very challenging to determine which security features have been deployed. It would be beneficial to have more insight into this. Additionally, once it is built, there does not seem to be an option to retroactively change security features, which can make it difficult to ascertain which ones have been deployed.
Their knowledge base is very verbose. There is too much information. It can complicate things a little bit. It is very detailed. If they can shorten it, that might be helpful.
For how long have I used the solution?
We have been using Red Hat Enterprise Linux for a few years now, approximately seven to eight years.
What do I think about the stability of the solution?
I would rate the stability of Red Hat Enterprise Linux as seven out of ten. We do encounter problems, most of which can be resolved. Occasionally, we face issues that cannot be resolved until the kernel developers address them. These are typically dealt with through quarterly releases or major upgrades.
What do I think about the scalability of the solution?
In terms of scalability, I would rate Red Hat Enterprise Linux about a nine out of ten. It is easy for us to make snapshots when we are patching. If we need to clone, we can do so, although they might not be full backups necessarily.
How are customer service and support?
We use their portal for contacting support. The support from Red Hat is quite quick because it operates on a service-level agreement (SLA). For the paid support features, they are very responsive.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I am familiar with CentOS, and I have used OpenSUSE and SUSE Enterprise for testing and comparison purposes.
CentOS did not have as many security features. Of course, CentOS had the community support. CentOS was bought by Red Hat, and then the support started lacking. It was then discontinued to promote Red Hat Enterprise Linux.
How was the initial setup?
We have done some physical to virtual migrations using VMware. We have been mostly involved in that. We have done a little bit of virtual-to-cloud migration but not as much as physical-to-virtual.
The migration is more on the complex side. There are quite a few players involved. We need to collaborate with different teams. We need to make sure that the database is there, and that the database team is always involved. It is not terribly simple. It requires quite a bit of project planning and coordination. We usually have a six-month project so that it can be planned and tested.
It does require maintenance on our end but not very frequently.
What's my experience with pricing, setup cost, and licensing?
Red Hat Enterprise Linux licensing is quite costly, but I personally do not deal with pricing.
What other advice do I have?
My advice to new users would be to focus more on the build aspect because it can be overlooked by many new users.
The Leapp utility works well when you do not have a much-customized environment. The more customized your environment is, the more complicated it gets to get Leapp to work to switch over to Red Hat Enterprise Linux. It is possible, but the more customized your environment is, the harder it is because it will require the kernel module. Convert2RHEL is pretty much the same as Leapp. The more customized the environment, the harder it is. It is feasible. It is just a matter of how much time you are willing to spend on it.
I would rate Red Hat Enterprise Linux a seven out of ten.