This product has charges associated with it for a hardened, minimal RHEL 8 image, newest 8.x (now 8.10): SELinux enforcing, root login disabled, key-only SSH, audit rules, PAM lockout and sysctl hardening, each verified on a booted instance. 10GB size (no LVM), UEFI/GPT, cloud-init, ENA and NVMe, RHUI.
This is a repackaged open source software product wherein additional charges apply for a hardened, minimal Red Hat Enterprise Linux 8 image built and verified by Rinne Labs. Rolling: always the newest 8.x release, currently built from 8.10.
What you are paying for
Red Hat Enterprise Linux is assembled from free and open source software. This listing charges neither for the operating system nor for support.
The charge covers the hardened build: a security baseline applied to the image at build time, an automated assertion suite that proves every control of that baseline is live on a booted instance before the image is published, and continued rebuilds carrying current security updates.
Hardening baseline
Every control below is applied at build time and verified by an automated assertion against a booted instance before publication. The image records the baseline it carries in a versioned marker at /etc/rinne-labs-hardening.
SELinux enforcing, at runtime and persistently across reboots
Root login over SSH disabled
Key-only SSH: password and keyboard-interactive authentication refused
Reduced SSH surface: X11 forwarding off, lowered MaxAuthTries and LoginGraceTime, empty passwords and host-based authentication refused
Kernel network hardening via sysctl, confirmed live in the running kernel
Audit rules loaded in the running kernel, auditd enabled at boot
Account lockout via pam_faillock, with a bounded unlock interval and root exempt
Password quality enforcement via pam_pwquality
A default umask of 027 for login shells
Login banners on console and network logins
The default user's authorized_keys restricted to mode 0600
Key Features
Built from the official Red Hat Enterprise Linux 8.10 ISO, "Minimal Install" package group; moves to each new 8.x release as the distribution ships it
10GB root volume, no LVM, for a fast boot and a small storage footprint
UEFI/GPT boot with an XFS root filesystem
cloud-init configured; root partition and filesystem grow to the volume size at first boot
Elastic Network Adapter (ENA) and NVMe drivers present and verified
AWS CLI preinstalled
Distribution security updates applied at build time
Registered with Red Hat Update Infrastructure (RHUI); no Red Hat subscription required
Ideal For
Apache HTTP Server and NGINX web and reverse-proxy tiers
PostgreSQL, MySQL, MariaDB and MongoDB database hosts
Jenkins, GitLab CI and self-hosted GitHub Actions runners
Terraform, OpenTofu and Ansible control nodes
Docker and Podman container hosts, and Kubernetes worker nodes
Auto Scaling groups and immutable golden-image fleets
Frequently Asked Questions
How do I connect? SSH in as ec2-user with the key pair you chose at launch: ssh -i your-key.pem ec2-user@your-instance. Password login is disabled and root may not log in over SSH; run sudo -i for a root shell.
Do I need a subscription? No. The image is registered with Red Hat Update Infrastructure and receives updates through AWS without a Red Hat subscription.
Which version do I get? The newest Red Hat Enterprise Linux 8.x at build time: 8.10 today. It is rebuilt on each 8.x point release and as security updates ship. For one fixed minor, use the pinned Red Hat Enterprise Linux 8.10 listing.
Who maintains this image? Rinne Labs. Nothing is published until it passes the full assertion suite on a booted instance.
Why Rinne Labs
Every image comes out of the same reproducible, fully automated build pipeline, starting from the distribution's official ISO. Nothing is hand-edited in.
Every image is validated by an automated assertion suite against a booted instance, covering the hardening baseline, the cloud drivers, the repositories and the applied updates. An image that fails an assertion is not published.
"Red Hat" and "Red Hat Enterprise Linux" are trademarks of Red Hat, Inc. Rinne Labs is an independent publisher, not affiliated with or endorsed by Red Hat, Inc. This product repackages free and open source software; all trademarks are the property of their respective owners.
THIS IMAGE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
Hardened at build time and proven on a booted instance before publication: SELinux enforcing, root login over SSH disabled, key-only authentication, a reduced SSH surface, kernel network hardening, audit rules loaded in the running kernel, account lockout and password quality through PAM, a 027 umask and login banners. Every control carries an automated assertion that must pass before the image ships, and the image records its baseline at /etc/rinne-labs-hardening.
Minimal by construction: built from the official Red Hat Enterprise Linux 8.10 ISO, the newest 8.x release at build time, using only the "Minimal Install" package group, on a 10GB root volume with no LVM, UEFI/GPT boot and an XFS root filesystem. Fewer packages means a smaller attack surface, quicker launches for auto-scaling groups, and lower EBS cost on every instance you run.
Ready for AWS from first boot: cloud-init expands the root partition and filesystem to the volume size you launch with, the Elastic Network Adapter (ENA) and NVMe drivers are present and verified, and the AWS CLI is preinstalled. Red Hat Update Infrastructure is configured, so package updates need no Red Hat subscription.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
You pay by the hour for this hardened, minimal Red Hat Enterprise Linux 8 image. Pricing is not tiered. Instead, each rate maps to a specific AWS EC2 instance type you choose to run. The dimensions cover a wide range of instance families, including general purpose, compute, memory, storage, and accelerated computing types, from small sizes up to metal instances. Your software cost scales with the size and capability of the instance you select. You are billed only for the hours each instance runs. Larger instances carry a higher hourly rate.
Top-of-mind questions for buyers
What does the hourly rate for each instance type cover?
The rate covers the software licence for this hardened, minimal Red Hat Enterprise Linux 8 image on the instance type you pick. You are billed for each hour that instance runs. The rate rises with instance size. AWS charges the underlying EC2 compute and storage costs separately.
Am I charged the software fee when my instance is stopped?
The software fee meters running hours only. A stopped instance accrues no hourly software charge. Once you restart it, hourly billing resumes for that instance type. Note that AWS may still bill underlying storage for a stopped instance, but that is separate from this software licence.
Do I pay extra to keep the image updated with security patches?
No separate charge applies for updates. The image ships with a repository update service configured so the running system stays current at no added cost. It also includes the last security updates available at the release date, with security-focused settings enabled.
www.rinne-labs.com
Helpful?
Vendor refund policy
The instance can be terminated at anytime to stop incurring charges. No refund available
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
SELinux enforcing mode, root SSH login disabled, key-only SSH authentication, reduced SSH surface with X11 forwarding disabled, kernel network hardening via sysctl, audit rules loaded in running kernel, PAM-based account lockout via pam_faillock, password quality enforcement via pam_pwquality, default umask of 027, and login banners configured
Minimal Image Construction
Built from official Red Hat Enterprise Linux 8.10 Minimal Install package group, 10GB root volume without LVM, UEFI/GPT boot with XFS root filesystem, and rolling updates to newest 8.x releases
AWS Integration and Drivers
Elastic Network Adapter (ENA) driver present and verified, NVMe driver support, cloud-init configured for automatic root partition and filesystem expansion, and AWS CLI preinstalled
Automated Build and Verification Pipeline
Reproducible fully automated build pipeline from official distribution ISO, automated assertion suite validating all hardening controls on booted instance before publication, and versioned hardening baseline marker at /etc/rinne-labs-hardening
Repository and Update Management
Registered with Red Hat Update Infrastructure (RHUI) for security updates without requiring Red Hat subscription, distribution security updates applied at build time, and continued rebuilds with current security patches
Logical Volume Manager Storage Architecture
LVM-based disk layout enabling dynamic resizing, flexible partition management, and storage expansion without reinstallation or downtime.
Security Hardening Configuration
SELinux enforcement, SSH key authentication, disabled root login, and security hardening optimizations provided by ProComputers.
Cloud Initialization Support
Cloud-init enabled for automated provisioning, configuration, and lifecycle management on AWS EC2 instances.
Enhanced Networking Performance
ENA (Elastic Network Adapter) networking support providing high throughput, low latency, and stable network performance.
Red Hat Enterprise Linux Binary Compatibility
100% binary compatibility with Red Hat Enterprise Linux 8 ensuring compatibility with enterprise-grade software stacks and RHEL 8 repositories.
Security Hardening
Pre-hardened image with SI Core STIG hardening applied to enhance security posture and ensure compliance with industry standards
Kernel Optimization
Modern kernel enhancements and performance tuning optimized for cloud deployments to deliver exceptional efficiency in workload management
Binary Compatibility
Maintains binary compatibility with CentOS predecessors, enabling seamless migration from CentOS or support for legacy applications
Long-Term Support
Regular updates and extended support commitment ensuring infrastructure remains current with latest advancements
Multi-Workload Support
Supports diverse workloads including web hosting, development environments, data analytics, containerization, and microservices deployment
High availability has supported always-on fintech operations but subscription costs still need work
Reviewed on Oct 21, 2026
Review from a verified AWS customer
What is our primary use case?
Red Hat Enterprise Linux (RHEL) is our primary production OS across multiple environments. On our client environment, we also use the same Red Hat OS to run our Fintech applications.
In our Fintech environment, we run our product with ATM solutions like Hitachi, which must operate 24/7 and be available 365 days a year. The software must support these operations, be hardened security-wise, and allow us to balance the workload as much as possible.
Red Hat Enterprise Linux (RHEL) is easy to use as a distributed OS, allowing us to set it up in VMs, and it is highly supported with available support.
In managing regulatory compliance and upcoming mandates like post-quantum cryptography, our system metrics help us run services effectively.
How has it helped my organization?
Since using Red Hat Enterprise Linux (RHEL), we have maintained our production environment at 99.9% availability, with highly available on-premises servers and cloud environments, resulting in 80% growth compared to other operating systems.
To measure the 99.9% availability and 80% growth compared to other operating systems, we configured observability for all our platforms, measuring and analyzing reports quarterly to assess metrics and understand what went wrong.
What is most valuable?
Red Hat Enterprise Linux (RHEL) offers several best features, including community support, commercial support, and automation support through pre-configured Ansible playbooks to automate complex tasks. The solution also provides AI-driven predictive analytics tools while ensuring enhanced Linux security and hybrid cloud options.
Out of these features, I rely on the image building option, security, automating in-built Ansible playbooks, and security hardening most in my day-to-day work.
Regarding Red Hat Enterprise Linux (RHEL)'s AI capabilities, its insights are very helpful. I am satisfied with the accuracy and reliability of Red Hat Enterprise Linux (RHEL)'s AI output, as it has met my expectations.
To navigate our security risks, we use identity management and SELinux policies, which are the major tools that help our organization.
For CVE management, we leverage features like Lightspeed. We have tried Red Hat Enterprise Linux Image Builder, which helps us assign particular permissions and environments to configure them each time.
What needs improvement?
Red Hat Enterprise Linux (RHEL) could improve in areas such as subscription costs, where we must pay for production support and updates. There are also some restrictions related to the license with slow updates.
The needed improvements focus on the stability that Red Hat is emphasizing, which makes the update process slower. We could potentially test updates on non-production or development environments and report issues back to Red Hat.
I chose a score of seven out of ten due to three main points: the lack of process flowability, the subscription cost, and the complexity of distributions, which can be challenging for newcomers to the industry.
For how long have I used the solution?
We have been using Red Hat Enterprise Linux (RHEL) since 2020 on our production environments.
What other advice do I have?
I rate Red Hat Enterprise Linux (RHEL) a seven on a scale of one to ten.
In our organization, we deploy Red Hat Enterprise Linux (RHEL) primarily on-premises servers, followed by public cloud and hybrid cloud environments.
We use Azure and AWS as cloud providers for our public or hybrid cloud deployments.
I advise others looking into using Red Hat Enterprise Linux (RHEL) to recognize that it is an industry-wide approved and recognized environment that they should try.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
A. AhadAlam
Hybrid workloads have been simplified and daily operations save significant time and effort
Reviewed on Oct 15, 2026
Review provided by PeerSpot
What is our primary use case?
I am using Red Hat Enterprise Linux (RHEL) on a document management system, services server lines, and to build these applications.
Regarding lifecycle practices in the cloud, I am using two applications on-premises and a few are on Docker containers.
How has it helped my organization?
Red Hat Enterprise Linux (RHEL) saves me around 60% on time. With regard to downtime, I can lower downtime by about two to three minutes.
Regarding pain points, Red Hat Enterprise Linux (RHEL) does not help me solve any specific issues.
What is most valuable?
The biggest advantage of Red Hat Enterprise Linux (RHEL) is that it is easily available and easily manageable. The support cases are more readily used and the online local support is available.
With regard to the management part, when it comes to provisioning and patching, I can do patching and management on my own. I see that there is no difference between on-premises and cloud solutions; both are similar and it depends on conditions and the way the structure is organized. This is why I have no issues with on-premises or hybrid cloud deployments.
I find that integration with Red Hat Enterprise Linux (RHEL) is easy, as I am using it with Oracle.
What needs improvement?
Regarding disadvantages in Red Hat Enterprise Linux (RHEL), the certification cost is a concern for me. The problem with the certification is that its price is high, and it needs to be minimal for countries like Pakistan.
About the knowledge base that Red Hat offers, I feel it needs to improve session offerings more. This is especially important for junior beginners.
For how long have I used the solution?
I have around three to four years of experience using Red Hat Enterprise Linux (RHEL).
What do I think about the scalability of the solution?
Regarding scalability, I am satisfied. The services are easily available and scalable as per the need.
How are customer service and support?
My experience with Red Hat support is that it is very helpful. If I had to rate support from zero to ten points, I would give it a nine because everything is solved.
How was the initial setup?
Regarding deployment strategy, I find it quite simple. Regarding the upgrades and migration process from on-premises to the cloud, I have to first create a setup on a test machine, then upgrade, and after that, go live.
What was our ROI?
Regarding return on investment, I see value for money with Red Hat Enterprise Linux (RHEL). Red Hat Enterprise Linux (RHEL) saves me almost 60%. The saving I speak of is on both time and money.
What's my experience with pricing, setup cost, and licensing?
When choosing Red Hat Enterprise Linux (RHEL), our security requirement was that I am using it on IBM Power servers, which offered a bundle price. That is why I opted for Red Hat Enterprise Linux (RHEL). Regarding the price, I think the license is a little bit expensive nowadays, but I have opted for six years in a bundle offer. That is why I am using it at a cheaper price.
Which other solutions did I evaluate?
In comparing Red Hat Enterprise Linux (RHEL) to other Linux distributions, I find Red Hat Enterprise Linux (RHEL) to be more stable than compared to others in terms of performance, storage, and security. Although other distributors are more secure, as part of my choice, I choose Red Hat Enterprise Linux (RHEL).
What other advice do I have?
When I have it on the cloud, I work with a local provider rather than a native Red Hat Cloud or cloud providers like AWS, Azure, or GCP. I have not tried Image Builder of Red Hat Enterprise Linux (RHEL) at this time. I would give Red Hat Enterprise Linux (RHEL) a rating of nine points.
Kandregula Sathvik
Granular access controls have strengthened security testing and streamlined user administration
Reviewed on Sep 24, 2026
Review provided by PeerSpot
What is our primary use case?
I mostly use Red Hat Enterprise Linux (RHEL) for security purposes, conducting security testing, cyber security testing, and general administration purposes, including maintaining accounts.
What is most valuable?
Red Hat Enterprise Linux (RHEL) offers extensive customization options that I can tailor to my specific needs. I love the customizability and adaptability.
The knowledge base offered by Red Hat Enterprise Linux (RHEL) is quite comprehensive and vast. I search through it and use AI to resolve any queries I have.
The most important security feature in Red Hat Enterprise Linux (RHEL) is the excellent administration policy regarding which user can access which file and what type of permissions I can assign. I appreciate this as a local IAM system.
The IAM feature is most valuable for us because we have around 200 to 300 users, and it can be difficult to track which people have what type of privileges. This feature provides a very neat and detailed view of the privileges that people are assigned.
What needs improvement?
I would like to see improvements in the CLI, making it somewhat easier instead of the complicated commands that are currently used. Keeping it simple and easy to remember would be beneficial.
For how long have I used the solution?
I have been working with Red Hat Enterprise Linux (RHEL) for three years.
What do I think about the stability of the solution?
Red Hat Enterprise Linux (RHEL) is very stable.
What do I think about the scalability of the solution?
Regarding scalability, I find Red Hat Enterprise Linux (RHEL) to be quite scalable and does not require much time for scaling.
The only concern is the costing when it comes to cloud instances.
How are customer service and support?
I have never escalated any questions to the technical support or customer service teams regarding Red Hat Enterprise Linux (RHEL).
Which solution did I use previously and why did I switch?
I have not used any different product for operating systems before.
How was the initial setup?
The initial setup process for Red Hat Enterprise Linux (RHEL) was straightforward.
What about the implementation team?
I completed the setup and deployment myself.
What was our ROI?
The business value of Red Hat Enterprise Linux (RHEL) is quite high. It provides excellent availability and never crashes. The machine performs reliably when I need it, resulting in very few downtimes.
What's my experience with pricing, setup cost, and licensing?
Regarding the pricing aspect of Red Hat Enterprise Linux (RHEL), I mostly use free resources and have not procured any license. I prefer to use open-source options and maintain my own set of rules.
With the open-source nature of Red Hat Enterprise Linux (RHEL), the measurable benefits I have seen are primarily cost benefits. It is highly customizable and saves considerable time because I do not need to explain what I want to anyone; I simply conduct research and implement those features into my instances.
Which other solutions did I evaluate?
I chose Red Hat Enterprise Linux (RHEL) because I am familiar with it and receive good updates and security updates.
What other advice do I have?
I have not worked with LEAP or Red Hat Insights yet.
I have mostly worked with Red Hat Enterprise Linux Image Builder and System Roles. System Roles have been helpful for me as I started using them recently. I previously limited some resources in my systems by using only a specific percentage of available hardware resources and reducing bloatware, which involves resource controlling.
I have never tried Red Hat Enterprise Linux (RHEL) in a hybrid environment. I mostly connect to some instances in the cloud through SSH but have never used hybrid solutions.
Until now, Red Hat Enterprise Linux (RHEL) has not helped me solve specific pain points, except for using the command line terminal and assigning many different permissions to accomplish one task.
The controlled updates and patches save a lot for me regarding Red Hat Enterprise Linux (RHEL).
From a features perspective, there are no missing features that I would see included in Red Hat Enterprise Linux (RHEL) in the future.
I obtained Red Hat Enterprise Linux (RHEL) directly from Red Hat. My overall review rating for this product is 9.
UmairKhan2
Platform has improved network administration but still needs simpler setup and better training
Reviewed on Sep 23, 2026
Review provided by PeerSpot
What is our primary use case?
I primarily use Red Hat Enterprise Linux (RHEL) for network administration.
What is most valuable?
I wonder if you tried either Leapp or Red Hat Insights. I don't know exactly, but I don't think we went that deep into it because there were some specific sets of instructions we used to run every time.
Red Hat Enterprise Linux (RHEL) helped to mitigate downtime and lower risks, and I would say it's above average.
Sometimes there are new rollouts or features, or if I am exploring something new in support, I basically face problems where it's difficult for me to educate newcomers, interns, or new entrants to get accustomed to these things because it's an entirely new environment and new platform compared to what we have been using here in our country and in our organizations. If I am using Microsoft for certain things, it's mostly graphic based, but in Red Hat Enterprise Linux (RHEL), it's mostly very command-line specific.
What needs improvement?
I think that if sometimes there are certain solutions where the support team with some specific technical personnel could remotely assist using TeamViewer or something similar to solve specific issues, then I think it could be much faster.
I think the commercial rollout of Red Hat Enterprise Linux (RHEL) could improve because this is a very specific kind of product that isn't commercial in nature. If there is some kind of integration with commercial customers and it is used more frequently in everyday life, along with improved graphic interfaces, capacity building, training platforms, or webinars, then I think we can extend the market, have more users, and receive more accurate feature-based feedback from them.
For how long have I used the solution?
I used Red Hat Enterprise Linux (RHEL) for almost two years or longer.
How are customer service and support?
Technical support for Red Hat Enterprise Linux (RHEL) was definitely good. Sometimes if we were stuck and needed troubleshooting or were trying to perform some function that wasn't happening, it was satisfactory. I can rate their technical support at least eight.
Which solution did I use previously and why did I switch?
I was using Red Hat Enterprise Linux (RHEL) personally for my own use. I am no longer using Red Hat Enterprise Linux (RHEL). I switched from Red Hat Enterprise Linux (RHEL) almost one year ago.
How was the initial setup?
The initial setup of Red Hat Enterprise Linux (RHEL) was initially complex.
Sometimes there are new rollouts or features, or if I am exploring something new in support, I basically face problems where it's difficult for me to educate newcomers, interns, or new entrants to get accustomed to these things because it's an entirely new environment and new platform compared to what we have been using here in our country and in our organizations.
What's my experience with pricing, setup cost, and licensing?
I would like to understand what my experience was with the pricing of Red Hat Enterprise Linux (RHEL) and whether I find it reasonable and competitive.
Which other solutions did I evaluate?
I think we purchased Red Hat Enterprise Linux (RHEL) from a third party, from some other vendor.
What other advice do I have?
I have multiple experiences working in this field. Initially, I was a network administrator, focusing on networking, mainly in routing and switching. I worked with internet service providers, so I have experience with a NOC and service provider solutions in that regard, particularly dealing with Red Hat Enterprise Linux (RHEL) for network administration.
Niek Beernink
RHEL has strengthened security and standardization in a disconnected environment
Reviewed on Aug 09, 2026
Review provided by PeerSpot
What is our primary use case?
I use Red Hat Enterprise Linux (RHEL) for servers as well as workstations.
Our site has around 3,000 workstations that our developers are building our software on. For servers (~1000), we are using it for self-hosting tools required for software development and testing.
Furthermore, we are also working on implementing a process for using Image Builder to build a Standard Operating Environment image deploy that to virtual machines. Then we use RHEL System Roles and a lot of custom ansible roles to manage the state of the machines.
What is most valuable?
Red Hat Enterprise Linux (RHEL) offers enterprise security and really well-written documentation.
The most important security feature in the Red Hat ecosystem is the errata data, combined with Satellite. It tells you exactly which component is vulnerable, which versions of Red Hat Enterprise Linux (RHEL) are affected, and overall the documentation provided with errata is easily readable for various audiences (for example a summary for management as well as more technical for engineers).
Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk by providing kpatch. These are kernel patches, which allow us to apply security patches to a running kernel. We can then plan a full reboot outside of office hours.
The Red Hat Offline Knowledge base offered by Red Hat Enterprise Linux (RHEL) is really helpful. In a disconnected environment it allows you to search all documentation and errata up to a given date without having to reach out for the internet to check the details.
What needs improvement?
Sometimes the support for Red Hat Enterprise Linux (RHEL) could be better. Since we're in a disconnected environment, it's sometimes really hard to share explicit details about the issue we're running into and we keep getting asked for an SOS report, which we cannot supply due to security concerns.
For how long have I used the solution?
I've been working with RHEL for seven years.
What other advice do I have?
Look at the interactive labs provided by Red Hat, they give a great hands-on experience and show off the benefits would advise others looking into using Red Hat Enterprise Linux (RHEL) to investigate the training that is available.