Has supported critical applications and reduced infrastructure costs through community-driven updates
What is our primary use case?
My main use case for Rocky Linux is that all the applications used by our company are hosted in Rocky Linux servers, so we will be maintaining, remediating the vulnerabilities which are getting reported on the servers, patching the servers and making them up to date, and helping all the users who log into servers to use their applications without any issues.
A specific example of an application where I'm using Rocky Linux in my company is the POS machines which are used by the customers, where all the POS related applications are hosted in Rocky Linux operating system, so that's where Rocky Linux came into the picture, and from the OS level, we will be giving all the support wherever it is necessary.
The middleware packages such as Apache Tomcat, Java, HTTPD are all running on these Rocky Linux servers, so we ensure all those services are up and running without any issues.
What is most valuable?
The best features Rocky Linux offers are that it is much easier to use. Since it is open source, whatever issues we face, we can get answers from the community for each and every issue we encounter, so finding a solution for each problem is much easier, and that's the major feature I feel for Rocky Linux.
When comparing Rocky Linux to Red Hat, it is more stable, as whatever issues arise, we can solve them quickly, and since there is an open community, we receive help from everybody who is using this.
Rocky Linux has helped our organization significantly in terms of cost. If we were purchasing a Red Hat subscription, it would cost significantly more, but since Rocky Linux is open source and free, it has helped with cost reduction, allowing us to utilize those funds for other needed things.
When we moved from Red Hat to Rocky Linux, we saved around 70% of the cost which was used for subscriptions. That money is now used for other things such as middleware applications and monitoring applications including DataDog and Dynatrace.
What needs improvement?
To improve Rocky Linux, providing releases for each package, firmware, and kernel more quickly would be beneficial. Currently, it takes more than one month to release a new package or kernel, so speeding that up would help reduce reported vulnerability remediations.
Documenting the frequently asked questions and related issues in a PDF or Word document would be helpful so that everybody can refer to them, eliminating the need to post a question and wait for a reply, thus reducing time delay.
Currently, there aren't many needed improvements, only the support aspect needs a little improvement. Everything else is going well and smoothly.
For how long have I used the solution?
I have been using Rocky Linux for more than six years.
What do I think about the stability of the solution?
Rocky Linux is stable, scalable, and it is very much easier to use.
How are customer service and support?
Regarding customer support, since it is open source, most of the solutions are available on the community page, but even if we raise a support ticket, we receive a resolution or a reply from the team within two business days.
I would rate the customer support a seven.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before choosing Rocky Linux, we were considering moving with Red Hat itself, planning to move from RHEL 8 to RHEL 9, but after considering the cost involving Red Hat, we thought about an open source solution, which led us to Rocky Linux.
What was our ROI?
When it comes to return on investment, a lot of money is saved since we moved from a purchased license to the open source provided by Rocky Linux. Time is also saved since whenever an issue arises, we get resolutions from the community without needing to raise a ticket with the support team.
What other advice do I have?
When we encounter an issue, we look all over the internet, not only depending on the community, so whichever solutions provide us with proper resolution are considered.
My advice to others looking into using Rocky Linux is that it is much easier to use, it's scalable, performance is good, and there is no cost involved in using it.
I rate Rocky Linux nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Has supported automated deployments and improved security through consistent patching
What is our primary use case?
As a Cloud Ops Engineer, we are setting up the server on the EC2 machine with Rocky Linux, while also doing some setup related to the frameworks for Ruby. We are installing their dependencies related to the Ruby on Rails application and other security-level software such as Rapid7, CrowdStrike, and many more.
On Rocky Linux, we have deployed a Ruby on Rails application, and we have set up other applications as well.
We are not doing this stuff manually, as we have set up an Ansible automation script to set up all this stuff on Rocky Linux, and for the installation and server setup, we are using Terraform. Using Terraform, we are spinning up the instance on AWS EC2.
I purchased Rocky Linux through the AWS Marketplace.
What is most valuable?
Rocky Linux provides us with extended maintenance, security patches, and support lifecycle aligned with RHEL, making it highly reliable for critical systems. For production deployment, Rocky Linux is a great choice because it offers full RHEL compatibility without licensing costs, along with strong community support.
If we are planning to migrate from CentOS, it was very smooth and straightforward, and we can follow their official document to migrate from CentOS to Rocky Linux. Rocky Linux 8 is supported until 2029, and Rocky Linux 9 is supported until 2032, which is a significant benefit.
Previously it was CentOS, which is already EOL, and now we have the latest packages and an up-to-date operating system, so we get the most benefit at the security level. Also, performance-wise, we are seeing improvement in the application and day-to-day operations.
What needs improvement?
I have no suggestions regarding how Rocky Linux can be improved. I haven't identified any areas that need improvement yet.
For how long have I used the solution?
I have been using Rocky Linux for over a year.
What do I think about the stability of the solution?
Rocky Linux is stable in my experience.
What do I think about the scalability of the solution?
Rocky Linux's scalability is very easy. Even if the server is not responding and we want to attach the volume on another instance or a temporary instance, it is very easy and straightforward with no hiccups.
How are customer service and support?
I have not reached out to customer support for Rocky Linux. This has not yet been discussed with my security team, as this is recent, and the security team started checking on this.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We switched to Rocky Linux because our previous OS was EOL, and we had to switch to the new OS, so we chose Rocky Linux.
What was our ROI?
Regarding return on investment, we have chosen the same exact resource that we were using earlier, so there is no immediate return on investment. That needs to be identified if we can cut down our resources with a smaller instance, but that has not yet been figured out.
I notice money saved as a return on investment.
What's my experience with pricing, setup cost, and licensing?
There is no extra cost for a license if we are purchasing Rocky Linux from the AWS Marketplace.
Which other solutions did I evaluate?
I didn't evaluate other options before choosing Rocky Linux.
What other advice do I have?
I rate Rocky Linux a nine out of ten.
If you are using any other RHEL-based OS, Rocky Linux is very similar to other RHEL operating systems.
I see some performance-related issues, but we are still checking on that, and we don't know if it is related to the OS or the resource; that is something still to be checked from our end.
I would recommend doing a POC on your existing application or use case with Rocky Linux. If it works smoothly, then observe it for a few periods, and if it works properly for your application and whatever your use case is, proceed with implementation. Each application and use case works totally differently, so if it works for some applications properly, it's not a given that it will work for every application. First do a POC, and if it works properly, then you can proceed with implementation.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?