External reviews
363 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Good automation tool
What do you like best about the product?
Nice comprehensive manager to run Ansible Automation. Really much improved and needed items for Tower.
What do you dislike about the product?
A little clunky with organization. Sometimes hard to find things and have to jump around many screens. Hoping new AI capabilities will lower troubleshooting and finding jobs.
What problems is the product solving and how is that benefiting you?
Automates our software updates and patching of existing software.
Simplifies automation
What do you like best about the product?
It's flexibility. I've been able to solve many problems across different stacks, technologies etc. at scale using Ansible.
What do you dislike about the product?
The logging is not the best. It could be improved.
What problems is the product solving and how is that benefiting you?
We have been able to scale and deploy applications, updates, configuration changes etc with reliability and very little human intervention.
AAP
What do you like best about the product?
AAP reduces configuration drift drastically.
What do you dislike about the product?
Deployment documentation is not thorough enough.
What problems is the product solving and how is that benefiting you?
AAP resolves configuration drift from secure baselines required for security compliance.
Ansible Automation platform
What do you like best about the product?
Ansible Automation platform provides an organized GUI
What do you dislike about the product?
not much to dislike about Ansible Automation platform
What problems is the product solving and how is that benefiting you?
configuration management, enterprise mgmt
Ansible for Automation
What do you like best about the product?
The best thing I like about the product of its agent less feature which help us to maintain upgrade process easy.
What do you dislike about the product?
The windows Agent less still require improvement in the product. There should also be a seem less upgrade from one version to another.
What problems is the product solving and how is that benefiting you?
We are using this product for security compliance
Ansible is a great tool for automation
What do you like best about the product?
I love that Ansible can connect to any device without using an agent.
What do you dislike about the product?
The license cost per node is quite high. There are open source versions available to use though not recommended for production environments.
What problems is the product solving and how is that benefiting you?
It allows me to quickly manage devices across my entire infrastructure.
AAP was built for you and me
What do you like best about the product?
I love Ansible for all things configuration management. Ansible Automation platform provides an awesome way for others to join in on utilizing the benefits of Ansible in a more friendly way. The user interface is clean and easy to learn.
What do you dislike about the product?
Cost is definitely a thing that can be off putting with moving towards the GUI offering (as well as other associated features that come with it).
What problems is the product solving and how is that benefiting you?
Allows organizations a way to onboard developers to using Ansible for standardizing code roll-out and deployment as well as configuration changes.
the beat automation tools, a life saver
What do you like best about the product?
really easy to get up to pace, friendly user interface
What do you dislike about the product?
I still like to do prompt , so I miss it sometime
What problems is the product solving and how is that benefiting you?
simplify apps delivery and implementing newsettings
Automation anywhere
What do you like best about the product?
Event Driven Automation for dynamic playbook
What do you dislike about the product?
Inventory discovery take longer time for large enviroment
What problems is the product solving and how is that benefiting you?
Make the standaration of complex activities and ensure the errorless delivery
Scalable Automation, Non-Scalable Credential Usage
What do you like best about the product?
I've been using AAP for quite a while. In Tower, the concept of creating a "secure bubble wrap" by utilizing virtualenvs was a great idea. However, from my world of Secrets Management, it made it near impossible to get attributes of the workload executing within to identify it without a "secret zero".
Today, in AAP... the containerized execution environments are a game changer! Now, we can determine the attributes of the environment to provide it secrets and when the execution completes -- POOF! -- the container and all secrets within are gone!
This simple change in architecture to improve modernization was an amazing advancement!
Today, in AAP... the containerized execution environments are a game changer! Now, we can determine the attributes of the environment to provide it secrets and when the execution completes -- POOF! -- the container and all secrets within are gone!
This simple change in architecture to improve modernization was an amazing advancement!
What do you dislike about the product?
I said I was in secrets management, so you should see this one coming:
"The Single Credential Problem"
Today, Job Templates only support 1 Machine Credential. If I want to scale a job template across many hosts to patch them efficiently, there is no native way to accomplish this today. I have to utilize a workaround that employs the use of lookup plugins in the playbook and dynamically fetching secrets just-in-time based on inventory_hostname. It was actually my Lightning Talk for AnsibleFest here at Summit this week. The feature request was added to AWX in 2017.
Also, AAP has no underlying OIDC configuration. This makes it hard to utilize an identity-aware process that allows secrets management to utilize attributes of workloads (the "payload" of the JWT from OIDC) to identify them instead of a "secret zero" needing to be utilized. Cloud services and even OpenShift has this support today... a modern AAP should also support the same similar to most CI platforms out there.
"The Single Credential Problem"
Today, Job Templates only support 1 Machine Credential. If I want to scale a job template across many hosts to patch them efficiently, there is no native way to accomplish this today. I have to utilize a workaround that employs the use of lookup plugins in the playbook and dynamically fetching secrets just-in-time based on inventory_hostname. It was actually my Lightning Talk for AnsibleFest here at Summit this week. The feature request was added to AWX in 2017.
Also, AAP has no underlying OIDC configuration. This makes it hard to utilize an identity-aware process that allows secrets management to utilize attributes of workloads (the "payload" of the JWT from OIDC) to identify them instead of a "secret zero" needing to be utilized. Cloud services and even OpenShift has this support today... a modern AAP should also support the same similar to most CI platforms out there.
What problems is the product solving and how is that benefiting you?
I'm a Red Hat Partner employed by CyberArk. I don't have business problems that I'm solving for myself, but my customers have business problems they're trying to solve. The largest one is the one I referenced before where these teams are struggling to understand how to efficiently scale to many hosts in a secure way.
showing 21 - 30