Red Hat Ansible Automation Platform Service on AWS
Automation has transformed patching and now secures thousands of servers in hours
What is our primary use case?
My main use case for Red Hat Ansible, which is a disruptive solution. I think every large company today should have Red Hat Ansible because it helps a lot with the administration of large environments, operating systems, and servers. In a scenario where we increasingly need governance, security, and configuration focused on defense against cyberattacks, having a tool that allows you to make these changes atomically on many servers at the same time, even thousands of servers at once, is vital. Ansible does this excellently regardless of the operating system, whether Windows, Linux, or Mac. It also integrates easily with network devices, whether Cisco IOS or any other vendor. I think Ansible is a must-have tool for every large company that wants to remain relevant and secure.
A quick and specific example of a situation in which RedHat 9 with support by ProComputers, together with Ansible, brought concrete benefits to my operation is when I needed to apply zero-day patch fixes. It also applies to cases where a workaround is needed because the patch isn't available, but a configuration change in the operating system closes that door for the attacker. I have handled several situations like that with Ansible, and I managed to make my entire environment secure, with more than ten thousand servers secured with one click.
I think it is worth reinforcing that it is a must-have tool for medium and large companies, but especially for large ones.
How has it helped my organization?
RedHat Ansible has had a positive impact on my organization by reducing the total time for applying patches. It used to take weeks to complete, and today it is finished in a few hours.
This reduction in time improves productivity by allowing the team to use the free time to focus on more important and less operational activities.
What is most valuable?
The integration of Ansible makes my work easier and benefits the team because Ansible should enter a provisioning pipeline. When we talk about SDLC today, we also understand that infrastructure as code is part of the software development life cycle. By putting Ansible in the middle of this SDLC, I can create machines and configure them, which in short is everything we usually call the full set needed to prepare a server or any computing device, and I have the full cycle from start to finish. All of this is versioned in Git, where I can have it as my infrastructure-as-code repository.
What needs improvement?
I believe that a native integration with CMDB vendors could be useful to integrate and automatically create an inventory inside Ansible.
I would also like to mention the pricing; I believe it is an expensive tool.
For how long have I used the solution?
I have been using RedHat Ansible for more than ten years.
What do I think about the stability of the solution?
RedHat Ansible is very stable; it is known precisely for its stability.
What do I think about the scalability of the solution?
The scalability of RedHat Ansible is excellent as well; you can scale from single units up to tens of thousands if necessary, so it is easy.
How are customer service and support?
The customer support of RedHat in Brazil is excellent, and the team is very competent. International support is also very good and very fast.
I would rate customer support an eight on a scale from one to ten.
Which solution did I use previously and why did I switch?
Previously, we used a manual solution, and we switched to be faster at meeting market demands and to have the environment secure more quickly.
What was our ROI?
We have saved time, but we haven't exactly done an ROI calculation to know how much that returned financially. Still, as I said earlier, the security patching process that used to take weeks started to take only a few hours.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing could improve. I think it is a very expensive tool. The negotiation is good, the support is very good, and the Brazilian sales team is very capable, but it is an expensive tool.
Which other solutions did I evaluate?
Red Hat Ansible is the market leader for one single and exclusive reason: it is the best tool available for this, so it is a consensus.
What other advice do I have?
On a scale from one to ten, I would rate RedHat Ansible an eight overall.
I rate it an eight because I consider Ansible to have a high financial cost. It is not a cheap tool. A ten doesn't exist; there is no tool that deserves a ten.
It is implemented in my organization in a hybrid cloud format. In our hybrid architecture, we use Azure, AWS, GCP, and OCI as cloud providers.
My advice for others who are thinking of using RedHat Ansible is to make sure to include it in your budget for next year.
Powerful automation tool with a slight learning curve
Efficient Automation with Some Learning Curves
Best-in-Class Agentless Linux Security with Complete Features
Powerful Linux Automation with Ansible and Fast Red Hat Support
Since now the latest Ansible version runs on containerized Environment Engineers require to have knowledge on containerized envroinment like docker and podman
But now with ansible once any update is available we can push the updates as and when required.
Automation has transformed server patching and has reduced months of work to minutes
What is our primary use case?
My main use case for Red Hat Ansible Automation Platform is managing servers through automated deployment, automated management, security patching, and everything in between.
For automating deployments or security patching with Red Hat Ansible Automation Platform, we use it for Docker Swarm clusters. We install Docker and automate Docker deployment inside the Docker Swarm, checking which are the master nodes and which are the server nodes and connecting them to each other. All of these things are maintained by Red Hat Ansible Automation Platform.
I have around 100-200 servers that we need to maintain through security patching. We need to perform sudo apt update or install packages inside them and maintain those servers. For that, we use Red Hat Ansible Automation Platform. We maintain an inventory file and execute everything from there.
What is most valuable?
The best features that Red Hat Ansible Automation Platform offers is that it does not require any additional resources inside the servers. Python is the only requirement, and since Python is already present inside the servers, we can run it from our location and it automatically deploys things and does the work for us.
The minimal requirements and easy deployment have definitely impacted my daily work and my team's efficiency. Red Hat Ansible Automation Platform is one of the best features that we depend on. We have evaluated other options, but Red Hat Ansible Automation Platform was the best choice because it has saved us a tremendous amount of time. We do not need to manually intervene in the servers or install third-party software to maintain these things.
It is very easy to write playbooks for Red Hat Ansible Automation Platform. Ansible Galaxy contains many playbooks that are readily available and ready to be used. It is highly configurable with Jinja templating, making it easy to maintain.
Red Hat Ansible Automation Platform has positively impacted my organization. Previously, we needed to go into the servers and maintain them manually, which used to take a lot of time. For 200 to 300 servers, the maintenance took about one to two months. New patches would arrive and we would have to repeat the process. Now, it is a one-night work or a 10 to 15 minutes task. We write a playbook, maintain an inventory, and roll out the updates and it starts working for us. Red Hat Ansible Automation Platform uses conditional clauses and has rollback options, functioning like a standard coding language that is simple to use.
There is definitely a reduction in errors with Red Hat Ansible Automation Platform because we have playbooks written with all the necessary clauses and rollback options. Manual work automatically creates more errors, whereas in automation, we have written sets that we do not forget every time we run it. We have protected written sets that we execute consistently.
What needs improvement?
Red Hat Ansible Automation Platform could benefit from improvements in certain areas. Red Hat Tower is available for enhanced functionality, though it operates on a paid model. I found that acceptable.
Otherwise, Red Hat Ansible Automation Platform is very easy to use with Jinja templating capabilities that make it really straightforward. I do not believe there is anything that could be improved with Red Hat Ansible Automation Platform that we have not already discussed.
For how long have I used the solution?
I have been using Red Hat Ansible Automation Platform for the past eight years.
What do I think about the stability of the solution?
In my experience, Red Hat Ansible Automation Platform is very stable.
What do I think about the scalability of the solution?
Red Hat Ansible Automation Platform is highly scalable. We are currently using 200 servers and we are adding more servers each day. Red Hat Ansible Automation Platform is easily maintainable and highly scalable.
How are customer service and support?
We are not using Ansible Tower for customer support, so we do not receive official support. However, Red Hat Ansible Automation Platform has a large community with many written blogs and resources available, making it easy to maintain.
How would you rate customer service and support?
How was the initial setup?
My experience with pricing, setup cost, and licensing for Red Hat Ansible Automation Platform was very simple. There is no pricing and no licensing required, as Red Hat Ansible Automation Platform is always free to use. If you do not use Ansible Tower, then it is definitely free and easy to maintain. Writing playbooks is just like writing a simple Bash script or writing code with clauses and everything.
What was our ROI?
I have seen a return on investment with Red Hat Ansible Automation Platform. We need fewer employees and have saved significant time. The work that previously took two months now takes 10 to 15 minutes. Red Hat Ansible Automation Platform is automated, so we do not need as many employees to perform manual work. We have fewer employees, which also results in cost savings.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Red Hat Ansible Automation Platform was very simple. There is no pricing and no licensing required, as Red Hat Ansible Automation Platform is always free to use. If you do not use Ansible Tower, then it is definitely free.
Which other solutions did I evaluate?
Before choosing Red Hat Ansible Automation Platform, I evaluated other options such as Chef and Puppet, but I did not use them.
What other advice do I have?
The advice I would give to others looking into using Red Hat Ansible Automation Platform is that it is one of the best Ansible management tools available for servers. You should start using it. Red Hat Ansible Automation Platform offers Jinja templating where you can write your own templates and NGINX configurations. It is very simple to use and you do not need any extra server or additional infrastructure. I give this product a rating of 9 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Consistent, Scalable Automation That Boosts Stability and Efficiency
Cloud services, on‑prem servers, or network devices, Ansible connects to everything without needing any agents. This flexibility has made it much easier to scale automation across the organization stacks.
Also, its write once-reuse anywhere motoo help us reuse across multiple projects or environments. This not only speeds up deployments but also ensures the same process runs the same way every time, which has noticeably improved our operational stability.
May be few cases where they struggeled are role structuring, output capturing and reusing andYAML Sensitivity are more prone to error.
UI is helpful, but it introduces extra complexity compared to using Ansible alone. Managing inventories, credentials, and job templates through the controller sometimes feels more complicated than necessary.
These are just my experiences, others may feel it easy though if the have already used CFT or TF.
Agentless Architecture and Scalable Orchestration Made Simple
IT Observability Advisor
Have managed thousands of servers with streamlined configuration processes
What is our primary use case?
I have created resources for the monitoring tech stack with Red Hat Ansible Automation Platform, especially for setting up one master data center and another data center for different applications routed to the monitoring setup, where I have created Splunk servers and installed all Splunk agents and prerequisites with the help of Ansible, including an Ansible playbook.
I have used the agentless architecture in Red Hat Ansible Automation Platform, as SSH is agentless.
I use a centralized automation controller in Red Hat Ansible Automation Platform, called the master setup, where we execute our commands with installed prerequisites, inventory information, and the Ansible playbook, managing other node servers with a passwordless setup.
When creating any server with Red Hat Ansible Automation Platform, it is a significant advantage because if we set up a Splunk agent in one case, it is necessary for each server. By writing the playbook, the agent is installed immediately during server provisioning, providing us with an edge.
What is most valuable?
Red Hat Ansible Automation Platform is very helpful due to passwordless integration and the ability to interact with multiple servers at once, which is especially advantageous when dealing with thousands of servers.
The integration aspect of Red Hat Ansible Automation Platform has optimized my IT ecosystem significantly by consolidating multiple tools, such as a CI/CD pipeline with Jenkins, where we validate everything, including testing and SonarQube code quality.
The agentless architecture of Red Hat Ansible Automation Platform, using the SSH key, makes it passwordless and allows us to push configurations with one click, creating a major advantage.
Red Hat Ansible Automation Platform's main benefit is that it allows us to push configurations to multiple servers without manually visiting each one, maintaining efficiency.
What needs improvement?
I have observed that Red Hat Ansible Automation Platform could improve by creating modules for upcoming AI and ML tech stacks, as currently, specific modules for these are not available.
For how long have I used the solution?
I have worked on Red Hat Ansible Automation Platform, especially Ansible Playbooks, for around three years.
What do I think about the stability of the solution?
I have not encountered any performance issues, crashes, downtimes, or limitations with Red Hat Ansible Automation Platform.
How are customer service and support?
Ansible is a Red Hat product, so they provide all necessary support.
I have not escalated any questions to the Red Hat support team regarding Red Hat Ansible Automation Platform, as their modules are professional and complete.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Both Red Hat Ansible Automation Platform and Chef have similar capabilities but differ in architecture; one is agentless while the other is agent-full.
How was the initial setup?
Setting up Red Hat Ansible Automation Platform on the AWS cloud is very straightforward; I take one server, install Ansible, set up the inventory, and use it.
What was our ROI?
By using the enterprise version of Red Hat Ansible Automation Platform, we receive support that aids in overcoming challenges, a measurable benefit in terms of ROI.
What's my experience with pricing, setup cost, and licensing?
For enterprise users of Red Hat Ansible Automation Platform, there are fees, but it is free and open-source for testing or small labs.
Which other solutions did I evaluate?
I have worked with Chef as a configuration management tool for one project, and I have used Chef and Red Hat Ansible Automation Platform together in the same project.
What other advice do I have?
I have worked on the AWS cloud with Red Hat Ansible Automation Platform.
Red Hat Ansible Automation Platform was hosted on AWS.
I prefer Red Hat Ansible Automation Platform because it is easy to implement, and the extensive supporting documentation is very helpful.
I suggest everyone consider Red Hat Ansible Automation Platform because it is agentless, easy to implement, and has sufficient supporting documentation available.
On a scale of one to ten, I rate Red Hat Ansible Automation Platform a ten out of ten.